Global Data Synchronisation Search v. 2.0.2

XML Standards	>	Search Request	Search Result

Message Description

GLOBAL DATA SYNCHRONISATION SEARCH v. 2.0.2

Problem Statement

The GS1 Data Synchronization GSMP project team identified a need to have a Global Search mechanism to support the Global Data Synchronization Network (GDSN) processes. A Change Request (CR) was submitted to create a separate project team to address this task.
Prior to synchronising Item or Party data, participants in the Global Data Synchronisation Network (GDSN) need to be able to discover Items or Parties that may be of interest. It is envisioned that this discovery process will be realized via a standardized Global Data Synchronisation process and related messages. This Global Search is a foundation to ensure that data (Item and Party) is discoverable within the Global Data Synchronization Network and conforms to a common structure, complying with global standards.
There is a precondition for those participating in the Global Data Synchronisation Network (GDSN) that implementation of some aspects of the network become mandatory, eg., assigning each Trade Item a Global Product Classification. Only those companies and service providers that have implemented the requirements of the GS1 standards fully and accurately, have made their data available with a Source Data Pool, and have successfully completed the Registration process will be able to anticipate that their data will feature correctly in the results of a search. See diagram in Section 2 “Business Process View” of the Global Data Synchronization Network and it’s functionality.

Objective

The initial objective is to define process and data standards for the Global Registry to enable discovery within the Global Data Synchronisation Network. Subsequent projects will expand the search capability throughout the Global Data Synchronisation Network.

The process and messages specified in this document are mandatory for parties that make up the Global Data Synchronisation Network (GDSN); namely, the Global Registry, Source Data Pools and Recipient Data Pools. Processes and messages outlined in this document are made available to Data Sources and Data Recipients as a “minimal set” that must be supported by certified Data Pools. Data Pools may offer additional processes and messages to their customers as “value added services” to this minimal set.

Audience

The audience of this standard is any participant in the global supply chain. This includes retailers, manufacturers, distributors, wholesalers, exchanges, service providers and other third parties. Entities wishing to become a certified Source and Recipient Data Pool within the Global Data Synchronization Network will be the adopters of this Global Search standard.

Business Context

Industry: All
Geopolitical: All
Product: All
Process: Align_GDSN
System Capabilities: EAN.UCC
Official Constraints: None

Business Transaction View

Use Case Overview

Use Case Description

Process
Use Case Name

Global Search

Use Case Identifier (Traceability)

UC-1

Use Case Description

This Use Case describes how a Data Recipient requests a search of the Global Registry and how the Global Registry returns a result to the Data Recipient.

Actors (Goal)

Global Registry, Source Data Pool, Recipient Data Pool, Data Source and Data Recipient

Performance Goals

N/A

Preconditions

All searchable Item and Party Information must be registered in the Global Registry

Postconditions

A Search Request is created and search results are returned to the searching party

Scenario

Begins when... The Data Recipient creates a Search Request.

Continues with...

Step #	Actor	Activity Step
1	Data Recipient	Sends the Search Request to its Recipient Data Pool.
2	Recipient Data Pool	Sends the Search Request to the Global Registry.
3	Global Registry	Matches the Search Criteria with registered Items and Parties.
4	Global Registry	Sends the Search Result to the Recipient Data Pool.
5	Recipient Data Pool	Sends the Search Result to the Data Recipient.

Ends when... The Data Recipient receives the search result and sends an acknowledgement to the Recipient Data Pool.

Alternative Scenario

AS 3 - The Global Registry does not find a match for the search criteria

Step #	Actor	Activity Step
1	Global Registry	Sends a Search Result to the Recipient Data Pool indicating that a match was not found.
2	Recipient Data Pool	Sends the Search Result to the Data Recipient.
3	Data Recipient	The Data Recipient receives the search result and sends an acknowledgement to the Recipient Data Pool.

Related Requirements

N/A

Related Rules

N/A

Business Transaction Sequence Diagram

TOP

Code Lists

Date of Publication: March 2007