peppol bii workshop n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
PEPPOL BII workshop PowerPoint Presentation
Download Presentation
PEPPOL BII workshop

Loading in 2 Seconds...

play fullscreen
1 / 68

PEPPOL BII workshop - PowerPoint PPT Presentation


  • 209 Views
  • Uploaded on

PEPPOL BII workshop. PEPPOL Conference Malmø February 11 th 2010. Who is who? CENBII Introduction CENBII Profile concept and architecture ePrior (example of implementing CENBII) Lunch Document concepts and architecture Pre awarding documents Post awarding documents Guidelines.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'PEPPOL BII workshop' - aelwen


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
peppol bii workshop

PEPPOL BII workshop

PEPPOL Conference

Malmø

February 11th 2010

agenda for today

Who is who?

  • CENBII Introduction
  • CENBII Profile concept and architecture
  • ePrior (example of implementing CENBII)
  • Lunch
  • Document concepts and architecture
  • Pre awarding documents
  • Post awarding documents
  • Guidelines
Agenda for today
who are we
Who are we?

Peter L. Borresen

Georg Birgisson

Editor of CENBII WG1

Director of Eykur

  • Chairman of CENBII
  • Director of ebConnect
  • Associated director of Document Engineering Sevices
cen workshop on business interoperability interfaces in public procurement in europe
CEN workshop on Business Interoperability interfaces in Public procurement in Europe
  • Messagecontent and business process
  • UBL-UN/CEFACT convergence
  • Toolbox
  • Pilot support
background
Background
  • IDABC initiatives on eProcurement
  • NES
  • CODICE
  • CIP i2010 roadmap pilot projects
  • Danish cost savings initiatives
vision
Vision
  • To save administrative costs 12-20 minutes pr. invoice
  • To lowen the prices with a real common electronic marked
  • To raise the quality of the business transactions
  • To agree on common interpretation of the EU directives
  • To create non-system depended interoperability.
objectives
Objectives
  • Interoperability
  • Harmonization
  • Prove it!
objectives full text
Objectives (full text)
  • To identify and document the required business interoperability interfaces related to pan-European electronic transactions in public procurement expressed as a set of technical specifications developed taking due account of current and emerging UN/CEFACT standards in order to ensure global interoperability
  • To co-ordinate and provide support to pilot projects implementing the technical specifications in order to remove technical barriers preventing interoperability.
interoperabillity
Interoperabillity

Proces level

Data level

Technical level

which parts addresses interoperabillity
Which parts addresses interoperabillity?

Part 4

Part 1

Semantic

& process level

Interoperability on

different levels

Syntax level

Part 1 + Part 2

Technical level

Part 3

cenbii is mainly a semantic definition with pontential many implentations
CENBII is mainly a semantic definition with pontential many implentations

CENBII

EDIFACT customization

e.g. EANCOM

EDIFACT customization

e.g. EANCOM

EDIFACT customization

e.g. EANCOM

CENBII implementation

e.g UBL

CENBII implementation

e.g UBL

EDIFACT

CENBII implementation

e.g UBL

the cenbii deliverables
The CENBII deliverables

Part 0: Introduction

Part 1:

Profile Overview

Part 2:

UBL-UN/CEFACT convergence

Part 3:

Toolbox

Part 4:

Pilot support

Publication at: http://www.cen.eu/cwa/bii

business interoperability interfaces for public procurement in europe
Business Interoperability interfaces for Public procurement in Europe

Part 4

Part 1

Semantic

& process level

Interoperability on

different levels

Syntax level

Part 1 + Part 2

Technical level

Part 3

what is a cenbii profile
What is a CENBII profile?
  • A profile of a business process
  • A CENBII profile is a orchestration of exchanged documents between two business parties
  • A CENBII profile can be used to form an collaboration agreement
  • A CENBII Profile can be broken down to collaborations
  • To form a full procurement process, more profiles my be needed
the evolution of profiles
The evolution of profiles
  • OIOUBL
    • Denmark public authorities
    • 2005
  • NES - North European Subset
    • North European and UK cooperation
    • 2007
  • BII – Business Interoperability and Interchange
    • European specification , published by CEN
    • December 2009
    • Contains all NES profiles in upgraded version
profile key components
Profile key components
  • Business process
    • Specification of an electronic business process.
  • Collaboration
    • Generic sub processes that can be linked together to form business process
  • Transaction
    • A set of data (information) sent from one partner to another, relevant to an activity within the process
a business party in a profile may have more than one role
A business party in a profile may have more than one role

Ordering

Buyer

Seller

Billing

Debitor

Customer

Customer

Debitor

a profile consist of reusable components
A profile consist of reusable components

Business Process

Profile

Collaboration

Transaction

Document

profile migration
Profile migration

BII04 Invoice only

Invoicing

BII05 Billing

Invoicing

Dispute resolution

BII03 Ordering

Ordering

BII06 procurement

Ordering

Invoicing

Dispute resolution

more profiles
More profiles

Catalogues, statement, ofl.

Tendering, support tools

BII10 - Tender Notification

BII11 - Qualification

BII12 - Tendering Simple

BII14 - Prior Information Notice

BII22 - Call for Tender

BII24 - Attachment Document

BII25 - Status Request

BII26 - Retrieve Business Document

  • BII01 - Catalogue only
  • BII02 - Catalogue update
  • BII17 - Multi party catalogue
  • BII16 - Catalogue deletion
  • BII23 - Invoice only with dispute
  • BII09 - Customs Bill
  • BII15 - Scanned Invoice
  • BII18 - Punch-out
  • BII20 - Customer Initiated Sourcing
  • BII21 - Statement
the players
The players
  • Business partners
    • The participants in business process. In procurement these are the Customer and the Supplier. Business partner are the responsible parties for the process as whole
  • Role
    • Roles change depending on the activity in the process
  • Party
    • The entity that carries out a role. Parties are the business partners themselves or work under their authorization.
roles and actors
Roles and actors

Business partner

Role

Party

Party

Role

Business partner

Customer

Purchasing authority

Economic operator

Suppler

Purchasing

Receiver

Dispatcher

Delivery

Debtor

Creditor

Billing

Payer

Payee

Settlement

document architecture
Document architecture
  • What is a business document?
  • CCTS
  • CCTS data types
  • Core document components
  • Customization and syntax mapping
what is a business document
What is a business document?
  • A formal exchange of a defined set of business information
  • Can serve to prove a status of a business process
  • Business documents are often backed up by legislation and partner agreements.
  • Business documents need a level of standardization
core components technical specification
Core Components Technical Specification
  • Technology independent (only aggregation)
  • Data types based on Simplification of XSD data types

Document

ABIE

ACC

ASBIE

BBIE

Type

ASCC

BBCC

Attribute

ccts data types

Numeric

  • Amount
  • Quantity
  • Identifier (ID)
  • Name
  • Text
  • Meassure
  • Rate
  • Percent
  • Binary objects
  • Value
  • Decimal
  • Date
  • Time
  • DateTime
  • Code
CCTS Data types
some important attributes in types
Some important attributes in types
  • currencyCode (Amount)
  • languageID (Name, Text)
  • unitCode (Quantity, Messure)
  • schemeID (Identifier)
  • schemeAgentcyID (Identifier
  • listID (CodeType)
  • listAgentcyID (CodeType
  • mimeCode (BinaryObject)
customization
Customization
  • In some contexts the core components contains two much information
  • An implementation can choose to restrict components for the whole subset
cenbii contextualization of address
CENBII Contextualization of address

Party PostalAddress

Delevery/Location/Address

StreetName

Additional StreetName

BuildingNumber

Department

  • ID
  • Postbox
  • StreetName
  • Additional StreetName
  • BuildingNumber
  • Department
subset customization
Subset customization

Core Invoice, Party

Full Invoice, Party

standard vs customization
Standard vs. customization
  • The standard is the “raw” material
  • The customization defines a subset of the stadard of which it will use
  • The customization defines a particular use of the standard
  • A standard is defined by a syntax. Validated by XSD
  • A customization is defined by a set of document models, codelist and business rules. Validated by Schematron (2nd pass validation)
cenbii validation strategy

Definition

Runtime

Application

(value) level

Application dll

Application validation

3rd pass

CENBII validation strategy

Industry schematron

Geopolitical schematron

Document XSLT

2nd pass

Semantic

level

Profile schematron

Subset schematron

Syntax

level

Standard schemas

Standard schemas

1st pass

exampel validation of an id

Application

(value) level

Application validation

Look up the ID in a webservice

Exampel: Validation of an ID

Id must be the same as in Contact/ID

Industry schematron

Geopolitical schematron

Id must be a VAT number

Semantic

level

Profile schematron

Id is mandatory

SchemeID and SchemeAgentcyID mandatory, SchemID must be in a list

Subset schematron

Syntax

level

Standard schemas

ID must not contain spaces (XSD:token)

levels in business rules
Levels in business rules
  • Profile level rules
    • How the exchange of a transaction affects the partners’ obligations
    • How information in transactions interacts with external information such as contracts
    • Definition on how update transactions affect exciting data
  • Collaboration
    • Process rules
    • Information constraints
  • Transaction rules
    • Information constraints
information constraints
Information constraints
  • Data element cardinality
    • Optional becomes mandatory in a given context
  • Data element Interaction
    • Formulas, e.g. B = sum of all A’s
    • Dependency, e.g. if A then B
    • Relationship, e.g. A > B
  • Data element values
    • Min, max or range
    • Allowed values, specified by code list
syntax mapping
Syntax mapping
  • CENBII is said to be syntax neutral
  • A syntax mapping is the operational (runtime) version of CENBII
  • Currently only syntax mapping to UBL exists
  • No syntax mapping fulfills the whole specification
  • Syntax mapping is a issue for CENBII2

OASIS UBL

CENBII

UN/CEFACT

business documents pre awarding
Business documents, Pre awarding

I want to show you some slides

business documents post awarding
Business documents, Post awarding
  • Sourcing
  • Catalogue profiles (BII01, BII02, BII16, BII17)
  • PunchOut (BII18)
  • CutomerInitiated sourcing (BII20)
  • Procurement (BII06)
  • Procument with invoice dispute (BII07)
  • Advanced procurement with dispute (BII08)
  • Advanced procurement with dispatch (BII13)
  • Advanced procurement (BII19)
  • Ordering
  • Basic Order only (BII03)

Procurement

  • Basic invoice only (BII004)
  • Billing (BII05)
  • Scanned invoice (BII15)
  • Billing with dispute and reminder (BII08)
  • Billing
  • Customs Bill (BII 09)
  • Statement (BII 21)
  • Attached Document (BII24)
  • Status Request (BII25)
  • Retreive Business Documents (BII26)
  • Support
catalogue exchange
Catalogue exchange
  • The Catalogue documents are documents to synchronize two parties catalogues
  • The sender may not be the seller, but can be catalogue provide e.g. a web site

Catalogue

exchange

Contractor

Seller

Catalogue provider

the core catalogue
The Core catalogue

http://spec.cenbii.eu/Profiles/Data/html/CoreTrnsDm/BiiCoreTrdm019%20Catalogue;%201.0;%20CENBII/D1.htm?http://spec.cenbii.eu/Profiles/Data/html/CoreTrnsDm/BiiCoreTrdm019%20Catalogue;%201.0;%20CENBII/D5.htm

thank you for your time
Thank you for your time

We hope to see you in the CENBII2 workshop

Learn more:

www.cen.eu/cwa/bii

plb@ebconnect.dk

georg@eykur.is