Server Deployment Overview

The servers that are used in the GxP reference architecture, follow a Master-Core and Local-Core architecture. This allows a centralized configuration and data storage concept, but also gives capabilities for autonomous operation.

Server Architecture

Central Core System

The Master-Core Server and associated servers are located in a central data center (on-premise, or cloud based).

The following Servers are part of the Central Core System in the GxP reference architecture

  • GXPC-Core

  • GXPC-RepA

  • GXPC-RepB

  • GXPC-RepC

  • GXPC-Interface

  • GXPC-Node

  • GXPC-VKPI

Site Core System

The Local-Core Server and associated servers are located at a site. The diagram shows a single site, but n-sites can be connected.

The following Servers are part of the Site Core System in the GxP reference architecture

  • SITE-Core

  • SITE-RepA

  • SITE-RepB

  • SITE-RepC

  • SITE-Relay

  • SITE-Interface

  • SITE-Node

Master-Core Server

The Master-Core Server exists only in the Central Core System. Its intended functionality is:

  • Central Configuration Repository

  • Global Use Cases

  • Central System Monitoring

  • Local Configuration Restoration

  • KPI and Performance Monitoring

The following services are installed: - AspenTech Inmation Core Service (Master-Core role) - AspenTech Inmation Web API Service - MongoDB (Standalone, for system log)

The following prerequisites are installed

  • Node.JS

  • inmation-compose-cli

Local-Core Server

The Local-Core Server exists once in each Site Core System. Its intended functionality is:

  • Autonomous Site Operation

  • Logic Execution

  • Contextualization

  • Local Storage and Buffering (Store-And-Forward)

The following services are installed:

  • AspenTech Inmation Core Service (Local-Core role)

  • AspenTech Inmation Web API Service

  • MongoDB (Standalone, for system log)

MongoDB (PSS)

A MongoDB replicaset is deployedk to ensure a high-availability database that can serve GxP and Non-GxP data. The Central Core System and all Site Core Systems have at least one replicaset. More replicasets can be deployed to increase storage capacity (vertical scaling).

The following services are installed:

  • MongoDB (rs0)

  • AspenTech Inmation Connector Service (active)

Interface Server

The Interface Server can be deployed on central or site level. The Central Core System has a mandatory Interface Server. For the Site Core System the Interface is optional (depends on usecase). Its intended functionality is:

  • Provide realtime data from AspenTech Inmation to 3rd party applications

  • Provide historical data from AspenTech Inmation to 3rd party applications

The following services are installed:

  • AspenTech Inmation Server Service

  • AspenTech Inmation Web API Service

Node Server

The Node Server can be deployed on central or site level, and be located in different network layers. This depends on the usecase that is realized with the node server. Its intended functionality is:

  • Connecting to datasources on supported interfaces

  • Collecting realtime and historian data

  • Buffering collected data (Store-And-Forward)

  • Executing logic

The following services are installed:

  • AspenTech Inmation Connector Service (active)

The Node Server requires only the installation of a Connector Service, so an existing server with 3rd party software can be extended to form a Node Server. The is specifically required for connecting to datasources that utilize non-Firewall-Friendly communication standards (for example OPC Classic).

Relay Server

The Relay Server is deployed in the DMZ network between Local-Core and Central-Core. It is deployed together with the Local-Core systems. Its intended functionality is:

  • Intelligent TCP-Forwarding

  • Real-time/Historical SPROX

The following services are installed:

  • AspenTech Inmation Relay Service

  • AspenTech Inmation Connector Service (active)