Standards Development

Scope

This document describes the transaction information requirements of the transactions used in the basic collaborations described in EN 17017-1:20xx Electronic Public Procurement – Fulfillment - Choreographies. For each transaction there is an overview, the transaction business requirements and the transaction information requirements model containing definitions of terms, usage descriptions and cardinality of the information elements.

The document describes the following transactions:

1) Despatch Advice;

2) Receipt Advice

The identifier of this transactions document is EN 17017-2:20xx.

Purpose

Purpose:

This document provides specifications on business processes for exchanging electronic despatch advices and receipt advices as part of the fulfilment business processes in the post-award area.

Justification:

The supply-chain business processes and activities of the post-award processes of public and private e-procurement are widely supported by computer systems, typically in the form of an enterprise source planning (ERP) system. While these systems are aimed at supporting the activities internal to a given organization, the business processes they serve frequently involve sharing and exchanging information with other parties such as:

• Automate verification of delivery so payment of invoices can happen more smoothly

• Providing information for the logistics processes to avoid retyping

• Provide transparency between the purchased item and the physical goods delivered, such as serial number and stages in a framework agreement.

• Prepare the delivery party for delivery of goods or services also to enable just in time delivery and delivery in the right order of what has been purchased.

In the current market there is no standardized system covering these information exchange processes. As a result, public and private sector market actors instead must rely on a multitude of formats and specifications available. These are typically developed to support specific sectorial requirements, such as those of the electronics sectors, the retail industry, etc. Specifications are also provided by user communities such as OpenPEPPOL, reusing CEN/WS BII specifications based on the UBL 2.1 standard, as well as sector specific specifications provided by other standard developing organizations such as those developed by UN/CEFACT.

Without standardized processes, businesses and other organizations face a disparate environment of solutions, both in relation to B2G and B2B post - award procurement processes. These challenges increase when engaging in cross - sector and cross - border e - procurement, where in addition to the different national rules and the language barriers, there is no guarantee of semantic and technical interoperability.

With respect to fulfilment, this standard will address these issues by allowing for:

• Efficient and effective implementation of electronic sharing and exchange

• Interoperability between independent implementations of systems

Reliable and resilient supply chains by ensuring a continuous flow of item/product information on quality and value (stock information and related forecasts, item substitutes, alternative ordering arrangements, etc.) across sectors, e.g. in crisis situations or when supply chains are under stress