1 / 63

e -Governance for Enhance Service Delivery

e -Governance for Enhance Service Delivery Transfer Knowledge, Develop and Implement Quick Win Pilot E-Services (Service Oriented Architecture (SOA) -Based Business Process Management (BPM)) June 2 nd to 21 st 2012 Amman- Jordan Day 2 Present by:. Agenda.

ulric
Download Presentation

e -Governance for Enhance Service Delivery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. e-Governance for Enhance Service Delivery Transfer Knowledge, Develop and Implement Quick Win Pilot E-Services (Service Oriented Architecture (SOA) -Based Business Process Management (BPM)) June 2nd to 21st 2012 Amman- Jordan Day 2 Present by:

  2. Agenda

  3. Business Process Management إدارة عمليات الأعمال

  4. What is BPM • Business Process Management is a generic term, that encompasses the techniques, structured methods, and means to streamline operations and increase efficiency. • BPM techniques and methods enable you to identify and modify existing processes to align them with a desired (improved) future state. • إدارة عمليات الأعمال هو مصطلح عام، يشمل تقنيات وأساليب التنظيم، والوسائل اللازمة لتبسيط العمليات وزيادة الكفاءة. • تقنيات وطرق إدارة عمليات الأعمال تمكنك من تحديد وتعديل العمليات الحالية لمواءمتها مع الحالة المستقبلية (المحسنة) المرجوة.

  5. Compliance Strategy Policies Information Goals Systems Business Process Management (BPM) Software and strategy for modeling, automating, managing and optimizing business processes across organizational divisions, systems and applications. برمجيات وإستراتيجية لقولبة، وأتمتة، وإدارة وتحسين عمليات الأعمال عبر التقسيمات التنظيمية والنظم والتطبيقات. Process People

  6. Principles of BPM مبادئ إدارة عمليات الأعمال • Organize around outcomes not tasks • Correct and improve processes before (potentially) automating them • Establish processes and assign ownership • Standardize processes across the enterprise • Enable continuous change • Improve existing processes, rather than build radically new or ‘perfect’ processes • تنظيم حول النتائج وليس المهام • تصحيح وتحسين العمليات من قبل أتمتها • إنشاء العمليات وتعيين المسؤولين عنها • توحيد العمليات عبر المؤسسة • تفعيل التغير المستمر • تحسين العمليات القائمة، بدلا من بناء عمليات جذرية جديدة أو 'مثالية‘.

  7. Typical Business Drives الدوافع • Reduce staff and office overhead numbers • Process business critical activities faster • Reduce the number of errors and exceptions • Reduce overall IT costs • Reduce duplications • Increase visibility into operational efficiencies and bottlenecks • Reduce business risks • Improve customer service and retention • خفض عدد الموظفين والنفقات العامة • معالجة أنشطة الأعمال الحاسمة بشكل أسرع • تقليل عدد الأخطاء والاستثناءات • خفض إجمالي تكاليف تقنية المعلومات • الحد من الازدواجية • زيادة وضوح في الكفاءة التشغيلية واختناقات سير عمليات الأعمال • الحد من مخاطر الأعمال • تحسين خدمة العملاء والاحتفاظ بهم

  8. Business Analysis تحليل الأعمال • No business process improvement or change activity can be undertaken without the use of business analysts and/or business analysis techniques • You must never attempt to change a business process without first analyzing the business impact of the change in detail • Most people think they understand the techniques of analysis (e.g., requirements gathering), but few actually do • Most projects failures do not stem from technology • Rather, a lack of insight, stakeholder support or planning -- all things that are the focus of business analysts!

  9. Business Process Analysis تحليل عمليات الأعمال • Most common starting point is when something is not right in the organization… • A meta problem: there are duplicative processes and information across departments • A business problem: exception rate is too high • A micro problem: some user interface screens are confusing • Business Analyst needs to • evaluate the situation from various angles and identify core issues • review any documentation, interview workers • flowchart/document current process • recommend improvements • When to use: When you have already clearly identified a specific process or process for improvements

  10. Benefits of BPM فوائد إدارة عمليات الأعمال

  11. BPM & SOA

  12. Success Depends on Business Impact and Process Complexityالنجاح يعتمد على مدى التأثير على الأعمال وعلى مدى تعقيد العملية

  13. Oracle BPM

  14. Oracle BPM Solution Components BPM BPEL PM Human Centric Business Process Management • Business user friendly • Human centric • Collaborative • Frequent process changes System Centric Process Management and SOA • SOA architecture • Apps integration, AIA • BPEL • High performance STP • Round-tripping with BPA

  15. Unified Process Foundation • Unified engine –BPEL, Rules, Human Workflow to support ALL types of processes • Business catalog –A registry of services and objects that enables IT to provide prewired processes and human tasks to be assembled in Process Composer • End-to-end management & monitoring -Find faults that have happened anywhere in the system and take corrective action • Integration Services –Adapters, UDDI integration, CEP integration, BI action framework integration, Identity management integration • Scalable architecture –From simple to complex tasks, and large volumes of transactions

  16. Unified Runtime Platform منصة تشغيل موحدة MS Office BAM, BI Worklist Process Portal BPEL BPMN 2.0 Human Task (BPEL4People) Business Rules Process Core BPEL Business View SCA BPM Server Enterprise Manager BPM (with Business and IT view)

  17. Oracle Business Process Execution Language BPEL

  18. What is BPEL • Business Process Execution Language • BPEL is an open industry standardhttp://docs.oasis-open.org/wsbpel/2.0/wsbpel-specification-draft.html • Oracle has made supported extensions to BPEL • Human Workflow Service Engine • Database Interfaces • Applications Adapter • SOA based (Service Oriented Architecture) BPEL allows for the integration of Web Services into end-to-end processes. • These BPEL processes can themselves be a Web Service. • BPEL is far more powerful than Workflow so keep an open mind as we all move through this transition.

  19. BPEL Features • Supports Synchronous & Asynchronous Transactions • Flow Controlالتحكم في التدفق • Compensating Transactionsالإجراءات التعويضية • Data Manipulation using XPath, XSLT, and Xquery • Human Workflow • Routing/Assignments توجيه / تكليف • Notifications إخطارات • Nomination, Delegation and Reassignment ترشيح، تفويض وإعادة تكليف • Escalations التصعيد • JSP Formsنماذج • Work List Applicationقائمة الأعمال • Comments and Attachmentsالملاحظات و المرفقات • Audit Trailالمراجعة والتدقيق

  20. BPEL Process in JDeveloper

  21. BPEL Mapping / Transformation

  22. BPEL Console

  23. BPEL Console – Process Flow

  24. Human Task Flow الإجراءات التي تتطلب تدخل بشري

  25. Human Task

  26. Human Task • A BPEL process invokes a special activity of the human task type when it needs a human to perform a task. • The process waits for the task to complete. • There is metadata associated with the task that is used by the human task service component to manage the lifecycle of the task: • Who performs the task • Who are the other stakeholders • When must the task be completed • How do users perform the task, • The human task service component uses an identity directory, such as LDAP, to determine people's roles and privileges. • The human task service component presents tasks to users through a variety of channels: • Worklist Application • Worklist Portlet • Notifications: email, phone, SMS, etc.

  27. Work Listقائمة الأعمال

  28. Human Task Features Flow Patterns & Routing Policies Flow Patterns & Routing Policies Escalation & Notifications

  29. Workflow Services

  30. Oracle Business Rules قواعد سير العمل

  31. Business Rulesقواعد سير العمل • Business rules are statements that describe business policies or describe key business decisions. • قواعد سير العمل هي العبارات التي تصف سياسات العمل أو تصف قرارات الأعمال الرئيسية. • Examples: • Business policies such as spending policies and approval matrices. • Constraints such as valid configurations or regulatory requirements. • Computations such as discounts or premiums. • Reasoning capabilities such as offers based on customer value.

  32. Business Rules – Declarative Rules

  33. Business Rules – Decision Table

  34. Oracle Business Activity Monitor BAM مراقب نشاط الأعمال

  35. Business Activity Monitor - BAM • Oracle BAM provides a framework for • Creating dashboards that display real-time data inflow. • Creating rules to send alerts under specified conditions.

  36. Business Activity Monitor - BAM • Data and Event Collection: The Oracle BAM provides mechanisms to collect event and data information from various sources, and it is integrated with Oracle BPEL Process Manager to link process-related events in real time. • Event Analysis: This allows the filtering and analysis of event-based information in line with the KPI information set by the users. • Intuitive Dashboards: This allows detailed reports regarding the process to be available to the users as per their requirements. It allows data from various sources to be made available using intuitive dashboards, which a user can use to take decisions or set customized alerts. • Real Time Alerts: The Oracle BAM provides the capability for setting alerts in case a business process is performing outside the range of acceptable standards.

  37. Oracle Applications Development Framework ADF

  38. Oracle Application Development Framework (ADF) • Is an end-to-end Java EE framework that is extensible • Utilizes and adds value to the Java EE platform • Abstracts Java EE complexity • Provides declarative and visual development • Enables developers to focus on the application, not the low-level infrastructure • Creates reusable and maintainable code • Uses metadata, simplifying the basic task of wiring user interfaces to services • Implements Java EE best practices and design patterns, including MVC

  39. The Model-View-Controller Design Pattern

  40. Implementing MVC with the ADF Framework Desktop Browser-based JSF JSP Office ADFSwing View ADF Faces / DVT Controller Struts JSF/ADF Task Flow ADF Bindings (JSR 227) Model Web Services Java EJB BAM BPEL ADFbc BI Essbase Portlets Business Services TopLink Data Services Relational Data XML Data Legacy Data Packaged Apps

  41. Types of ADF Business Components StorefrontAM CustomerEO Customer CustVO CustomerOrder OrderEO OrdVO AllOrders LineItemEO View ObjectsandView Link Application Modulewith View Object Instances Entity Objects and Associations

  42. SOA Guidelines & Best Practices المبادئ التوجيهية و أفضل الممارسات

  43. Understand Your Organization

  44. Start with Business Firstإبداء بالأعمال أولا • Do not try to boil the ocean. • Focus on what is strategically important --- NOW! • Front End E-Services first • Regulations & Compliancy • E-Government Coverage • Near-term focus, grow scope over time • لا تعقد الأمور • ركز على ما هو مهم من ناحية إستراتيجية • الخدمات الموجهة للجمهور أولا • اللوائح و الامتثال للقوانين • تغطية كاملة للحكومة الإلكترونية • التركيز على الخطط قريبة المدى ثم الانطلاق إلى بعيدة المدى

  45. Be Flexibleتمتع بالمرونة • Executives will probably never, ever, use EA models but they will always need the outputs • Provide what they need in a form that they like • Recognize Business Architecture for business planning is an emerging discipline • المديرون التنفيذيون لن يستخدموا نماذج هيكلية المؤسسات على الأرجح ، لكنهم يسعون دائما لنواتج المتأتية منها. • حاول توفير ما يحتاجون له في شكل يمكن أن يروق لهم. • الاعتراف بمعمارية وتخطيط الأعمال كعلم وانضبات ناشئ.

  46. SOA Guidelines • Align architecture principles across lines of business by creating reference architectures • Centralize the creation of standards, policies, and processes • Select technical solutions and vendor partners that adhere to industry standards • Establish an enterprise data management function to define and monitor enforcement of data governance across governmental entities. • Enforce security policies at the data service layer with declarative policy definition centrally • The SOA approach should focus on high-value business processes • EA and SOA should be driven by multiyear strategic plans that integrate business and IT goals • Provide enterprise SOA training for managers and stakeholders as well as architects, developers, PMs, BAs, and QAs • Utilize a service registry to catalogue existing services and define processes to identify and submit potentially sharable services

  47. SOA Guidelines • Centralize SOA operations and support until greater maturity is realized • Deploy a Web services management solution for runtime policy enforcement through distributed policy enforcement points • Establish SOA goals and strategies that are tightly aligned with the business • Establish SOA goals, standards, policies, and procedures proportionate to your SOA maturity • Define clear metrics that are obtainable and can show your progress in maturing your SOA and EA efforts • Put repeatable and well-defined governance processes in place and capture metrics • Automate as many of the governance processes and collection of metrics as possible • Use a multiyear financial strategy to justify SOA investments • Consider central funding for services that are to be used across departments

  48. Service Design Best Practices • Service Size: Granular and not complicated • Self Contained and reflects a real life service rendered to consumers • Very well defined interface and contract • Stick to WS Interoperability standards and data types • There is no versioning support in WS*. You need to add version number to the Service namespace to make it part of the name. • Do not use code generation tools to generate a service interface. Always start with building the service interface first. • Internal Error Handling and Logging is essential • Clearly document the transaction behavior of the service

  49. Enterprise Message Data Model Canonical Data Model

  50. Composition vs. Orchestration • Oracle SOA Suite SCA-based architecture is all about composition of components together into an “integrated circuit” that might well be part of a bigger application. • Orchestration concerns the control of a process across multiple systems and people. That control involves branching, state management and human task flows. • One should use SOA composite for composition and BPEL for process orchestration.

More Related