Transcription of DeltaV™ Mobile Network Architecture Considerations
1 White PaperDecember Mobile Network Architecture ConsiderationsThis document provides an initial overview of Network Architecture Considerations for your deltav Mobile PaperDecember 2017 deltav Mobile Network Architecture of ContentsIntroduction ..3 Network Topology ..3 Information Sources ..5 Mobile Device Connections ..6On-premise ..6 Off-premise ..7 Notification Options ..8 Native Mobile push notifications ..8 Email notifications ..9 SMS text notifications ..93 White PaperDecember 2017 deltav Mobile Network Architecture Mobile provides operations personnel and managers with access to process and production data from Mobile devices.
2 deltav Mobile users can monitor real-time process and diagnostic values, along with their historical data in touch-friendly trends. Additionally, users can view personalized lists of alarms and even receive notifications for deltav alarms. The Mobile application is primarily focused on two views:1. Watch List: a persistent collection of tags that the user wants to Alarm List: a collection of alarms based on filter criteria such as process hierarchy, functional classification, priority, and alarm Mobile builds on and extends the deltav Executive Portal platform.
3 In addition to supporting web-based displays on Windows PC or tablets, the overall platform now supports viewing data and alarms on Mobile devices. deltav Mobile supports iPhone (5s and above) and Android (KitKat OS and above) Mobile devices. For viewing web-based displays Internet Explorer is Systems act as data sources for deltav Mobile . To enable these data sources, you must install a software component ( deltav Communicator) on a deltav Application Station (with the deltav Continuous Historian) to enable the communication of process data and alarms.
4 The deltav Mobile installation package contains the following: deltav Mobile installation media deltav Communicator installation media deltav Display Export tool (part of the original deltav Excutive Portal release) Software license bundle The deltav Mobile application is downloaded from the Apple App Store or Google Play Store This document provides a description of the Architecture and deployment options for deltav Mobile . It also details Mobile device access and notification TopologyDeltaV Mobile may be installed as either a 2-tier or a 3-tier topology.
5 The 3-tier topology is shown in Figure 1, and the 2-tier topology is shown in Figure 2. A multi-level topology provides flexibility which may be utilized, as required by site policies, to restrict Mobile device access. The deltav Portal is used to manage connections to one or more deltav Systems. It also manages users and deltav Mobile Server provides support for the actual Mobile device app ( iPhone or Android app). It also provides support for the deltav Mobile web-based configuration application, deltav Mobile Studio, which is used to configure deltav Mobile watch lists, alarm lists, and lowest layer of the topology is the deltav Communicator.
6 The deltav Communicator is installed on a deltav Application Station (with Continuous Historian) and provides access to deltav real-time process data, historical data, and PaperDecember 2017 deltav Mobile Network Architecture NetworkPlant NetworkDeltaV Area Control NetworkL4L3L2 Professional PlusFirewall AFirewall BFirewall CFirewall DOperator WorkstationEngineering StationWeb PortalDeltaVMobile ServerDeltaV CommunicatorApplication StationDeltaV Mobile AppDeltaV Mobile App deltav Mobile StudioFigure 1.
7 The 3-tier topology installs the deltav Mobile Server separately from the deltav the 2-tier topology, the deltav Mobile Server and the deltav Portal are both installed at the same level of the Network topology, presumably on the same server, although this is not NetworkPlant NetworkDeltaV Area Control NetworkL4L3L2 Professional PlusFirewall AFirewall BFirewall COperator WorkstationEngineering StationWeb Portal& Mobile ServerDeltaV CommunicatorApplication StationDeltaV Mobile AppDeltaV Mobile App deltav Mobile StudioFigure 2.
8 deltav Mobile 2-tier topology combines the deltav Mobile Server and deltav Portal on the same Network PaperDecember 2017 deltav Mobile Network Architecture a third option, deltav Portal can be co-deployed with the deltav Communicator on a deltav Application Station in deltav or newer, when the Operating System requirements are met ( Server 2016). This option is depicted is Figure NetworkPlant NetworkDeltaV Area Control NetworkL4L3L2 Professional PlusOperator WorkstationEngineering StationWeb ServerDeltaV Portal & CommunicatorApplication StationDeltaV Mobile AppDeltaV Mobile App deltav Mobile StudioFigure 3: A third deltav Mobile supported Architecture for deltav and SourcesDeltaV Portal supports multiple information sources, including deltav Systems and OPC Servers.
9 The deltav System information source delivers alarms, real-time process values, and historical process values to the deltav Mobile platform. Currently, the deltav Portal supports up to five deltav System information NetworkL3 Professional PortalDeltaV CommunicatorApplication StationDeltaV CommunicatorApplication StationL2 System 1 Professional PlusL2 System 2 Figure 4: Multiple deltav System information sources combine into one deltav PaperDecember 2017 deltav Mobile Network Architecture OPC information sources include real-time OPC DA and historical OPC HDA servers.
10 With these information sources, you can expand your deltav Mobile platform to consolidate relevant information across multiple vendor systems and sources of 3 deltav PortalOPC DAOPC HDAF igure 5: deltav Portal can accept OPC DA and OPC HDA information Device ConnectionsMobile devices must connect to the deltav Mobile Server to view alarms and process values. This connection uses HTTPS over a user-configurable port (default port 44155).On-premiseOn-premise, this is achieved using a local Wi-Fi Network . No direct internet (WWW) connection is Mobile ServerLevel 4 EnterpriseInternetDeltaV Mobile connets via local Wi-FiFirewallFirewall DDeltaV Mobile AppDeltaV Mobile AppFigure 6.