PIC Council Charter Jürgen Wagner, Friedhelm Krebs SAP AG Version 1.1 April 26 th, 2004
PIC Council Charter Mission of PIC Council Its mission is to guarantee quality of process integration content by reviewing interfaces and data types for semantic correctness ensuring conformity to international standard encouraging reuse of data types establishing SAP-wide consolidation continuously improving the Integration Guidelines. PIC Council feels committed to a seamless and continual quality assurance from modeling via design and documentation to shipment, all based on XI repository Tasks Approval of GDTs and interfaces according to rules and guidelines Identify needs for methodology, rules and guidelines and propose working groups Approval of methodology, rules and guidelines SAP AG 2002, Title of Presentation, Speaker Name / 2
Input for PIC Council Integration Scenario Description Component view or Activity diagram GDTs Semantic description Structure Interfaces Rough structure description (class diagram) Semantic description Structure of underlying Message Data Type Master language is German due to necessity on semantically precise descriptions SAP AG 2002, Title of Presentation, Speaker Name / 3
Deliverables of PIC Council PIC Council reviews and approves: GDTs Semantic description Structure Interfaces Naming Semantic description Structure of underlying Message Data Type Reviewed objects (semantic description and structure) must not allow any freedom of decision during implementation phase. Semantic description of GDTs and Interfaces is provided as MS- Word-document and is taken as raw documentation for KW. Review of structure of Data Types is based on implementation in XI repository, namespace SAPGlobal (see appendix) SAP AG 2002, Title of Presentation, Speaker Name / 4
PIC Council Members Permanent members (role oriented) per Org Unit Facilitator (from XI Content Services) Verifier (from XI Content Services) Up to three integration experts per BSG with business scope, covering all industries BSG M BSG S BSG F AP&A / Vienna XI expert (from XI Content Services) Coaching team Open Standard expert (from NW Open Standard) Guideline owners Guests Project representative / GDT owner Members are assigned by their Org Units. Participation is mandatory to assure continuity and presence of a quorum. Distribution List DL XI PIC SAP AG 2002, Title of Presentation, Speaker Name / 5
PIC Council working mode Schedule Two regular meetings per week (2h + 1.5h) Third meeting on demand (1.5h) Agenda Planned agendas are published via meeting invitation two days in advance Agenda contains topics with estimation of duration and link to original documents Every PIC Member can submit agenda proposals Information All PIC related information is accessible via http://intranet.sap.com/xi-content Additionally minutes are published via Mail (DL XI PIC PROTOCOL + Guests) Escalation Escalations to PTB via Peter Lorenz Sponsors are Peter Zencke and Klaus Kreplin SAP AG 2002, Title of Presentation, Speaker Name / 6
Roles and tasks Tasks of facilitator Manage and publish agenda pipeline Be responsible for keeping the agenda Keep discussions in the scope of the agenda Terminate discussion, if discussion seems to exceed estimated duration according to agenda Discussions shall be limited to questions of understanding and not grow into solution finding Take minutes and publish minutes Tasks of verifier Track and publish results of working groups for methodology, rules and guidelines topics Track and monitor status of GDTs and Interfaces (namespace SAP Global only) (not yet possible) Track and monitor status of GDTs and Interfaces with postponed approval SAP AG 2002, Title of Presentation, Speaker Name / 7
Roles and tasks Tasks of coaching team (with respect to PIC Council) Send agenda topics timely to meeting owner to enable pipeline management Present consolidated proposals with good chance of broad consensus Organize offline meetings, if proposal does not meet general approval and voting is not possible Tasks of guideline owner Elaborate guidelines and present for approval on demand on it s own initiative Guideline owner for: Communication Paradigms tbd (see appendix) Interfaces: Michael Seubert Global Data Types: Jürgen Wagner SAP AG 2002, Title of Presentation, Speaker Name / 8
Roles and tasks Tasks of integration experts Meeting preparation Study documents in advance Send comments or objections to document owner and coaching team timely Meeting Check GDT against guideline Check interface against guideline Check usability in own application Check comprehensibility of documentation SAP AG 2002, Title of Presentation, Speaker Name / 9
Roles and tasks Tasks of project representative / object owner Project representative has to provide input for PIC meetings timely Project representative and coach decide, when to present to PIC meeting Object owner has to create GDTs / Message Data Types in namespace SAPGlobal Object owner or project representative has to inform verifier, if GDTs / Message Data Types are defined in namespace SAPGlobal according to final review Emergency fallback (exception!): If an interface cannot be reviewed in time, and thus the project delivery dates are endangered, the Project Steering Committee may decide to withdraw the interfaces and switch to Component Interfaces instead. This decision has to be justified during Dev2Prod Handover Meeting. Those interfaces will be published in SAPNet and tracked: Proposals have to be submitted to the next release. SAP AG 2002, Title of Presentation, Speaker Name / 10
PIC Council working mode Voting A vote is taken, if further argumentation doesn t help coming to an agreement and if delegating to a working group wouldn t provide any further progress. Every PIC member can request a vote be taken. Each of the following BSGs has one vote: BSG M BSG S BSG F AP&A / Vienna Each of the following development units has one vote: NW Open Standards Coaching Team XI Content Services Delegates from any five out of these seven units are required to make a quorum. Vote may be taken immediately, if a quorum is present and if nobody contradicts; otherwise votes have to be announced one meeting in advance. An absolute majority of four votes is required to approve a proposal (even if several alternatives have been proposed). Results of a vote regarding content can not be made against the owners opinion. If no compromise is possible, the SVPs of the involved units have to agree on the further proceedings. If necessary the owner has to switch to Component Interfaces. Results of a vote regarding methodology are mandatory for all parties. SAP AG 2002, Title of Presentation, Speaker Name / 11
PIC Council Charter New participants Additional Development Areas (in the sense of the previous slide) may apply for permanent membership Voting rules are to be adopted appropriately Change Management Everybody is invited to suggest improvements Changes in scope have to be approved by PTB Changes in proceeding may be decided by PIC Council with majority; sponsor is to be informed SAP AG 2002, Title of Presentation, Speaker Name / 12
PIC Council Charter Authorization PIC Council as a regular meeting has to be seen in the context of PIC Governance, supporting Product Standard Application Integration & Interfaces PIC Governance is committed by PTB and DMT and was announced and started in Dec 2002: governance_process_xi_200212.ppt SAP AG 2002, Title of Presentation, Speaker Name / 13
Appendix Appendix Open Points Mappings Scenarios Documentation Tool Usage during approval steps till now in future (subject to proof of concept) Abstimmregeln (deutsche Version) SAP AG 2002, Title of Presentation, Speaker Name / 14
Open points Mapping of Interfaces to external standards Mapping is considered during coaching time Coaching Team offers conceptual advice for mapping, project delivers document with mapping concept PIC Council does not review mapping concept, but takes for granted SAP AG 2002, Title of Presentation, Speaker Name / 15
Open points Scenarios Scenarios are designed by application architects and are presented in PIC for information purpose PIC Council does not review scenarios for the time being Further considerations regarding scenario reviews will take into account the initiative of Thomas Reiss It has to be clarified whether communication choreography is reviewed It has to be clarified whether communication paradigms and guidelines are to be provided by Stefan Kaetker and/or Günther Pecht-Seibert SAP AG 2002, Title of Presentation, Speaker Name / 16
Open points Documentation Documentation is available as Word file Concept for translation and shipment under construction SAP AG 2002, Title of Presentation, Speaker Name / 17
Appendix: Steps for approval (till now) Approval of interfaces and GDTs is done in three PIC meetings with different scope and input PIC 1 Scenario Component view in Powerpoint Interface structure Semantic description in Word Top down refinement PIC 2 PIC 3 GDTs Complete Interface Interface structure description in Visio (low granularity) Semantic description in Word GDT structure in Excel Full semantic description including integrity conditions in Word Interface structure description in Visio (low granularity) Detailed GDT and interface structure in Excel None of these documents are shipped to customers SAP AG 2002, Title of Presentation, Speaker Name / 18
Appendix: Steps for approval (in future) Approval of interfaces and GDTs is done in three PIC meetings with different scope and input PIC 1 Scenario Component view in Powerpoint Interface structure Semantic description in Word Top down refinement PIC 2 PIC 3 GDTs Complete Interface Interface structure description in Visio (low granularity) Semantic description in Word (KW template) GDT structure in Interface Repository Full semantic description including integrity conditions in Word (KW template) Interface structure description in Visio (low granularity) Detailed GDT and interface structure in Interface Repository As proof of concept approval of Message Data Type and GDT structure of CreditManagement is based on Interface Repository SAP AG 2002, Title of Presentation, Speaker Name / 19
PIC Council working mode Abstimmungen Es wird abgestimmt, wenn trotz Austausch aller Argumente keine Einigung erzielt werden kann und die Auslagerung in eine Arbeitsgruppe keinen Fortschritt mehr verspricht. Jedes Mitglied kann eine Abstimmung beantragen. Abstimmberechtigt ist jeder der Entwicklungsbereiche mit jeweils einer Stimme: BSG M BSG S BSG F AP&A NW Open Standards Coaching Team XI Content Services Zur Beschlussfähigkeit müssen fünf der sieben Bereiche vertreten sein. Abstimmungen können sofort durchgeführt werden, wenn das Gremium beschlussfähig ist und niemand widerspricht; ansonsten müssen sie ein PIC Meeting vorher angekündigt werden. Zur Annahme eines Vorschlages ist die absolute Mehrheit von vier Stimmen erforderlich (auch bei Einreichung mehrerer Alternativen). Abstimmungen zum Content können nicht gegen den Willen des Owners durchgesetzt werden. Falls sich kein Kompromiss finden lässt, müssen sich die SVPs der betroffenen Abteilungen auf das weitere Vorgehen einigen. Nötigenfalls muss der Owner auf Component Interfaces ausweichen. Abstimmungen zur Methodologie sind verbindlich für alle Beteiligten. SAP AG 2002, Title of Presentation, Speaker Name / 20