Licensing Guide for the Wonderware System Platform …api/deki/files/298/Licensing... · The...
Transcript of Licensing Guide for the Wonderware System Platform …api/deki/files/298/Licensing... · The...
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 1 of 31
Please direct any feedback to [email protected]
The unofficial official licensing guide from InSource.
Wonderware has ceased to update this guide but InSource is continuing to update it to the
best of our ability.
Use this as a guide and best practice and when the time comes to work out specific
commercial issues, InSource will be there to help make sure your licensing is correct and
you are legal in the eyes of Wonderware.
See more in the version history HERE.
Licensing Guide for the Wonderware
System Platform and Clients
Copyright 2005 Wonderware Corporation
26561 Rancho Parkway South
Lake Forest, Ca 92630
All Rights Reserved
This document contains information of a proprietary nature.
ALL INFORMATION CONTAINED HEREIN SHALL BE KEPT IN CONFIDENCE
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 2 of 31
Please direct any feedback to [email protected]
Version History
Version 2012R2 (3.6) November, 2012 Version 3.0A- Released September 5th, 2007 Application Server is now Wonderware Application Server or Application Server for short. There are new part numbers for System Platform. Supervisory Client is now InTouch for System Platform which includes InTouchView with a Platform or Session. Wonderware FactorySuite A2 Development is now Wonderware Development Studio. Version 2.1B- Released February 16, 2007 SuiteVoyager is now Wonderware Information Server 3.0. This will result in a license change and part number revision change from 2.1B to 2.1B for the System Platform Parts and Options. InSQL is now Wonderware Historian and will be referred to as such. This will be reflected in the System Platform and Options Part Numbers. Also Information Server CAL – Standard is being added. This will result in two types of Information Server CALs, Standard and Advanced. Changed computer architecture drawings to show a router in between networks rather than host computers with dual NIC’s that are connected to both networks at the same time. Dual NIC configurations are considered a poor security practice for industrial applications and networks. Version A2- Released December 14th, 2006 On November 6th, 2006 Wonderware Introduced the Wonderware System Platform with new sales collateral and new part numbers on a separate tab in the Global Price Sheet. This is the new preferred way to present, communicate and sell the combined Wonderware product offering for Supervisory, SCADA and P&PM. The System Platform License is comprised of Application Server IO, Historian Tags, Information Server Content Server, Device Integration Server and a Number of Application Server Platforms. This License runs on multiple computers and is delivered as 4 license mini-disks or 4 license mini-disks and 4 USB Keys. All existing products are available a-la-carte, but the intent is that the Application Server and Information Server Content Server will be removed from the Wonderware Global Price Sheet in the future. The Wonderware System Platform is a Strategic Industrial Application Services Platform, built on Archestra Technology for Supervisory HMI, SCADA and Production and Performance Management. It contains an integral core set of capabilities and services to support sustainable production and operations performance improvement and enables consistent and reliable operations across manufacturing facilities and industrial sites. What Products make up the System Platform License?
� Wonderware Application Server (Application Server) � Wonderware Historian Server � Wonderware Information Server Content Server � Wonderware Device Integration Servers
What options are available for the System Platform?
� Additional Device Integration Servers � Additional Wonderware Historian Servers w/Application Server Platform
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 3 of 31
Please direct any feedback to [email protected]
� Additional Wonderware Information Server Content Servers w/Application Server Platform � Additional Application Server (Application Server) Platforms for Existing InTouch or Stand-alone
Application Server or TSE Console for TSE Clients What are the Wonderware Client Parts?
� Supervisory Client- for Operator Clients with Trending � InTouchView w/Application Server Platform Client- for Operator Clients without Trending � Information Server Client- for Web Report and Analysis � Active Factory with WW Basic CAL- for Stand-alone AF Clients
Changes to past versions of the Application Server License Guide Version N – Updated July 4, 2013 This licensing guide has ceased to be updated by Wonderware, unfortunately. This is an update to it by InSource Solutions. Most licensing concepts still apply. Licensing in the past few versions of System Platform has largely remained unchanged. Exceptions are regarding low node count Galaxies. Low node count Galaxies can be more competitively priced using the newer Starter Bundle licensing method. In System Platform version 2012, Wonderware replaced the single and dual node System Platform licensing with a one and two client Starter Bundle concept. Most importantly, the number of clients that can be added to this bundle was extended to five (5). One can add normal InTouch for System Platform clients to the 2-client starter bundle, up to 5 clients. This effectively closed a price gap that existed in 3-5 client projects. The starter bundle is delivered with individual component license files, unlike its predecessor (single and dual node SP) which had all functionality rolled into one license file, limiting network architectures. The newer Starter Bundles have no such license file and architecture limitations, making for easy architecture transitions from 5 client starter to 6 client ‘full’ System Platform. In this unofficial revision of the licensing guide, an attempt is being made to eliminate Part Numbers from the guide, as they change with every software revision. One should refer to the license description to apply these licensing concepts to current and future software revisions. Other changes:
• All Historians bundled with System Platform are of the Enterprise version, in order to support the newer Tiered Historian features of Historian 2012 (v10) and beyond.
• ActiveFactory has become Historian Client
• Additional platform(s) and device integration has been added to all System Platforms to allow for all best practice architectures. This required updates to the network architecture drawings indicating nodes and functionality included in the System Platform bundle.
Version M- Updated June 23rd, 2006 Minor Changes Version L- Updated Dec 1st, 2005
Licensing for Application Server 2.1 is basically unchanged, with the exception of a new feature line that is included in the Wonderware Development for TSE License to control the number of IDE Sessions. The FS A2 Dev is now also enforcing the size of Galaxy that a certain size FS Dev License can connect to in order to deploy, modify or maintain the system.
Details:
There are several changes to the structure of Application Server Part Numbers and Licenses with Release 2.1.
� New version part numbers for Application Server 2.1 Galaxy IO, Platforms and Sessions
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 4 of 31
Please direct any feedback to [email protected]
� Wonderware Development sizes small, medium, large and unlimited now contain feature lines for Application Server 2.1
� License Protection of the ArchestrA IDE in Wonderware Dev for TSE. The FS A2 Dev for TSE is now protected using a combination of soft license and paper license. The new FS Dev for TSE License will contain all the feature lines of the standard (thick client) version of FS Dev, with a new feature line that will enforce the session count when the IDE is used in a Terminal Services Environment. This new feature line is called Dev_Session_Count and controls TS connections for IDE, GR Access, WindowMaker and WindowViewer browser sessions. The InTouch components will be paper licensed.
� A FSA2 Dev license is required in the node where IDE is installed. To successfully launch the IDE Connection Dialog box the system first verifies that a valid FSA2 Dev license is installed in the node.
� When using the Galaxy Browser from InTouch WindowMaker the system will verify that a valid FS A2 Dev license exist on the node where WindowMaker is installed
� To connect to a Galaxy from the IDE the system will verify that the Dev_IO_count in the FS A2 Dev license is greater than or equal to the Galaxy IO count in the AppServer license in the GR node.
Version K- Updated December 13, 2004
Changes for this release: There are several changes to the structure of Application Server Part Numbers with Release 2.0. They include the following:
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 5 of 31
Please direct any feedback to [email protected]
New part numbers for Application Server 2.0
• Additional Run-time IO sizes. On the low end, additional sizes are 250, 2,500 and 5,000. On the high end, the new feature lines are 200K, 500K and 1 Million IO. A Tech Worksheet is required to quote Galaxy sizes of 25K IO or more.
• Wonderware Development is tied to the run-time Galaxy IO Count to allow for a more scaleable development license. There are 4 sizes of FS A2 Dev for small, medium, large and unlimited. Wonderware Development Studio is used for developing all of Wonderware’s FactorySuite products, including standalone InTouch. As a result, the following limitations will be stated in the associated License Certificate:
FS Dev Size Application Server Galaxy IO
InTouch Tags (InTouchView has Unlimited Remote References)
InSQL Tags
Small 250 64 100
Medium 2,500 500 100
Large 5,000 1,000 500
Unlimited Unlimited Up to 60K 500
• Licensing a Galaxy by a) number of IO, b) by number of platforms and c) by number of TSE Sessions. This is being done to alleviate any issues with “High Redundancy Costs” for Terminal Services sold with Application Server. This means that TSE Platforms and Sessions Part Numbers have been removed and there is only one type of Platform. A TSE Session will continue to be Seat-Based on the client side, but can be used with any Platform (TSE Server) on the server side. This means that a Galaxy License will be issued with limits of number of IO, number of Platforms and number of Sessions, period. With the current Globetrotter Licensing System, the number of Sessions will be a paper license.
• Over a low-bandwidth network, Terminal Services or Remote Desktop has been found to be a more optimal means for making a change to a running Galaxy Repository as opposed to having the IDE located at a remote site. To make sure the customer is within license, there is a new paper-based license available for all 4 sizes of the Wonderware Development for use inside of a Terminal Services environment. This paper license is required for any computer that will access an existing Wonderware Development over the network through a Terminal Services session. It is a seat-based license and not concurrent. A regular FS Dev License and License file is a pre-requisite for purchasing this TSE License.
• Please note that Microsoft bundles the Remote Desktop Client (RDC) with Windows XP and Windows 2003. This allows a user to establish a single remote desktop connection to any computer running these operating systems, providing that they have a user account on the computer. The purpose of RDC is to allow the normal user of the computer to access and use their applications remotely if needed. Therefore, a Wonderware Development for TSE License is not needed if the customer wants a single remote connection to an existing Wonderware Development Seat using RDC. It is only required if multiple on-line sessions are being severed using Microsoft Terminal Server.
• The allowed number of Platforms per Galaxy License increased from 40 to 100 with Release 2.0.
• Wonderware Development does not require a run-time Platform License to develop, test locally and deploy changes to a production system. If the customer wants to also use the Wonderware Development as a Visualization Node in a production environment, they must purchase a Platform License.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 6 of 31
Please direct any feedback to [email protected]
Table of Contents
LICENSING GUIDE FOR THE WONDERWARE SYSTEM PLATFORM AND CLIENTS .......................... 1
VERSION HISTORY ................................................................................................................................................................ 2
1. INTRODUCTION .............................................................................................................................................................. 7
2. GENERAL GUIDELINES FOR LICENSING THE WONDERWARE SYSTEM PLATFORM ............................... 7
3. SYSTEM PLATFORM PART NUMBER KEY ............................................................................................................... 9
4. STEPS IN THE ESTIMATION OF A SYSTEM PLATFORM LICENSE .................................................................. 10
5. SIMPLE FLOW DIAGRAM FOR ORDER PROCESS ............................................................................................... 11
6. DEFINITION OF NODE TYPES DESCRIBED IN THIS DOCUMENT ................................................................... 12
7. CONFIGURATION EXAMPLES .................................................................................................................................. 13
8. WONDERWARE SYSTEM PLATFORM AND P&PM PILOT BUNDLE ................................................................ 14
9. BASIC SYSTEM PLATFORM CONFIGURATION .................................................................................................... 15
10. SUPERVISORY CLIENT SERVER CONFIGURATION WITH DEDICATED IO SERVER NODE .................... 16
11. RUNNING IO SERVERS ON AOS NODES.................................................................................................................. 17
12. COMBINING VISUALIZATION, AOS AND IO SERVERS (FULL PEER-TO-PEER) .......................................... 18
13. COMBINING VISUALIZATION AND AOS ON THE SAME NODE (IO SERVERS IN A SEPARATE NODE) . 19
14. IO SERVER REDUNDANCY ......................................................................................................................................... 20
15. USING A DEDICATED TERMINAL SERVER NODE ............................................................................................... 21
16. REDUNDANT TERMINAL SERVER NODE ............................................................................................................... 22
17. TERMINAL SERVER LOAD BALANCING LICENSING WITH THE SYSTEM PLATFORM .......................... 23
18. DETAIL ON DEVICE INTEGRATION LICENSING ................................................................................................. 24
19. DETAIL ON ADDING THE SYSTEM PLATFORM TO AN EXISTING INTOUCH APPLICATION (UPGRADE
EXISTING INTOUCH NODES AND ADDING PLATFORMS) ................................................................................. 25
20. DETAIL ON ADDING THE SYSTEM PLATFORM TO AN EXISTING INTOUCH APPLICATION (NO
CHANGE TO EXISTING INTOUCH) .......................................................................................................................... 26
21. CONFIGURATION DATABASE (GR NODE) ON A DEDICATED COMPUTER .................................................. 27
22. STANDALONE DEVELOPMENT OR NON-PRODUCTION SYSTEM .................................................................. 28
23. OFF-LINE MULTI-DEVELOPER ENVIRONMENT ................................................................................................. 29
24. USING IDE OVER TERMINAL SERVICES- LOW BANDWIDTH ENVIRONMENT .......................................... 30
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 7 of 31
Please direct any feedback to [email protected]
1. Introduction
Purpose of this Document
This document is used as a guide in determining the license requirements for an ArchestrA technology based system, which utilizes the Wonderware System Platform. It is a companion to the Wonderware Deployment Guide and the Wonderware Global Price List. All three documents should be used when estimating the total licensed price for a Wonderware System. Users of this document will include Sales Personnel and Estimators. Please note that the use of the term “License” in this document refers to the legal rights a customer has to use Wonderware Software. There is also a local License Manager and associated .LIC file which is loaded with specific Wonderware Software packages and monitors the use of that specific package. Please refer to the appropriate product documentation to learn more about the Wonderware License Management System.
2. General Guidelines for Licensing the Wonderware System Platform
• The Wonderware System Platform license contains a single license for the Application Server IO and 3, 4, 6, 10, 18, 20, 22, or 42 Application Server Platforms, Wonderware Historian Tags, Information Server Content Server and a number of Device Integration Servers. This is the starting point for any configuration. To this license are added options to expand the configuration, such as additional Historian Servers, Information Server Content Servers, Device integration Servers or Application Server Platforms. On top of this, Wonderware Clients are ordered for Visualization, Reporting and/or Analysis.
• The Development Tool for the Wonderware System Platform is the ArchestrA Integrated Development Environment (IDE), which is included in the Wonderware Development Studio License. The Wonderware Development Studio License also includes a single Per Device MS SQL Server CAL. This allows the Galaxy Repository (GR) to be stored on this node. Users can also build and deploy a Galaxy and automation objects on the local node for test purposes, but the ability to locally execute automation objects in production is not authorized. Deployment of objects to other systems is allowed. The Wonderware Development Studio license comes in five sizes of Limited, Small, Medium, Large and Unlimited.
• The Wonderware Dev Studio License includes the ability to test and deploy automation objects. The first Platform that must be deployed in a Galaxy is for the GR. The Wonderware Dev comes with a Dev_Platform as part of the license. In order to test or start a GR on the Wonderware Dev Node, a Platform from the active Galaxy will need to be allocated. With a future release of Application Server, the Wonderware Dev Studio Node can use a limited Dev_Platform License or a full Run-time Platform License. Until then, we ask that customers ignore any system warnings that arise from the need to allocate a Platform to the Wonderware Dev node for Testing and Deployment Purposes. Please note that a Run-time platform is required whenever the Wonderware Dev is also used as a Run-time Visualization Station.
• The Wonderware System Platform is not a bundle that can be separated as individual licenses for upgrade purposes. All the components are tied to a single Galaxy. The System Platform is a single software license that can run on multiple computers. Because the current Wonderware License Manager is node-based, this license is distributed on multiple license mini-disks. When the new network-based license management system is available, this will be a single license managed on a central License Server. The System Platform license runs on multiple computers and is delivered as 4 license mini-disks or 4 license mini-disks and 3 USB Keys. The 4 License Mini-Disks are for 1) Application Server IO and Platforms, 2) Historian Server Tag Count, 3) Information Server Content Server w/ 1 CAL, and 4) Wonderware Device Integration License. In keyed licenes, the Information Server Content Server is not keyed, hence only 3 hardware keys.
• Version upgrades for the System Platform are provided as part of a Wonderware Customer Support Contract or can be purchased via individual part numbers listed in the Global Price Sheet. When performing a version upgrade, the entire System Platform License must be upgraded. In order to minimize the effect of upgrade costs, a Customer Support Contract is highly recommended for all Wonderware Customers. This provides the greatest value and helps to spread support costs over the entire life-cycle of the system rather then incurring upgrade costs as a single lump sum.
• System Platform license has a Serial Number. Customer Support Program charges are calculated based on System Platform part price and not sub-products.
Upgrades
� Functional Upgrade Credits are available for all System Platform parts in the Functional Upgrade Credit Table on Team.Wonderware.
� Version upgrades are only allowed at the System Platform part level, not the individual product level.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 8 of 31
Please direct any feedback to [email protected]
� There are also credits available for going from Application Server or Historian to the System Platform license. A column has been added to the Functional Credit Table on Team.Wonderware with special amounts if upgrading to the System Platform for customers who already have the same release and capacity level of Historian or Application Server. If the customer has an existing Historian 9.0 of the same capacity or Application Server, then 100% purchase price credit is applied toward the purchase of the System Platform package. Customers must be at the same version to get a 100% credit. If not, the standard functional upgrade credit is applied. Functional trade-ins are only allowed for equal or less capacity. Customer can also choose to keep existing Historian for extra historical archive capacity with the System Platform.
� There are no Functional Upgrade Credits for SuiteVoyager toward the System Platform.
� For Application Server Platform Licenses, 100% credit will be given for up to the existing Platform Count, not to exceed the number
of platforms contained in a System Platform license. For example, if an existing user has a platform count of 10, and they buy a 5,000 IO System Platform License (which has 3 Platforms), they will get credit for the 3 Platforms and a new license for a total of 10 platforms is generated.
� There are no functional Upgrade Credits for existing Device Integration licenses. Use it with the new System Platform License.
� There are no functional Upgrade Credits for going from InTouchView, ActiveFactory or SV Clients to the Wonderware Client
Licenses. Use them with the new System Platform License. Here is a diagram that illustrates the Functional Upgrade process for System Platform:
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 9 of 31
Please direct any feedback to [email protected]
3. System Platform Part Number Key (This is dated material not being updated)
The Wonderware System Platform part numbers are smart parts. This means that they contain some logic and structure that allows the understanding of the content of the part. The following is the key.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 10 of 31
Please direct any feedback to [email protected]
4. Steps in the estimation of a System Platform license
Step 1: Select the appropriate System Platform size. IO count is based on the number of IO points that are configured in DI Objects. These are associated with OPC Servers, IO Servers, DA Servers or Proxy Objects, over the whole Galaxy Namespace, regardless of how many PCs are in the system. Historian history tag counts are equal to IO points unless otherwise indicated. Step 2: Select any options needed for the System Platform. A single Galaxy IO, Historian Server, Information Server Content Server with 1 CAL and 2, 4, 8, 16, 18, 20, or 40 Device Integration licenses, as well as 3, 4, 6, 10, 18, 20, 22, or 42 Application Server Platforms is included in the System Platform license. Platform licenses included in the System Platform are intended for use on servers, such as GR, AOS, Historian, Information Server nodes. They are not intended for use with visualization clients, as these are purchased separatly. If more are needed, you can specify:
� Additional Device Integration Servers � Additional Wonderware Historian Servers w/Application Server Platform � Additional Wonderware Information Server Content Servers w/ Application Server Platform � Additional Application Server (Application Server) Platforms for Existing InTouch or Stand-alone Application Server or TSE Console
for TSE Clients Note: Select additional Device Integration Licenses based on the number of computers which will be performing IO communications. A device Integration License is only needed for any one computer that executes a Wonderware communication solution like an IO Server or a DA Server and is good for any number of interfaces executing on that node. If DI Objects are executed on the same node, a Platform license will also be needed. Only one Platform license is needed for any one computer. If the customer has an existing IO or InTouch with IO license on a computer, a Device Integration License is not needed on that computer. Step 3: Select the number of clients for visualization. There are three choices, 1) InTouch for System Platform with Trending/ Analysis (Preferred), 2) InTouch for System Platform without Trending/Analysis and 3) InTouch for System Platform Read-only with Trend/Analysis. Visualization Clients can access an unlimited number (60K technically) of object attributes, where InTouch is limited by the number of tags for which it is licensed. Standard InTouch v9.0 or greater run-times can leverage the System Platform with the addition of an Application Server Platform license. Step 4: Select the number of clients for analysis and/or reporting. There are two choices, 1) Information Server Client- for Web Report and Analysis, and 2) Historian Client- for Stand-alone, thick client reporting and analysis, including Microsoft Office support. Step 5: Select the number of Development Studio Seats based on the number of Engineers and System Administrators who will be simultaneously managing the system. A Wonderware Development Studio seat, which includes the ArchestrA IDE as well as development tools for InTouch, Historian, allows developers/administrators to create templates, instantiate system components, deploy and re-deploy components and assemble applications. Note- To use the InTouch Runtime and/or InTouch for System Platform Client portion of the Wonderware Development Studio as a production runtime client – purchase an extra platform license using Step 2. Note- you can only use the RT as either an InTouch Runtime or InTouch for System Platform Client (one, not both). A deployed Application Server Galaxy does not require that an IDE or Galaxy Repository be present to operate, but users will not be able to make changes to the system without them. Please note that when developing an ArchestrA-based application, the Wonderware Development license size is linked to the System Platform IO Run-time License Size. For Example, a Large Wonderware Development Studio License will allow you to develop and test a Galaxy up to 5,000 IO. To deploy this Application Server based application, you can use the Large Wonderware Development to connect to a 5,000 IO or smaller System Platform license. If you try to connect a Large (5,000 IO) Wonderware Development License to a 25,000 IO or larger System Platform license, the customer will be violating the Wonderware License Agreement and the IDE will not allow the connection. Step 6: Select any additional Wonderware product licenses that will be needed, such as Wonderware P&PM Modules like Equipment Operations Module (EOM) or Equipment Performance Module (EPM).
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 11 of 31
Please direct any feedback to [email protected]
5. Simple Flow Diagram for Order Process
Select System Platform Size (I/O with History)
Determine I/O Count
= Use traditional “I/O Tag” count (Real IO in PLC)
WW Development Studio
At least one is required
Select any System Platform Options needed
= Additional Device Integration Servers
and/or
Additional Wonderware Historian Servers Application Server Platform
and/or
Additional Wonderware Information Server w/Application Server Platform
Stand-alone Reporting and Analysis Clients
Standard Information Server Client- for Web Report and Analysis
or
Advanced Information Server Client- for Web Report and Analysis
and/or
Active Factory- for Stand-alone AF Clients
Wonderware MES Modules
Choose from several Wonderware MES Modules and QuickStarts
Visualization Clients
= One for every “operator station” (Note: Terminal Server requires a license for every client)
Choose from InTouch for System Platform with Trending and Analysis
and/or
InTouch for System Platform without Trending and Analysis for Graphics Only
(Add 20% of total price for redundant Terminal Server)
Customer Support
If the customer is not on Customer Support, they should be added.
Any Extra Application Server Platforms needed?
= Additional Application Server Platforms for Existing InTouch
and/or
Additional Application Server Platforms for Stand-alone Application Server (AOS)
and/or
Additional Application Server Platforms for TSE Console (Server) for TSE Clients
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 12 of 31
Please direct any feedback to [email protected]
6. Definition of Node Types described in this Document
Configuration Database Node The configuration database node consists of the Galaxy Repository (GR). The Galaxy Repository manages the configuration data associated with one or more Galaxies. This data is stored in individual databases, one for each Galaxy in the system. Microsoft SQL Server 2000 is the relational database used to store the data. The License file for the Galaxy IO and number of Platforms is a loaded on this Node. Platforms can then be deployed for use on any node where Bootstrap Software is installed. Automation Object Server (AOS) Node The Application Server is made up of all the nodes in the Galaxy Namespace. The Automation Object Server (AOS) provides the single node processing resources for Application Engines, Areas and Automation Objects (Application Objects, and DI Objects). The AOS node is enabled by a Platform. Depending on the process requirements and system capabilities, the functionality of an AOS node can be combined with a visualization node, as in a peer-to-peer topology. Visualization Client A visualization client is a computer running InTouch for System Platform with or without Historian Client, which is InTouchView plus a Platform. The Platform provides for communication with any other Galaxy components via the ArchestrA MX protocol. Information Client The Information client is a computer used to access the Information Server Content Server. This is known as an Information Server Client Access License. Trends and Office Client The Trends and Office client is a computer used to with Historian Client. It provides Microsoft Office Integration for analysis and reporting as well as trends. Historical data is provided by the Historian Node. IO Server or DA Server Node An IO or DA Server node functions as the data source for the System Platform. Running on this node are Communication Servers that can communicate with external devices. Communication protocols supported by the system are Dynamic Data Exchange (DDE), SuiteLink and OPC. DI Objects manage the communication between Application Objects and the IO or DA Servers. DI Objects require a Platform and an Application Engine to be deployed. These objects can reside either on the IO/DA Server node or on any node with a platform in the Galaxy. If the DI Objects run on the IO Server node, then a Platform is required to communicate with any other Platform in the Galaxy. Engineering Station Node All of the recommended topologies include a dedicated engineering station for maintenance purposes. The engineering station node contains an Integrated Development Environment (IDE) and InTouch WindowMaker. (These development tools are provided with a Wonderware development license). The configuration database could reside on this node. Thus, you could implement any required changes in the system from the engineering station node using the IDE, which would then access the local configuration database. This configuration provides you flexibility in maintaining remote sites, as you can use a laptop computer as the engineering station and configuration database node and gain access to the AOS Node via a LAN connection. If you need to deploy or un-deploy large applications, network traffic in the Galaxy would not be affected. The engineering station node also executes the development tools to modify InTouch applications using WindowMaker and the Network Application Development (NAD) feature of InTouch. In this document, it is assumed that the Engineering Station will not be used as a run-time Visualization Node, and therefore will not require a run-time Platform License. The Wonderware Development License contains “Dev_IO” and “Dev_Platform” feature lines, which allow you to develop and test and Application Server based applications on the local node, and to deploy objects to any node with a Platform in the Galaxy. Note: An Engineering Station can also be a visualization node with the addition of a run-time platform license. Historian Node The Wonderware Historian stores all of the historical data and also provides data to clients such as InTouch, Historian Client, Information Server, and so on. The Historian node does not technically require a Platform, but one is included as a best practice for alarm storage and future needs. It is recommended that one simply count the Historian as requiring a Platform to avoid future version issues. The Application Server pushes the data to be historized to the Historian Server using the manual data acquisition service (MDAS). Information Server Node An information server consisting of the Wonderware Information Server is part of the System Platform License. You can use the Win-XML Exporter to convert InTouch windows to XML format, so that Information Server clients can access real-time data from the Galaxy. Note on the use of network routers in the following diagrams. Depending on the requirements of the local IT Organization at the customer’s facility, network routers or bridges may be present between the PLC Network and the Control or Information Networks. Wonderware software products could reside on either network and communicate across these network routers or bridges. Routers or bridges have not been included in the drawing of these example configurations, but could be assumed to be present in place of the “Dual Nic” configurations shown.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 13 of 31
Please direct any feedback to [email protected]
7. Configuration Examples
The following examples are included for the purpose of graphically illustrating how the System Platform is licensed within a system order. The examples provided are not the only configurations customers may choose to employ, but do give a good cross-section of typical systems.
� WONDERWARE SYSTEM PLATFORM AND P&PM PILOT BUNDLE � BASIC SYSTEM PLATFORM CONFIGURATION � SUPERVISORY CLIENT SERVER CONFIGURATION WITH DEDICATED IO SERVER NODE � RUNNING IO SERVERS ON AOS NODES � COMBINING VISUALIZATION, AOS AND IO SERVERS (FULL PEER-TO-PEER) � COMBINING VISUALIZATION AND AOS ON THE SAME NODE (IO SERVERS IN A SEPARATE NODE) � IO SERVER REDUNDANCY � USING A DEDICATED TERMINAL SERVER NODE � REDUNDANT TERMINAL SERVER NODE � TERMINAL SERVER LOAD BALANCING LICENSING WITH THE SYSTEM PLATFORM � DETAIL ON DEVICE INTEGRATION LICENSING � DETAIL ON ADDING THE SYSTEM PLATFORM TO AN EXISTING INTOUCH APPLICATION (UPGRADE EXISTING INTOUCH
NODES AND ADDING PLATFORMS) � DETAIL ON ADDING THE SYSTEM PLATFORM TO AN EXISTING INTOUCH APPLICATION (NO CHANGE TO EXISTING
INTOUCH) � CONFIGURATION DATABASE (GR NODE) ON A DEDICATED COMPUTER � STANDALONE DEVELOPMENT OR NON-PRODUCTION SYSTEM � OFF-LINE MULTI-DEVELOPER ENVIRONMENT � USING IDE OVER TERMINAL SERVICES- LOW BANDWIDTH ENVIRONMENT
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 14 of 31
Please direct any feedback to [email protected]
8. Wonderware System Platform Pilot Example
PLC Network
Visualization Client
Information Server Historian andDevice Integration
Engineering StationConfiguration Database
1
2 3
4
250 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
1 1 InTouch for System Platform w/Trend
2, 3 1 System Platform 250 IO/250 History
Or
1,2,3 1 System Platform 2012R2 Starter 1 Client 1K IO/100 History (lower price method)
4 1 Wonderware Development Studio Size xx * The 250 IO SP License includes 3 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 15 of 31
Please direct any feedback to [email protected]
9. Basic System Platform Configuration
PLC Network
Trends and Office ClientInformation ClientVisualization Client
Information ServerAOS Node Historian andDevice Integration
Engineering StationConfiguration Database
1 2 3
4
7
65
5,000 IO System Platform License
= Platform Network Device
(Switch or Router)
Node Quantity License Item
4, 5, 6 1 System Platform 5K IO/5K History*
1 1 InTouch for System Platform w/Trend
2 1 Info Server Standard Client, Per Named (or Per Device) User
3 1 Historian Client Per Device
7 1 Wonderware Development Studio Size xx Note: In this example, the number of platforms required (nodes 4,5,6) prevented the use of the single client Starter Bundle (2 platforms). * The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 16 of 31
Please direct any feedback to [email protected]
10. Supervisory Client Server Configuration with Dedicated IO Server Node
PLC Network
Visualization ClientInformation ClientVisualization Client
AOS NodeAOS Node Historian
IO/OPC/DA Server
Information Server
1 2 3
4
Engineering Station
Configuration Database
7
65
8
9
5,000 IO System Platform License
= Platform
Network Device(Switch or Router)
Node Quantity License Item
1, 3 1 InTouch for System Platform w/Trend
2 1 Info Server Standard Client, Per Named (or Per Device) User
7 1 Wonderware Development Studio Size xx
4, 5, 6, 8, 9 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes
4 Application Server Platforms.
Order Summary Table
Quantity License Item
2 InTouch for System Platform w/Trend
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 17 of 31
Please direct any feedback to [email protected]
11. Running IO Servers on AOS Nodes
PLCNetwork
Information Client Visualization Client
Historian Information ServerAOS NodeI/O Server
AOS Node
I/O Server
1 2 3
4
Engineering Station
Configuration Database
765 8
Visualization Client
5,000 IO System Platform License= Platform
Network Device(Switch or Router)
Node Quantity License Item
1, 3 1 InTouch for System Platform w/Trend
2 1 Info Server Standard Client, Per Named (or Per Device) User
7 1 Wonderware Development Studio Size xx
4, 5, 6, 8 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes
4 Application Server Platforms. Order Summary Table
Quantity License Item
2 InTouch for System Platform w/Trend
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 18 of 31
Please direct any feedback to [email protected]
12. Combining Visualization, AOS and IO Servers (full Peer-to-Peer)
2 3 4 5
PLC
Network
Historian Information Server
6
Engineering Station
Configuration Database
Visualization
I/O Server
AOS
Visualization
I/O Server
AOS
Information Client
1
5,000 IO System Platform License
= Platform
Network Device(Switch or Router)
Node Quantity License Item
1 1 Info Server Standard Client, Per Named (or Per Device) User
2, 3, 4, 5 1 System Platform 5K IO/5K History
2, 3 1 InTouch for System Platform w/Trend
6 1 Wonderware Development Studio Size xx
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes
4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 19 of 31
Please direct any feedback to [email protected]
13. Combining Visualization and AOS on the same Node (IO Servers in a Separate
Node)
1 4 5
7
PLCNetwork
HistorianVisualization Information Server
6
Engineering StationConfiguration Database
IO/DA/OPC Server
AOS
3
VisualizationAOS
Information Client
2
5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
4, 5, 7 1 System Platform 5K IO/5K History
2 1 Info Server Standard Client, Per Named (or Per Device) User
1, 3 1 InTouch for System Platform w/Trend
6 1 Wonderware Development Studio Size xx
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes
4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 20 of 31
Please direct any feedback to [email protected]
14. IO Server Redundancy
PLC Network
Visualization Client Information Client Visualization Client
AOS Node AOS Node Historian Information Server
I/O Server (primary)Dual NICs
I/O Server (secondary)Dual NICs
1 2 3
4
Engineering StationConfiguration Database
765 8
9 10 5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
1, 3 1 InTouch for System Platform w/Trend
2 1 Info Server Standard Client, Per Named (or Per Device) User
7 1 Wonderware Development Studio Size xx
4, 5, 6, 8, 9, 10
1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Order Summary Table
Quantity License Item
2 InTouch for System Platform w/Trend
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 21 of 31
Please direct any feedback to [email protected]
15. Using a Dedicated Terminal Server Node
PLC Network
Historian
InTouch Terminal Server Console
AOS Node AOS Node Information Server
1
543
Engineering Station
Configuration Database
76
IO/OPC/DA Server
8
Information Client
2
Supervisory Thin Clients
5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
1 1
3
Application Server Platform
InTouch for System Platform w/Trend TSE (one T, two TP)
2 1 Info Server Standard Client, Per Named (or Per Device) User
7 1 Wonderware Development Studio Size xx
3, 4, 5, 6, 8 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms. Note: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1). For Terminal Services situations, an extra platform is needed on the Terminal Server Console (Node 1). Order Summary Table
Quantity License Item
1 Application Server Platform
1 Info Server Standard Client, Per Named (or Per Device) User
3 InTouch for System Platform w/Trend TSE (1T, 2TP)
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 22 of 31
Please direct any feedback to [email protected]
16. Redundant Terminal Server Node
PLC Network
HistorianAOS Node Information Server
65
Engineering Station
Configuration Database
87
IO/OPC/DA Server
9
Information Client
3
Supervisory Thin Clients
5,000 IO System Platform License
1
InTouch Terminal Server
Console- Primary
2
InTouch Terminal Server
Console- Secondary
= Platform
AOS Node
4
Network Device
(Switch or Router)
Node Quantity License Item
1, 2 2
3
3
Application Server Platform
InTouch for System Platform w/Trend TSE (1T, 2TP)
InTouch for System Platform w/Trend Failover TSE (1TF, 2TFP)
3 1 Info Server Standard Client, Per Named (or Per Device) User
8 1 Wonderware Development Studio Size xx
4, 5, 6, 7, 9 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms. Note: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1 and 2). The InTouch for System Platform w/Trend Failover TSE is for ordering InTouch redundancy. It is priced as 20% of the List price of the InTouch for System Platform w/Trend TSE. For Terminal Services situations extra platforms are needed on the Terminal Server Consoles (Node 1 and 2). Order Summary Table
Quantity License Item
2 Application Server Platform
3 InTouch for System Platform w/Trend TSE (1T, 2TP)
3 InTouch for System Platform w/Trend Failover TSE (1TF, 2TFP)
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 23 of 31
Please direct any feedback to [email protected]
17. Terminal Server Load Balancing Licensing with the System Platform
PLC Network
HistorianAOS Node Information Server
76
Engineering Station
Configuration Database
98
IO/OPC/DA Server
10
Information Client
4
Supervisory Thin Clients
5,000 IO System Platform License
1
InTouch Terminal
Server Console
2
InTouch Terminal
Server Console
3
InTouch Terminal
Server Console
ServerFarm
= Platform
AOS Node
5
Network Device
(Switch or Router)
Node Quantity License Item
1, 2, 3 3
4
4
Application Server Platform
InTouch for System Platform w/Trend TSE (1T, 3TP)
InTouch for System Platform w/Trend Failover TSE (2TF, 2TFP)
4 1 Info Server Standard Client, Per Named (or Per Device) User
9 1 Wonderware Development Studio Size xx
5, 6, 7, 8, 10 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms. Note: The Thin Client computers in the drawing are associated with the Terminal Server (Nodes 1,2,3). The InTouch for System Platform w/Trend Failover TSE is for ordering InTouch redundancy. It is priced as 20% of the List price of the InTouch for System Platform w/Trend TSE. For Terminal Services situations extra platforms are needed on the Terminal Server Consoles (Node 1, 2, 3). Order Summary Table
Quantity License Item
3 Application Server Platform
4 InTouch for System Platform w/Trend/Analysis TSE
4 InTouch Failover System TSE
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 24 of 31
Please direct any feedback to [email protected]
18. Detail on Device Integration Licensing
PLC Network
Information Client
AOS Node AOS Node Historian Information Server
1
3 4 56
Engineering Station
Configuration Database
7
8 9
DI Objects
DI Objects
IO/OPC/DA ServerDual NICs
IO/OPC/DA ServerDual NICs
Visualization Client
2
5,000 IO System Platform License
= Platform
Network Device(Switch or Router)
Node Quantity License Item
1 1 Info Server Standard Client, Per Named (or Per Device) User
2 1 InTouch for System Platform w/Trend
9 1 Application Server Platform
7 1 Wonderware Development Studio Size xx
3, 4, 5, 6, 8, 9
1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms. Node 9 IO Server is included in the SP, but node 9 platform is a la cart. Node 8 does not need a Platform because it is not hosting DI Objects.
Order Summary Table
Quantity License Item
1 Info Server Standard Client, Per Named (or Per Device) User
1 InTouch for System Platform w/Trend/Analysis
1 Application Server Platform
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Notes on DA Servers and DI Objects: Data Access Servers (DA Servers) are deployed with Device Integration Network (DI Net) Objects and facilitate communications with DI Device objects to their respective hardware. In addition, DA Servers can be installed standalone to provide communications to any OPC, SuiteLink, or DDE client. DI Objects represent the communication with external devices. DI Objects run on a local Application Engine, and require a Platform to operate.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 25 of 31
Please direct any feedback to [email protected]
19. Detail on adding the System Platform to an Existing InTouch Application
(Upgrade Existing InTouch nodes and adding Platforms)
PLC
Network
Visualization Client Information Client Visualization Client
Historian Information ServerAOS Node
I/O Server
1 2 3
Engineering Station
Configuration Database
7
54
6
Note: Node 1 and 3 are used as the
System Platform Visualization Client by re-using existing InTouch License
and adding a Platform.
5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
4, 5, 6 1 System Platform 5K IO/5K History
2 1 Info Server Standard Client, Per Named (or Per Device) User
1, 3 1 Application Server Platform
7 1 Wonderware Development Studio Size xx
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Note: In this scenario, a customer is keeping their existing InTouch Applications (1 and 3) and adding an AOS Node and using the existing InTouch Nodes as HMI Stations. The Customer may or may not choose to migrate functions from the existing InTouch tag-based Applications to the Application Server objects. Order Summary Table
Quantity License Item
1 System Platform 5K IO/5K History
1 Info Server Standard Client, Per Named (or Per Device) User
2 Application Server Platform
1 Wonderware Development Studio Size xx
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 26 of 31
Please direct any feedback to [email protected]
20. Detail on adding the System Platform to an Existing InTouch Application (No
Change to Existing InTouch)
PLC
Network
InTouch Node7.11 or Older
Historian
AOS NodeI/O Server
1 2 3
Engineering Station
Configuration Database
7
54
6
InTouch NodeInTouch 10.0
Information Client
Existing Existing
Note for node 1: IAS 3.0 supports InTouchnodes only for versions 10.0, 9.5 or 9.0 P02. Similar InTouch version compatibility limitations apply to newer SP versions (reference ReadMe document for SP for details). The only thing you can do with this old InTouch node is to communicate from galaxy to InTouch node thought InTouch Proxy Object.
Because node 3 is an InTouch 10 with a Platform, this adds remote reference capability from InTouch to AOS.
Information Server
5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item
4, 5, 6 1 System Platform 5K IO/5K History
2 1 Info Server Standard Client, Per Named (or Per Device) User
3 1 Application Server Platform
7 1 Wonderware Development Studio Size xx
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 27 of 31
Please direct any feedback to [email protected]
21. Configuration Database (GR Node) on a Dedicated Computer
PLC
Network
Visualization Client Information Client Visualization Client
Historian Information ServerAOS Node
IO/OPC/DA Server
1 2 3
4
Engineering Station
8
5
Configuration DB
(GR Node)
7
6
5,000 IO System Platform License
= Platform
Network Device
(Switch or Router)
Node Quantity License Item Part #
1, 3 1 InTouch for System Platform w/Trend
2 1 Info Server Standard Client, Per Named (or Per Device) User
8 1 Wonderware Development Studio Size xx
4, 5, 6, 7 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Order Summary Table
Quantity License Item
2 InTouch for System Platform w/Trend
1 Info Server Standard Client, Per Named (or Per Device) User
1 Wonderware Development Studio Size xx
1 System Platform 5K IO/5K History
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 28 of 31
Please direct any feedback to [email protected]
22. Standalone Development or Non-production System
Node Quantity License Item
1 1 Wonderware Development Studio Size xx, v10.0
Note: Allows a user to:
• Develop and test Application Objects locally
• Maintenance Engineers and Support Personnel to link into an existing system to make changes. It is assumed that the customer already has the Galaxy Repository Node installed.
Wonderware® Development Studio is an integrated, component-based application development environment. With Wonderware Development Studio, you have access to all the information and functionality you need to develop your factory information, visualization or SCADA application including an HMI (Human Machine Interface), data collection, historian, control and optimization, and analysis. The Wonderware Development Studio License is to be installed on one computer only and provides:
• A single package for development of all Wonderware Products. This includes InTouch and InTouch for System Platform applications used with the Wonderware System Platform.
• The ability to create, edit, deploy and manage ArchestrA Objects as part of a Wonderware System Platform Galaxy Namespace.
• A base historian (Historian Server Standard Edition) for use with InTouch or the Wonderware System Platform. The base Historian Server is limited to 24 Hour data retrieval. For a full Historian Server for use in production, please refer to the Report and Analysis Tab or the System Platform Tab
Note: A Wonderware Development Studio can be used as a stand-alone InTouch-only or a runtime client within a Wonderware System Platform Galaxy Namespace by simply purchasing an additional runtime Application Server Platform License for use on this node.
Wonderware Development Studios comes in 5 Sizes:
Package Size InTouch Only Development and Runtime Tag Limit
InTouch for System Platform Development and Runtime Remote Reference Limit
ArchestrA Galaxy Connection and Development IO Limit
InSQL Runtime Tag Limit
Limited 64 64 NA NA
Small 500 Unlimited 250 100
Medium 1,000 Unlimited 1,000 100
Large 3,000 Unlimited 5,000 500
Unlimited 60K Unlimited Any Size 500
Note: Because of the new smaller, lower priced options, Wonderware Information Server, Historian Client run-times are only included in the unlimited version.
Wonderware Developments Studio is tied to the size of the Galaxy Run-time License. For example, a small Wonderware Development Studio can create, connect to and deploy to a 250 IO Run-time Galaxy. A Large Wonderware Development can create, connect to and deploy to a 250 IO, 1,000 IO, 2,500 IO or 5,000 IO Run-time Galaxies. A Small Wonderware Development cannot create, connect to or deploy to a 1,000 IO or larger Run-time Galaxy.
Engineering Station 1
Configuration DB
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 29 of 31
Please direct any feedback to [email protected]
23. Off-Line Multi-Developer Environment
HistorianConfiguration DB
(GR Node)
1 2
54
Engineering Station Engineering Station
3
Engineering Station
Information Server
6
7
Information Client
5,000 IO System Platform License
= Platform
Node Quantity License Item
1-3 3 Wonderware Development Studio Size xx
7 1 Info Server Standard Client, Per Named (or Per Device) User
4, 5, 6 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 30 of 31
Please direct any feedback to [email protected]
24. USING IDE OVER TERMINAL SERVICES- LOW BANDWIDTH
ENVIRONMENT
RS-485Network
RTU Radio Modem
Level
transmitter
PRINTHELPALPHASHIFTENTERRUNDGERFIAJBKCL7M8N9ODGDGDGDGT3U0V.WXYZTAB%UTILIZATIONHUB/MAUNIC2BNC4Mb/s
L
PRINTHELPALPHASHIFTENTERRUNDGERFIAJBKCL7M8N9ODGDGDGDGT3U0V.WXYZTAB%UTILIZATIONHUB/MAUNIC2BNC4Mb/s
Level
transmitter
L
(RS-232)
RTU Radio Modem
Dial-up28.8K bps
line
Ethernet
Historian (Dataand Alarms) Information Server
Engineering StationConfiguration Database
AOS Node
HEWLETTPACKARD
Router
RTU Radio Modem
Control Network
Terminal Server or
Visualization
ClientVisualization
ClientInformation
Client
IO/OPC
/DA Server
1 2 34
TS Client
Engineering Station
5
8 9 1011
Remote Desktop
TS Client
Engineering Station
6
TS Client
Engineering Station
7
5,000 IO System Platform License
= Platform
Node Quantity License Item
1, 2 1 InTouch for System Platform w/Trend
3 1 Info Server Standard Client, Per Named (or Per Device) User
4 1 Application Server Platform
5, 6, 7 3 Wonderware Development Studio Size xx for TSE
8, 9, 10, 11 1 System Platform 5K IO/5K History
* The System Platform license is for the entire Galaxy. The 5,000 IO SP License is an example. It includes 4 Application Server Platforms.
Licensing Wonderware System Platform Version 2012R2 (7-4-13).docx
Invensys Wonderware Inc. Page 31 of 31
Please direct any feedback to [email protected]
Order Summary Table
Quantity License Item
2 InTouch for System Platform w/Trend
1 Info Server Standard Client, Per Named (or Per Device) User
1 Application Server Platform
3 Wonderware Development Studio Size xx for TSE
1 System Platform 5K IO/5K History
Note: Over a low-bandwidth network, Terminal Services or Remote Desktop has been found to be a more optimal means for making a change to a running Galaxy Repository as opposed to having the IDE located at a remote site. To make sure the customer is within license, there is a license available for all 4 sizes of the Wonderware Development for use inside of a Terminal Services environment. This license is required for any computer that will access an existing Wonderware Development over the network through a Terminal Services session. It is a seat-based license and not concurrent. Please note that Microsoft bundles the Remote Desktop Client (RDC) with Windows XP and Windows 2003. This allows a user to establish a single remote desktop connection to any computer running these operating systems, providing that they have a user account on the computer. The purpose of RDC is to allow the normal user of the computer to access and use their applications remotely if needed. Therefore, a Wonderware Development for TSE License is not needed if the customer wants a single remote connection to an existing Wonderware Development Seat using RDC. It is only required if multiple on-line sessions are being severed using Microsoft Terminal Server.