PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL Coordinating Communities Brussels

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Agenda 1.Introduction and welcome 2.Current status and scope of TICC and PoACC 3.Current activities of the TICC 4.Current activities of the PoACC 5.TICC and PoACC Governance 6.AOB/Close Page 2

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Introduction Who are we? Introduce yourself! -Organization, affiliation -Short description of yourself -Role in PEPPOL -Expectations and reason for participation Page 3

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Ground rules & expectations for this morning’s session -Participate -Engage! -We’re looking forward to your constructive and well founded suggestions and input - No questions are stupid – only inactivity is… -Maintain a high level of activity Some goals for this morning: - Clarify and reach concurrence on: -Prioritizations -Tasks - Identify resource requirements - Establish high level plans Page 4

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Ground Rules (cont’d) Discussions over Powerpoint Concrete actions over unclear and fluffy visions Assumed responsibilities over no one in charge Laughsover an uncomfortable silence Page 5

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Setting expectations for the OpenPEPPOL TI & PoA coordinating communities (CC) and placing the CC’s in context – High level goals Page 6 -Capture and work on issues and change requests from our stakeholders - Operational – short / midterm perspective -Alignment with market trends and developments to further add value for our stakeholders - Strategic – long term perspective -Ensure cont’d success of PEPPOL - Adoption, marketing, information and communication key -Continue to build on networking as way of sharing work loads, engage and keeping focus on value creation -Facilitating and maintaining a reasonable balance between business, operational and technical aspects

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Context – the Eco System Page 7 Making E-Procurement work is a team effort – working together towards the goal of bringing best of breed solutions to our stakeholders based on available technical specifications and standards is key to success. E-SENS CEF Stakeholders: EU level consolidation and development project participants Interaction: change requests, long term development strategies, consolidation Stakeholders: De juro and De Facto standards organizations (SDO’s) Interaction: change requests, problem resolution, sustainability Stakeholders: Policy makers and agencies at EU level Interaction: change requests, policies, directives, sustainability Stakeholders: Governance & Life Cycle management EU level participants Interaction: change requests, policies (change mgmt, versioning, LCM, sustainability), directives Stakeholders: buyers, sellers, service providers and solution providers. Interaction: change requests, issues, support, training, information, communication OpenPEPPOL – facilitating e- Business in Europe through state-of-the-art solutions based on open solutions & standards. One agreement gives access to European wide business opportunities.

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL – Coordination Communities Page 8 Information & Guidance Basic support Issues On-boarding CC meetings Liaison Events Change Mgmt. Release Mgt. Core elements (e.g. PEPPOL BIS, SML registries, Transport protocols, validation tools etc.) Specifications & Building Blocks Lifecycle mgmt. & Governance Support & Development Adoption, Marketing & Alignment

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL – Coordinating Communities General goals with CC’s (revisited): -Identify and work on areas subject to improvement -Assist in the prioritization of tasks -Report success stories and concerns / issues -Divide and share labor -Assist in the take up and adoption of the PEPPOL network Page 9

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Current status - TICC 10

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL TICC – Status Page 11 Continuous Operation since september 1st > 40 Service Providers > 2300 Registrations in SML > Transactions (DIFI statustics by 2012)  OpenPEPPOL Transport Infrastrucure Agreements effective  4 PEPPOL Authorites (NO, SE, FR, DK)  SML services operated by BRZ  Sample Code SW CIPA release by DG DIGIT  PKI Service by DIGST  Busdox specifications resubmitted to OASIS

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No TICC PKI infrastructure Page 12 PKI solution for OpenPEPPOL TI-CC provided by Danish Agency for Digitation (DIGST) Current Situation: PEPPOL Test PKI infrastructure New PKI agreement with Symantec/Verisign to transfer from LSP Project to OpenPEPPOL – Backoffice Services now Complete ! Separate Test and Production Root-CA and Certificates Publication of new Root-CA and SML Central - February 2012 Service Provider obligation to support OpenPEPPOL Certificates March 2013 Appx. 6 week migration period Solutions testing starting beginning of February including SML services, CIPA, Oxalis, Silicone and other solution providers

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No TICC – AS/2 Support Page 13 To leverage existing implementations of AS/2 for transfer of Business Documents between AP and address: Interoperability issues Cross platform support Availabilty of commercial solutions Open source implementations Status: Draft PEPPOL spec – “Phase IN” Issues Metadata support Verify compliance with PEPPOL PKI solution

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Business Document Envelope - Why 1.Makes it possible for APs to route messages without access to the business content Always the same way of identifying sender/receiver and document type No namespace or versioning issues for APs Need-to-know principal for the function of routing 2.Can carry some of the infrastructure elements when using simpler protocols like AS2

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No SBDH Routing information Payload metadata Process/service scope Payload

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Activity: Issue business document Activity: Export in electronic format Result: E-document in original format Decision: Is transformation need? Activity: Transform e- document to the agreed exchange format Result: E-document in agreed exchange format Activity: Validate e- document Activity: Transmit e- document Activity: Receive e- dokument Result: E-document in agreed exchange format Decision: Is transformation needed? Activity: Transform to receivers inhouse format Decision: Is archiving of original format needed? Activity: Archive e- document in received exchange format Result: E-document in inhouse format Activity: Import into ERP/Workflow Activity: Look-up end point addresses and transport parameters Activity: Validate e- document No Yes No Yes No Issuer´s responsibility Receiver´s responsibility Often carried out by Service Provider

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Current status Verify CENBII Envelope requirement specification from an openPEPPOL perspective Deadline for requirements Map requirements to SBDH version 1.3 Based on the mapping result  1. Create an implementation guide for openPEPPOL 2. Or look for other solutions that meet requirements better If SBDH 1.3 supports the requirements: 1. Mid March - A draft specification of SBDH 2. Mid March - A new draft of the AS2 profile utilizing SBDH 3. March - mid April - Publich review within openPEPPOL 4. April - Approval Looking forward

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No TICC – Oasis BDX-R Page 18 The BDX-R Technical committe was rechartered in 2012 PEPPOL BusDox specifications have been resubmitted Ongoing discussions in TC related to conseptual definitions and usecases in different communities Objective to publish Oasis specifications for PEPPOL BusDox SML Specification PEPPOL BusDox SMP Specification PEPPOL BusDox START Specification Parrallel work on EBMS 3.0 support Need for resources in the TC

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No TICC Overview of CR Page 19 Support for AS/2 protocol between AP's Support for Business Document envelope Improved reporting on usage statistics from AP’s to OpenPEPPOL To support automatic reporting of usage of the PEPPOL infrastructure It is proposed that the level of detail is reduced to only aggregated numbers are reported giving information on the sum of documents sent/received for each document type. Enhanced certificate based validation of Receiving AP In DBX specifications it is required to support SSL encryption but it is not required to use a trusted certificate Mandate the use of trusted SSL certificates by all receiving AP’s in accordance with a selected “White list” defined or adopted by OpenPEPPOL. Include validation checks in sample implementations Remove of SMP lookup in receiving Access Points verification

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No TICC Goals for 2013 Page 20 Establish operational and well functioning TICC Working Groups (WG’s) on the following topics: Transfer of PKI. AS2 Transport Protocol support. Business Document Envelope (in cooperation with PoACC). Validation and conformance tools. Oasis BDXR activities. Further develop governance setup and organizational routines in order to handle TICC specific and general issues: Support issues and change requests. Establishing routines for recurring meetings and WG’s. Documentation, presentation and general information updates. Coordinate OpenPEPPOL Transport Infrastructure related activities in e- SENS.

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Current status - PoACC 21

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No PoACC– Specific tasks, overview Page 22 WG’s - Change management Technical Specifications Sample code Validation artefacts Information – supporting resources Release Management Reporting – Administration MC Meetings Community Events Risk management Quality assurance – validation support Specific tasks Recurring tasks

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL Post Award – Current activities - Overview Page 23 BII Core Invoice Requirement Mapping to National Formats in SE, NO and DK Comparison between current e-Invoice formats in DK – OIOUBL Invoice 2.01, SE – Svefaktura 1.0 and NO – EHF Faktura 1.6 and CEN BII 2 Important stepping stone in the PEPPOL BIS to CEN BII 2 upgrade assignment Run by: SFTI, DIGST and DIFI. Despatch Advise BIS Analyzis of requirements for and use of CEN BII 2 as spec for Despatch Advise. Run by: ICEPRO, SFTI, DIGST and DIFI. Message Level Response (MLR) Support för MLR based on the CEN BII 2. Run by: DIFI

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Post Award – e-Invoice Mapping The mappings and guidelines can be used for: Creation of translation/conversion tools Facilitating interoperability between existing well-established e-invoice formats A stepping stone in a migration towards a common e-invoice format Page 24

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Despatch Advise BIS Overall objective A common Implementation Guideline for the Despath Advise profile to be used in national context for the Nordic countries and PEPPOL Post Award. Goal: a collaborative generation of artifacts for implementation in national solutions and engagement of PEPPOL PostAward; Including Guidelines, Stylesheets, Codelists and Schematron Validation. Page 25

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Message Level Response (MLR) -Purpose: facilitates automated processing and handling of end-to- end scenarios -Based on CEN BII 2 MLR specs -Initial analyzis of requirements to existing specs ongoing (DIFI) Page 26

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Handling Change requests & Issues Page 27

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Terminology Page 28 PlanDesignRealize Manage (service) Evaluate Release management Governance Support Change. Configuration and Release management are all related to and cross dependent on Governance and Life Cycle management (LCM). LCM is the overarching principle. Release management is primarily the discipline used when changes are to be become operational. Support provides input to LCM and assists in keeping foxus value creation. Change management LCM

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Page 29 OpenPEPPOL 3-Tier Pilot Support Structure Service Provider, Systems integrator, Solutions Provider PEPPOL Authority PEPPOL Authority WP 1 External organization Support Product Management Open PEPPOL CC’s OpenPEPPOL CC’s 1 st Level: Support End Users, Maintain locally deployed solutions Primary support: Service Providers, Systems Integrators, Solutions providers – AP:s/SMP:s 2 nd Level: Support level 1 providers. Primary support: PEPPOL authorities. Secondary support: OpenPEPPOL’s Coordinating Communities (CC). 3 rd Level: Support and Update PEPPOL elements OpenPEPPOL’s CC’s or external organization PEPPOL elements support SP support End User Support OpenPEPPOL CC’s

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Support Work Flow Guiding principles: OpenPEPPOL provides 3rd level support Keep it simple All support issues must be: Logged (entered into Jira – classified and prioritized) Closed (not open for more than xxx weeks? Months?) A predetermined # of resources are identified External resources are spent only when needed Report to set Enter Into Jira Assess: -Classify -Prioritize -Allocate -Plan -… Report back to Stakeholder Update Jira Act on Support Issue Execute, depending on -Type of issue -Time-to-resolve -Complexity -Resource (internal -/ external) Document & Communicate

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Support issues - legend 1.The service providers constitute first (1st) line of support 2.Support issues are sent to the following -adress: 3.All issues are entered into Jira with the following information: Date, Submitted by, Description, Classificiation *, Criticality *, Resolution *, Resource *, Ready by *, Expected completion *, Open/Closed * * - To be entered when initial impact assessment has been made 4.All issues are initially assessed by the CC Leader. If the issue in question is of the nature that it requires further analysis and/or external resources to be addressed, it should be handled by the OpenPEPPOL Management Committee. 5.The status and and the subsequent action of the support issue (manifested as a ”support ticke”) is communicated back to the submitter of an issue Page 31

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Support issues – principles (cont’d) 5.The approach is ”multi layered” according to the following principle: Level 1 support: provided by the end user’s Service Provider. SLA according to invidual agreements. Level 2 support. Through PEPPOL authorities. SLA none. Level 3 support: OpenPEPPOL, through dedicated -address. SLA none. Page 32

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Looking ahead! Page 33

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Challenges Common: 1.Organizing and recruiting members to Work Groups Resources 2.Prioritizing 3.Planning and executing the actual work 4.Transition /from one version to another/ - re PEPPOL BIS upgrade Release management Updating contracts Page 34

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Assignments 2013 – Post Award 1.MLR - End-to-end communication (Recipients) jointly with TI-CC 2.Standard Business Document Header (SBDH - CEFACT), Business Document Envelope (BII 2) jointly with TI-CC * 3.New PEPPOL BIS - support for Despath Advise 4.PEPPOL BIS 2.0  CEN BII 2 upgrade 5.Forum for Service Providers’ Purpose: to facilitate easy cross service provider communication, for problem mitigation and error resolutions 6.Validation tool consolidation 7.Information upgrade 8.Adoption and marketing Page 35 * - Related to / included in the AS2 TICC effort

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Planning -PEPPOL BIS upgrade Current mapping (re BII Core Invoice Requirement Mapping) important first step WG for PEPPOL BIS to assume responsibility for PEPPOL BIS upgrade? Other steps to take? Challenges to tackle: Seemless transition from one version of PEPPOL BIS to another Challenges: Contract updates Tentative planning: Project plan and project team ready by end of February Actual work continued / initiated Q Public review by Q Transition and release by Q Page 36

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No OpenPEPPOL organisational model Page 37

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Coordinating Communities are free to adopt their own internal procedures for governance Decision making, election and appointment procedures can be agreed within the CCs, Not necessarily uniform across CCs Each Coordinating Community must appoint a Leader, who becomes a member of the OpenPEPPOL Managing Committee. Current CC Leadership: Transport Infrastructure CC: Sven Rasmussen (DIGST appointed at the time of establishment by OpenPEPPOL founding Members Post-Award CC: Anders Kingstedt (ESV), appointed at the time of establishment by OpenPEPPOL founding Members Page 38 Current CC Governance Status

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No As Members of the Managing Committee, CCLs are expected to: Attend regular MC meetings (currently in a weekly basis) and perform shared tasks as decided by the MC Their organizations must carry the costs associated with their role CC Leaders must be representatives of a PEPPOL Authority If no such candidates exist, CC Leaders from public organizations may be appointed Candidacies from private organizations may be considered only if No candidacies from PEPPOL Authorities or other public organizations are presented Sufficient assurances on market neutrality and willingness as well as ability to invest in the CCL role have been provided to the Managing Committee Page 39 CC Leadership Criteria

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Current CC Leaders are standing for re-appointment by their CC Members Transport Infrastructure CC: Sven Rasmussen (DIGST0 Post-Award CC: Anders Kingstedt (ESV) No other candidacies have been declared (deadline for notifications was Jan.25 th, 2013) The Transport Infrastructure and Post-award Coordinating Communities are asked to confirm the re-appointment of their current CC Leaders as the only candidates standing for the positions. Page 40 Appointment of CC Leaders

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Engage! Page 41

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Work Group members wanted! -As a OpenPEPPOL member and WG participant you can: - Influence the future of PEPPOL - Provide (and share) expertise - Assist in fast tracking issues relevant to OpenPEPPOL and Post Award -Recurring Post Award Coordinating Community provides opportunities for information sharing and knowledge transfer -Contact Anders Kingstedt, PoACCL or Sven Rasmussen TICCL for more information. Page 42

PEPPOL is an EU co-funded project CIP-ICT PSP-2007 No Page 43 eProcurement without borders in Europe