Table of contents

1. Interface environments
   • 1.1 Test environment
   • 1.2 Stage environment
   • 1.3PCS Production
2. Routing to/from the PCS site (applicable only for PCS Stage environment)
   • 2.1 Outbound communication (from PCS)
   • 2.2 Inbound communication (to PCS)
3. RNE Local Instances
   • 3.1 Test LI
   • 3.2 Stage LI
   • 3.3 Production LI
4. PCS TAF/TAP TSI interface general architecture

1. Interface environments

1.1 Test environment:

• PCS Test 4:
• Login credentials are available here and available to all 
• No production dossier information

1.2 Stage environment:

• PCS Test 2:
  • The same login credentials as for the production environment
  • The Access is restricted based on the agency type of the user in the production environment (for example: an IM cannot log in as an applicant)
  • Production dossier information
  • The trigger of outbound communication (message sent from PCS) is done by RNE based on the inputs provided by the applicant/IM (example: send x path requests where a specific location is included) 

• PCS Test 5:
  • Login credentials are available here and available to all 
  • No production dossier information

1.3 PCS Production

2. Routing to/from the PCS site (applicable only for PCS Stage environment)

The routing is done based on the value provided in the MessageRoutingID element.

2.1 Outbound communication (from PCS)

• PCS Test 5: the MessageRoutingID is included in the message and contains the value “5”.
• PCS Test 2: the MessageRoutingID is included in the message and contains the value “2”.

2.2 Inbound communication (to PCS)

• PCS Test 5: the MessageRoutingID must be included in the message and contain the value “5”.
• PCS Test 2: the message must be sent without the MessageRoutingID

3. RNE Local Instances (LI)

3.1 Test LI

3.2 Stage LI

3.3 Production LI

4. PCS TAF/TAP TSI interface general architecture