Notes on System Architecture Options

AVEVA's software components can be used to design industrial IT systems using several architectures, according to the exact requirements of a customer. The choice of architecture can impact the best practices used for designing an application to be validated.

The present guide will focus on the development options using AVEVA Batch Management in a AVEVA System Platform environment. It does not cover any specific Foxboro Evo, Core Control Services, or Foxboro DCS Software. Any custom code is out of scope of this document.

AVEVA Batch Management .NET controls and/or ActiveX can be inserted in ArchestrA graphics or InTouch views respectively to integrate the AVEVA Batch Management client components in an InTouch container. Alternatively, the AVEVA Batch Management standalone clients (Batch Display, Batch Scheduler) can be used as the human machine interface to operate or schedule batches.

AVEVA Batch Management provides the ability to connect to the control system in two different ways:

• Using IBSERV and AVEVA Batch Management’s tag linker to connect to a DA Server (only in Standalone mode).

• Using IBMX and ArchestrA objects which themselves are connected to DI Objects and DA Server.

As this document is using the combination of AVEVA Batch Management with AVEVA System Platform, the later approach used is represented in Figure 1.

Figure 1 - Architecture assumptions

Because the recommended architecture involves AVEVA System Platform, InTouch, and the AVEVA Alarm System, the reader should also refer to “AVEVA System Platform Deployment Guide” for completeness.