Architecture

The following image shows the architecture of AVEVA Work Tasks Connector for System Platform:

Principles of Integration with System Platform

• ArchestrA is used as IDE for contextual development of Workflows and Composite applications

• Work with Object-oriented concepts of System Platform

• Allows scalable deployments

• Allows redundancy for reliable operations

• Provides automated deployment across platforms

• ArchestrA graphics symbol for bringing process-specific UI inside HMI

• Get Events from any object

• Provides a scalable, easy to use and configurable, and inheritable model

• Enables existing users of IDE/HMI to work with workflows

High Level View of AVEVA Work Tasks Connector for System Platform Architecture

AVEVA Work Tasks and System Platform Integration

A WCF (Windows Communication Foundation) layer integrates the System Platform with AVEVA Work Tasks. An AppObject named WorkflowGateway, placed in the ArchestrA environment, manages the Outbound and Inbound communication between these layers.

• Outbound connection contains information related to the WCF service hosted inside the workflow engine (windows service). Outbound connection is used to trigger workflow during events in ArchestrA. The same connection is also used to get information from AVEVA Work Tasks layer.

• Inbound connection contains information related to the WCF service hosted inside the Runtime node as a windows service. Inbound connection is used to perform read/write attribute operation and also to synchronize user information from ArchestrA layer to AVEVA Work Tasks layer.

InTouch and System Platform IDE renders the Enterprise Console functionality.