Systems availability
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

CBs sharing a GGN in Database and/or VS

Go back to:  |  |

The following chapter refers to cases in which products of a producer or a producer group are certified by different certification bodies (CB) in the Database (DB) and/or Validation Service (VS). 

The different possibilities on how to share a GGN are explained below. 

  1. Sharing a GGN in the Database 
    If you wish to share a GGN with another CB where both CBs are going to enter the certificate in the Database it is possible, as explained here: Manage Business Relations - GLOBALG.A.P. Wiki Site (ggwiki-globalgap.org)  
    The same FAP can be certified in parallel by two CBs. 
  1. Sharing a GGN in VS and Database 
    a. CB1 issues a certificate in VS while the other CB2 issues a certificate in the Database: 
    Since it is only possible for the Trustee of a GGN to manage the GGN in VS we recommend to keep the respective CB that uses the VS for issuing the certificate as the Trustee. In case a trustee change is needed in such instance, please contact us.  
    For the CB2 using the database the procedure mentioned here, is needed. 
    The same FAP can be certified in parallel by two CBs. 

    b. Both CBs wish to issue a certificate in VS: 
    If you wish to share a GGN with another CB also using the VS it is possible with the assistance of the customer support team. In VS only the Trustee selected in the Database can manage the respective GGN in VS. Therefore, if CB2 wishes to enter the certificate in VS, please contact us to request the change of trustee for a few working days to allow CB2 to issue the certificate in VS. During that time CB1 has no access to that GGN in VS. Once done we would change the trustee back to CB1. With this CB2 has no access to the GGN in the VS anymore.  
    The same FAP cannot be certified in parallel by two CBs (see Example4). 

Example 1: 2 CBs issue certificates in DB 
(Starting scenario CB1 is the Trustee) 
- CB1: GGN1 with certified Option 2, V6 SMART Banana, in the Database. 
- CB2: wants to issue a certificate Option 2 V6 SMART Apples under GGN1, in the Database. 
Trustee Change is not needed to CB2. 

Example 2: 2 CBs issue certificates in DB and VS 
(Starting scenario CB1 is the Trustee) 
- CB1: GGN1 with certified Option 1, V6 SMART Banana, in the database. 
- CB2: wants to issue a certificate Option 1 V6 SMART Single Site Apples and PHA under GGN1, in VS. 
Trustee Change is needed to CB2. We recommend keeping the Trustee CB2 also after the certificate was entered, since CB1 can also manage the product in the Database without being the trustee. 

Example 3: 2 CBs can issue certificate in VS
(Starting scenario CB1 is the Trustee) 
- CB1: GGN1 with certified Option 1, V6 SMART Banana Single Site, in VS. 
- CB2: wants to issue a certificate Option 1 PHA under GGN1, in VS. 
Trustee Change is needed to CB2. 

Example 4: 2 CBs cannot issue certificates (for the same module) in VS 
(Starting scenario CB1 is the Trustee) 
- CB1: GGN1 with certified Option 1 V6 SMART Single Site Banana. 
- CB2: wants to issue a certificate Option 1 V6 SMART Single Site Apples under GGN1. 
In VS CB2 will not be able to issue this certificate even after a trustee transfer to CB2. Reason being that the VS system does not allow to certify the same module (e.g. Option 1 V6 SMART single site cert) in parallel! In such cases one of the CBs has to enter the certificate in the different system (database). 

Summary of two CBs sharing one GGN in VS:  
- Once a CB is not the trustee anymore there is no access and therefore no amendments can be done. Meaning the GGN cannot be managed by this CB in VS . 
- A producer group (PG) member can be linked to two different PGs even though being managed by to two different CBs, however the Trustee of course needs to be changed respectively. 
- A PG cannot be a member of another PG.  
- It is possible to issue in parallel any other FAP certificate except for the one that already exists.

Procedure: 

  1. CST receives an e-mail either 
    a. directly from the current Trustee CB1 to confirm to trustee change to CB2 in order to enable CB2 to issue the certificate in VS.
    Or 
    b. CST receives an e-mail from CB2 that contains the confirmation for trustee change from CB1.   
  2. CST changes the Trustee and informs CB2 accordingly with the request/advice to create/issue the certificate in the following few working days.   
  3. CB2 confirms to CST via e-mail that the certificate has been issued and then CST can change back the Trustee from CB2 to CB1.  

General: If CB2 needs to correct anything for GGN in VS and are not the trustee of the GGN, CST needs to be contacted.