260 likes | 407 Views
Modeling and PIC Governance. Ralf Herzog AP OP QSPG, SAP AG Version 1.0.0 November 23, 2005. Revision Log. Concept. Models for Product Definition and Implementation. Integration View. Internal Functional View. Product View. High-Level Model. Platform map.
E N D
Modeling andPIC Governance Ralf HerzogAP OP QSPG, SAP AG Version 1.0.0 November 23, 2005
Concept Models for Product Definition and Implementation Integration View Internal Functional View Product View High-Level Model Platform map Integration scenario catalog Functional building blocks, F&F ApplicationPlatform Portfolio View Deployment units with their BOs Processinteraction map Requirement specification for new platform development Business Model View Implementation View Cross-deployment unit process integration Specification/design BO Models and ESR • BOs, Nodes, Elements • XI messages (A2A/B2B) • Choreograph messages for each process interaction • Agents, interfaces, message data types Detailed Model
Invent Define Engineer & Develop Deploy High Level Modeling Functions & Features Portofolio Cases Design (SDD) Define Phase Detailed Modeling Specification (SRS) Unittests Documentation Configuration Software Engineer & Develop PIL@AP Development Model Roll-In = Define Modeling = Implementation = Test Validation
IP Secure Intellectual Property ProcessIntegrationContent – Modeling and Governance • Modeling Processes take place early in development • Governance processes ensure engineering excellence • The Iterative approach covers all externalized aspects of a business object Change Requests Change Requests Business Object PIC node structure actions, interfaces .. elements Platform Portfolio Implementation and Rollout PIC0 PIC1 PIC2 PIC3 mySAPconsol. Business ObjectCoordination GDT PIC High-Level Modeling Detailed Modeling Alignment: mySAP/A1S/B1[as of Release 2] Community Process
Process Gates PIC 0 and PIC 1,2,3 IntegrationScenarioStructure ESA EntityIdentification& Cut ServiceOrchestration PIC 01 PIC 02 PIC 03 Identification of BO’s,PC’s, DU’s(Name and Semantics) Identification of PC’s and PCinteractions within Integration Scenario(Name and Semantics) Identification and cut of Service Operations andInterfaces within PC interaction(Name and Semantics) ChangeRequests PIC 03approval of PCIM’s (Interfaces and Serv.Operations) requiredto start PIC 3 PIC 01approval Required tostart PIC 1 NodeStructure Actions, Queries, Interfaces Elements PIC 1 PIC 2 PIC 3 GDT’s Assignment GDT’s to BOnodes Definition of Actions, Queries, compoundservices GDT PIC Definition of Node Structure of BO Detailed Definition of Global Data Types
Process Modeling – PIC0 Business Object Modeling – PIC 1-3 Global Data Type Modeling – GDT PIC Further Readings
Step 1. Identification and Structuring Step 3. Definition of Service Orchestration From business scope to high quality implementation in a structured and efficient way • Portfolio/Scope • Functional Building Blocks • Features & Functions • Integration Scenario Catalog BO/DU Map Level 1: Deployment UnitLevel 2: Process ComponentLevel 3: Business Object Step 2. Integration Scenario Overview Integration Scenario Model “Circuit Diagram” Process Components and their interactions Governance Process PIC0 Service Orchestration Process Component Model / Process Component Interaction Model A2A & B2B Services, Process Agents, • Content Governance • BO Modeling • Operation SignatureModeling
P2Dsign offSAP Mgmt AP Mgmtfinalapproval Governance Process for Process Integration Modeling KEY MESSAGE The BO, PC and DU identification is part of a Governance Process PIC0. Only Objects that have passed the process will be part of the Enterprise Services Repository. In scope of this Governance Process are Core BOs, Replicated BOs, PCs and DUs. Other Object Types such as Maximal BO Modeling Templates, Adapted Objects, Dependent Objects, Business View Objects are not subjects of the Governance Process for Object Identification. A dedicated Governance Process for these Objects is currently under discussion. Developmentpreparescontent, coachingby Gov. team AP ArchitectsReview AP Management Review Gov. TeamGate AP ArchitectsGate AP MgmtGate AP Review Process SAP-wide ReviewProcess for Integration Scenarios BO PIC (1-3)
Process Modeling – PIC0 Business Object Modeling – PIC 1-3 Global Data Type Modeling – GDT PIC Further Readings
Goals of the Governance Process for Business Objects (BOs) consistency of semantics across development units reuse wherever possible similar treatment of similar objects (customer invoice – supplier invoice) identical modeling and documentation rules => “high quality” Business Process Platform (from a conceptual viewpoint) P2D Dev Close BO PIC Governance Governance Coaching, Steering, Approval Implementation Scoping, Identification Definition • Business Objects • Elements • Interfaces / Operations PIC 1 PIC 2 PIC 3 PIC0 Structure Elements Final
Governance Process for Process Integration Content documentcreation Owner and Integration Expert AP OPS BO Experts Coaching Team Review feasible? Review Part 1 Escalation Critical Issue? Review Part 2 Final Document created Sign-Off Phase Document Accepted? Objections PIC Meeting SAP wide Review Document Accepted? PIC Final Release
Governance Process for Process Integration Content Creation of document according to guidelines Inform owner + experts about review details If coaching within 7 days is not feasible BO Owner can start PIC Review without coaching Review feasible? Check by coach 7 days • Discussion in Q&A document • monitoring by Coaching Team Review by experts Every 2 weeks status report to SVPs Adress questions in Q/A Escalation Inform SVP Critical Issue? Check by owner 7 days Review and Sign-Off Phase for Frontrunner II BOs only 7 days overall Bilateral Clearing Phase Final BO Document created 7 days Sign-Off Phase Objections? ConsolidationOpen Issues PIC Scheduling Document Accepted? Check by AP OPS PIC Meeting Open Issues ≤ 7 days Translation ok? Check by owner Owner triggers translation after sign-off and finalization of document 7 days SAP wide Review (only PIC 1 + 3) AP OPS 14 days BO Experts Document Accepted? Check by AP OPS Coaching Team Owner and Integration Expert PIC Final Release
Governance & Guidance by Coaching Team Approval by Process Integration Content Council (PIC) Business Objects / Nodes / Operations Data Types Methodology Business Objects / Nodes / Operations Data Types PIC Governance Process and Roles for Business Objects D Methodology Council: Methodology, Design Rules, Procedure Model A B C Development by Project Integration Experts / Content Owner Organizational structure with roles and tasks (A – D, details see BO Guideline)
Process Modeling – PIC0 Business Object Modeling – PIC 1-3 Global Data Type Modeling – GDT PIC Further Readings
GDT Overview / Goals • Business objects and operations are hierarchically structured. • Elements of a BO or an operation are uniformly described by data types known as “Global Data Types” (GDT). • Global data types are based on a set of basic types, known as core component types (CCT). Core component types were defined by the UN/CEFACT in the ebXML framework and are based on the XML Schema • If the same semantic subject appears in (leaf) elements, it is always characterized by the same Global Data Type. GOAL of the GDT PIC-process is to harmonize GDTs SAP-wide
Development by Project Guidance by Coaching Team Review by Process Integration Content Council (PIC) Integration Experts Communication Interfaces Data Types Communication,B2B/A2A Interfaces Global Data Types • Registration at Coaching Team • Communication Review PIC1 • Review of GDTs • Quality Check PIC Process and Roles Coaching and Guiding Invent Define Develop Deploy Optimize
GDT PIC Governance Design of GDT according to guidelines If coaching within 7 days is not feasible GDT Owner can start PIC Review without coaching Review feasible? Check by coach Inform owner + experts about review details Review by experts Every 2 weeks status report to SVPs Escalation to BOT or DCM Review accepted? Final GDT document Creation of GDT in X3R Initiate translation of GDT SAP wide review Document Accepted? AP OPS Update GDT catalogue Experts Coaching Team GDT Owner
Process Modeling – PIC0 Business Object Modeling – PIC 1-3 Global Data Type Modeling – GDT PIC Further Readings
Further Readings • Process Modeling and PIC0 • Guidelines • ESA Modeling Handbook • Content Creation Guideline • Naming Rules for Operations and Interfaces • ARIS Business Designer and Web Designer • Templates • Changerequest Template and Change Process • (can also be found in SAP Portal : AP Engineering Process Modelling) • BO Modeling and PIC1 – PIC3 • Guidelines: \\dwdf029\ap_eng\Content_Governance\40_Guidelines\BO_Guidelines • Templates:\\dwdf029\ap_eng\Content_Governance\10_Business_Object_Governance_&_Coaching\40_Template-and-Pattern • GDT Modeling and GDT PIC • Guidelines: \\dwdf029\ap_eng\Content_Governance\40_Guidelines\GDT_Guidelines • Templates: \\dwdf029\pic-coaching\100_ESA_BusinessObjects\00_GDT_Templates • Templates can be found also in the AP Portal Quality&Standards Templates
Process Modeling – PIC0 Business Object Modeling – PIC 1-3 Global Data Type Modeling – GDT PIC Appendix