eNotification European Message Standard for Public Procurement Notification

1
e-NotificationEuropean Message Standard for
Public Procurement Notification

• Business Requirements SpecificationIntroduction

2
Table of Contents

• Context of the project
• Introduction to the BRS and its modelling method
• Details of the work
• Discussion and comments

3
e-Notification Objectives

• Creation of a CEN (UN/CEFACT) standard
• Standardise the European messages in the Public
  Procurement domain, which are exchanged between
  contracting entities and official publication
  bodies or between publication bodies
• Define consistent e-Notification processes.

4
e-Notification Requirements

• A UN/CEFACT standard requires
• Business Requirements Specification (BRS)
  according to UN/CEFACT Modeling Methodology (UMM)
• Requirements Specification Mapping (RSM)
  according to the ebXML Core Components and
  UN/CEFACT naming and design rules for XML

5
e-Notification Approach

• Comply with UN/CEFACT e-Tendering standard of
  TBG 6, as far as appropriate.
• UN/CEFACT e-Tendering standard (10/2006) used as
  formal template for BRS and RSM
• First phase BRS
• Business context description for all EU forms
• Business document description restricted to 4 EU
  formsPrior Information Notice, Contract Notice,
  Contract Award Notice and Cancel Corrigenda
  notice

6
EU Forms (1)

• F1 Prior Information Notice
• F2 Contract Notice
• F3 Contract Award Notice

F4 Periodic Indicative Notice F5 Contract
Notice - Utilities F6 Contract Award Notice
Utilities
F13 Results of Design Contest
F12 Design Contest Notice
F14 Notice for add. information, information on
incomplete procedure or corrigendum
7
EU Forms (2)

• F7 Qualification System Utilities
• F8 Notice on a buyer profile
• F9 Simplified contract notice on a dynamic
  purchasing system
• F10 Public works concession
• F11 Contract notice - concession

Further forms
F15 European Economic Interest Grouping F16
European Society F17 Annual Contractors List
8
UN/CEFACT e-Tendering (I)
Standard for messages

• created during the tendering processes
  Registration, Information, Tender, Publication
  of Awardidentified in e-Tendering
• exchanged between Procuring Entity (Contracting
  Authority) and Tenderers (Economic Operators) or
  between agents of the Procuring Entity

9
UN/CEFACT e-Tendering (II)

• Focus Exchange of documents between Procuring
  Entity and Tenderers.
• Publication modelled as
• collaboration between units of the Procuring
  Entity
• collaboration between Procuring Entity and
  Tenderers.
• Publication process and collaboration between
  Procuring Entity and Publishing Body not
  considered
• Covered business documents (notices) do not take
  into account specific requirements of EU notices
  
• Prior Information Notice
• Invitation to Tender
• Contract Award

10
e-Notification Example
Example for different notification and
publication steps
EuropeanCommission
City of Berne
SIMAP.CH
SOGC (SHAB)
OJ/S EU
ContractingEntity
PublicProcurementPlatform
NationalOfficialGazette
SupranationalOfficialGazette
SupervisingAuthority
LocalOfficialGazette
OtherServiceProviders
Publication
Publication
Publication
Publication
InterestedParties
11
Business Process Actors (1)
Contracting Entity
12
Business Process Actors (2)
Publishing Body
13
Business Process Actors (3)
e-Notice Submitter
?
14
e-Notification (I)
Standard for messages

• resulting of the e-Tendering processes
• exchanged between Contracting Entity and a
  Publishing Body
• created during the general Notification process
• exchanged between an e-notice submitter and a
  publishing body

15
Business Process Actors (4)
Tendering processes
Notification process

• e-Notice Submitter
• Publishing Body

• Contracting Entity
• Publishing Body

16
e-Notification (II)

• Focus collaboration between Contracting Entity
  and Publishing Body and between publishing
  bodies.
• No direct information exchange between
  Contracting Entity and Economic Operators or
  other interested parties
• Introduces new actors and a different perspective
• Refers to an own business process Notification
• Input to this process are business documents of
  the Tender process area
• Includes EU-specific notification requirements

17
Clarification of Terms
IDABC eProcurement
UN/CEFACT e-Tendering

• eProcurement Phases
• e-Notification
• e-Tendering
• e-Awarding

• e-Tendering Processes
• Public Invitation
• Tender/Opening of Tenders
• Publication of Award

The e-Tendering and e-Notification standards do
not correspond to IDABC eProcurement phases
18
Business Requirements Specification
Description of Business Requirements

• Business process elaboration
• Information flow definition
• Information model definition

within the defined scope of the Business Domain
19
UN/CEFACT Modeling Methodology
UMM is a UML modeling approach based on three
views

• Business Domain View
• Business Requirements View
• Business Transaction View

20
BDV Business Operation Model
Business Process Pre-Information
Business Process Invitation
Business Process Notification

• Business Domain
• Business Areas
• Process Areas
• Business Processes are linked to process areas

Business Process Tender
Business Process Award Notification
e-Notification standard
21
BDV Business Areas

• Business AreaProcurement Sector
• Public Sector
• Utilities Sector

• Business Area Procurement by Tender
• Procurement of Works
• Procurement of Goods ("Supplies")
• Procurement of Service ("Services")
• Contract
• Design Contest

22
BDV Process Area

• Out of Scope Process Areas
• Contract
• Fulfilment
• Ordering
• Invoicing

Process Area Tender

• Open Tender
• Restricted Tender
• Restricted
• Accelerated Restricted Tender
• Framework Agreement

• Competitive Dialogue Tender
• Negotiated Tender
• Public Invitation
• Negotiated
• Accelerated Negotiated
• No Public Invitation

23
BDV Business Processes
Tender processes

• Pre-Information
• Invitation
• Tender
• Award Notification

Supporting process

• Notification

e-Notification standard
e-Tendering standard
Business Process Pre-Information
Business Process Registration
Business Process Invitation
Business Process Public Invitation
Business Process Tender/Opening of Tenders
Business Process Tender
Business Process Award Notification
Business Process Publication of Award
Business Process Notification
24
UMM Business Requirements View

• Identifying collaborative business processes
  between different business partner types
• Documenting of requirements realised by
• Business Collaboration use cases
• Business Transaction use cases

25
Business Collaboration Use Case
26
Business Transaction View

• Transformation of business process requirements
  into a choreography of information exchanges
• Choreography of business collaborations (activity
  diagrams)
• Choreography of business transactions (activity
  diagrams)
• Exchanged business information (class diagrams)
• A business transaction defines a simple
  choreography of exchanging business information
  between two authorized roles and an optional
  response.

27
Business Transaction Activity
28
Requirements Levels and Views

• Business Requirements View and Business
  Transaction View are both used in the BRS for
• Business Process Elaboration
• Information Flow Definition
• Optional use in Business Requirements View
• Business Process View
• Business Entity View
• The BRS Information Model Definition is related
  to the Business Information View, which is part
  of the Business Transaction View

29
Business Requirements Specification
Main aspects

• Business process elaboration (5.1)
• Elaboration in which context documents are used
• Information flow definition (5.2)
• Identification of documents used to ensure
  information flow in the context of 5.1
• Information model definition (5.3)
• Description of the business documents

30
Business Requirements (I)
Notification process (generic)

• Identify collaboration related to notice
  publication (5.1)
• Identify related transactions (5.1)
• Identify generic business documents related to
  the notification process (5.2)
• Identify specific business documents and
  information entities exchanged during the
  publication process transactions (5.2)
• Describe business documents (5.3)

31
Business Requirements (II)
Tender processes

• Identify each procurement context leading to a
  notice publication or submission, i.e. each
  business collaboration invoking the notification
  process (5.1)
• Identify related business transactions (5.1)
• Identify business documents and information
  entities submitted to the publication process
  (5.2)
• Describe business documents (5.3)
• Considered processes
• Pre-Information
• Invitation
• Tender
• Award Notification

32
Business Process Elaboration
Approach

• Identify notification needs in Public Procurement
  processes
• Assumption 1 EU forms cover all official
  publication needs
• Assumption 2 EU Public Procurement directives
  2004/18/EC and 2004/17/EC define all required
  official publication cases

33
Business Process Elaboration
Analysis of Forms Examples (1)

• F2 - Contract Notice
• Identification of a case, where F2 is not an
  invitation to tender

Notice is no invitation
34
Business Process Elaboration
Analysis of Forms Examples (3)

• F3/F6 - Contract Award Notice
• Identification of a cases, where information is
  not published

No publication of notice
No publication of notice items
35
Business Process Elaboration
Analysis of Directives Examples (4)

• F4 Periodic Indicative Notice
• Expression of interest

• F7 Qualification System - Utilities
• Re-publication of a qualification system

36
Information Flow Definition
Approach

• Only currently used XML business documents are
  considered
• Only associated activities are considered
• Notification process Messages sent by the
  Publishing Body, i.e., acknowledgements of
  receipt, of publication or of non-publication,
  refusals of publication and requests for
  additional information are not covered.

37
How to read the BRS How to identify the
business document to use

• Determine whether the current situation refers to
  an ongoing notification process or to a
  notification need within a tendering process

38
How to read the BRS How to identify the
business document to use Tender processes

• Identify the business context in the Business
  Operation Map

39
How to read the BRS How to identify the
business document to use Tender processes

• Identify the tender process and phase

5.1.4

• Identify the collaboration use case

5.1.7.1.5
5.1.7.1.2
5.1.7.2

• Identify the business transaction

• Identify the business document to use

5.2.2.10
40
Notification process (1)
Business Documents

• Input document Public Procurement notice
• Process internal business documents for modifying
  and cancelling a published notice

41
Notification process (2)
Business Collaborations

• Publication of a Notice
• Publication of the notice
• Edition of the notice (F14)
• Publication of a modifying notice (F14)
• Publication of a cancelling notice (F14)
• Notification without Publication
• Service Categories 17 to 27
• Contract Award Notice - Utilities

42
Notification process (3)
Example
43
Tender processes
Business Collaborations (Examples)

• Pre-Information
• Publication of a Qualification System without
  Call for Competition
• Invitation
• Publication of a Qualification System with Call
  for Competition
• Publication of a call for expression of interest
  (Utilities)
• Tender
• Publication of a notice on an on-going
  procurement procedure (negotiated procedure
  after selection of candidates)
• Award Notification
• Publication of Non-Award

44
Notification process (3)
Example
45
BRS Current Status

• Draft available for
• Business Process Elaboration
• Information Flow Definition
• Information Model Definition
• Identified Business Collaborations
• Notification Process 5
• Tendering Processes 28
• Identified Business Transactions
• Notification Process 6
• Tendering Processes 17

46
Business Document Notification
47
Business Document Award Notification
48
Information Model Definition
Approach

• Modelisation of current business documents
• Description of OJ/S document rules
• Work on RSM will modify models and element names

49
Discussion and Comments

• Business Operation Model
• Business Process Elaboration
• Information Flow Definition
• Information Model Definition
• National needs, e.g.
• Particular fields
• Publication below thresholds
• Minimum message for publication
• Invoice or other codes to consider