PI System Architecture

 

 

PI System Architecture — Typical Site Implementation

Starts with a variety of data sources on a plant’s Manufacturing Control Network (MCN) including:

  • Individual pieces of equipment monitored by :
    • PLC/Instrument Systems
    • SCADA Systems
    • DCS Systems
     
  • 3rd-Party Data Historians
  • Manual Entry
  • LIMS systems
  • Others (Ongoing development and support of over 400 PI interfaces)

PI Interface nodes collect process data and forward it through a firewall to a PI server (or servers in a High Availability configuration) within a secure DMZ which may also contain client applications that access and take action on collected PI data.  This DMZ then communicates through an additional firewall with the Site’s corporate LAN and its world of users and client applications.

PI System Architecture — Typical Enterprise Implementation


Starts with a collection of individual site implementations

Individual sites communicate via firewalls with an Enterprise Datacenter (ECN) which typically includes:

  • PI WebParts and SharePoint 2010 implementations
  • An Enterprise PI Collective
  • Business Intelligence, Marketing, Forecasting, Applications and Users

The ECN in turn communicates via firewall with the Business Network for Applications, Functions, and Users including:

  • Business Systems Portal Servers
  • Application Servers
  • PI Collectives
  • Client Applications
  • Mobile Clients
  • Wireless