Licensing Industrial Application Server Rev D

261861553.
doc
INVENSYS WONDERWARE CORPORATION
Licensing Guide for the

Industrial Application
Server
Copyright 2003 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
Invensys Wonderware Corporation
Page 1 of 40
261861553.doc
Version History
Version
Type
Date
Author
Draft
5/2/03
S. Garbrecht
Draft
5/19/03
S. Garbrecht
Final
6/9/03
S Garbrecht
Description
Final Version
Page 2 of 40
261861553.doc
Table of Contents
LICENSING GUIDE FOR THE INDUSTRIAL APPLICATION SERVER ................................................1
VERSION HISTORY..................................................................................................................................................................2
1.
INTRODUCTION................................................................................................................................................................4
2.
GENERAL GUIDELINES FOR LICENSING THE FACTORYSUITE A2 SYSTEM.................................................4
3.
STEPS IN THE ESTIMATION OF A FACTORYSUITE A2 LICENSE WITH THE APPLICATION SERVER.....5
4.
DEFINITION OF NODE TYPES DESCRIBED IN THIS DOCUMENT.....................................................................6
5.
CONFIGURATION EXAMPLES......................................................................................................................................7
6.
CLIENT SERVER CONFIGURATION WITH DEDICATED I/O SERVER NODE..................................................8
7.
RUNNING I/O SERVERS ON AOS NODES.................................................................................................................10
8.
COMBINING VISUALIZATION, AOS AND I/O SERVERS IN A SINGLE NODE (FULL PEER-TO-PEER)....12
9.
COMBINING VISUALIZATION AND AOS ON THE SAME NODE (I/O SERVERS IN A SEPARATE NODE)14
10. I/O SERVER REDUNDANCY.........................................................................................................................................16

11. USING A DEDICATED TERMINAL SERVER NODE................................................................................................18
12. REDUNDANT TERMINAL SERVER NODE................................................................................................................20
13. TERMINAL SERVER LOAD BALANCING LICENSING WITH THE APPLICATION SERVER......................22
14. RUNNING A TERMINAL SERVER ON AN AOS NODE............................................................................................24
15. DETAIL ON WEB SERVER (SUITE VOYAGER) LICENSING WITH THE APPLICATION SERVER.............26
16. DETAIL ON ACTIVEFACTORY LICENSING WITH THE APPLICATION SERVER..........................................28
17. DETAIL ON DEVICE INTEGRATION LICENSING..................................................................................................30
18. DETAIL ON ADDING THE APPLICATION SERVER TO AN EXISTING INTOUCH APPLICATION
(UPGRADE TO INTOUCH 8.0 WITH PLATFORM)..........................................................................................................32
19. DETAIL ON ADDING THE APPLICATION SERVER TO AN EXISTING INTOUCH APPLICATION (NO
CHANGE TO EXISTING INTOUCH)...................................................................................................................................34
20. CONFIGURATION DATABASE (GR NODE) ON A DEDICATED COMPUTER...................................................36
21. STANDALONE DEVELOPMENT OR NON-PRODUCTION SYSTEM...................................................................38
22. OFF-LINE MULTI-DEVELOPER ENVIRONMENT..................................................................................................39
23. GLOSSARY OF TERMS..................................................................................................................................................40
Page 3 of 40
261861553.doc
1. Introduction
Purpose of this Document
This document is used as a guide in determining the license requirements for a FactorySuite A 2 system, which
utilizes the Industrial Application Server. It is a companion to the Wonderware FactorySuite A 2 Deployment
Guide and the Wonderware Global Price List. All three documents should be used when estimating the total
licensed price for a system.
Users of this document will include Sales Personnel and Estimators who develop proposals which include the
Industrial Application Server. In addition to the Application Server, the following Wonderware products may
also be present:
FactorySuite Development 8.0 or higher

InTouch View 8.0 or higher
InTouch 8.0 or higher
InSQL Server 8.0 SP1 or higher
InTouch for Terminal Services 8.0 or higher
Suite Voyager 2.0 or higher
Active Factory 8.0 or higher
and others.
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 FactorySuite A2 System
The Industrial Application Server is designed to leverage existing Wonderware products such as
InTouch for visualization, Industrial SQL as its historian, and the device Integration product line (I/O
Servers and DA Servers) for device communication. The Industrial Application Server uses InTouch
v8.0 or InTouchView v8.0 for visualization with the addition of Application Server Platforms on the
visualization node.
The Run-time Environment for the Industrial Application Server is sized by the number of Workstation /
Server and Terminal Services Platforms and real I/O in a single Galaxy Namespace. A single Industrial
Application Server license consists of I/O, Platforms, and/or Terminal Service Platforms with
corresponding session count.
A Platform associated with an Application Server includes a per-seat FSCAL2000 (which includes a
Microsoft 2000 SQL Server CAL) for sole use with Wonderware products.
The Development Environment for the Industrial Application Server is the IDE, which is included in the
FactorySuite A2 Development License. The FS A2 Development License also includes a single per seat
MS 2000 SQL Server CAL. This allows the Galaxy Repository to be stored on this node, but the ability
to execute automation objects in a production environment is not authorized. Users can however build
and deploy a Galaxy and automation objects on the local node for test purposes.
Page 4 of 40
261861553.doc
3. Steps in the estimation of a FactorySuite A2 License with the Application Server

Step 1: Select the appropriate Application Server I/O level for the Application Server System. I/O count is
based on the number of I/O points that are configured through an OPC Server, I/O Server, DA Server or
InTouch Proxy Object, over the whole Galaxy Namespace, regardless of how many PCs are in the system.
Step 2: Select the number of Application Server Platforms required. Use the same part number to order
Platforms with a new Application Server and to add Platforms to an existing Application Server. Each
Workstation and/or Automation Object Server communicating directly within the Galaxy requires a Platform,
with exception of:
IndustrialSQL Server Nodes
Standalone interface nodes that execute I/O Servers, OPC Servers, and DA Servers without local DI
Objects. In this case, the DI Objects are executed on the same computer as the Application Objects.
ActiveFactory Nodes that do not contain InTouch.
FactorySuite A2 Development Nodes that do not contain a GR Database (IDE Only) or are used as a
single node development station with no connection to other production platforms.
Step 3: Select the number of Terminal Services Platforms and the number of sessions for each TS Platform.
At least one session must be ordered with each TS Platform. Terminal Services Platforms can also be used to
execute Automation Objects.
Step 4: Select the number of InTouch View or InTouch client licenses. InTouch View Client, v8.0s are InTouch
RT v8.0 that requires the Industrial Application Server as its sole data source. Standard InTouch v8.0 runtimes
can leverage the Industrial Application Server with the addition of a Platform license. When licensing a new
system that includes the Industrial Application Server, InTouch View is the preferred client as it is usually less
expensive than standard InTouch and the Application Server provides the supervisory control services (alarms,
scripting, I/O, etc.) needed for the system. Existing InTouch Nodes only need a Platform license to be part of
the Galaxy Namespace.
Step 5: Select the number of Development Seats based on the number of Engineers and System
Administrators who will be simultaneously managing the system. A FactorySuite A 2 Development seat, which
includes the ArchestrA IDE as well as development tools for InTouch, InSQL and InControl allows
developers/administrators to create templates, instantiate system components, deploy and re-deploy
components and assemble applications.
A deployed Industrial 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.
Step 6: Select Device Integration Licenses based on the number of computers which will be performing I/O
communications. A device Integration License is needed for any computer that executes a Wonderware I/O
Server, OPC Server or DA Server and is good for any number if 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 I/O or InTouch with I/O license on a computer, a
Device Integration License is not needed on that computer. Note: For Third party I/O Servers, please contact
the specific vendor.
Step 7: Select the appropriate Industrial SQL Server license based on the number of attributes that will be
historized.
Step 8: Select any additional Wonderware product licenses that will be needed, like SuiteVoyager,
ActiveFactory, InBatch, InControl, InTrack, etc. Also consider any additional FactorySuite CALs or Terminal
Services CALs that are required to run with the FactorySuite component.
Page 5 of 40
261861553.doc
4. 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.
Automation Object Server (AOS) Node
The Industrial 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 Node
A visualization node is a computer running InTouch View 8.0 or higher on top of a Platform. The Platform provides for
communication with any other Galaxy components via the ArchestrA MX protocol, which is based on the Microsoft
Message Queuing technology.
I/O Server Node
An I/O Server node functions as the data source for the Industrial Application Server system. Running on this node are
I/O Servers that can communicate with external devices. Communication protocols supported by the system are Dynamic
Data Exchange (DDE), SuiteLink and OPC.
On the Industrial Application Server side, DI Objects manage the communication between Application Objects and the
I/O Servers. DI Objects require a Platform and an Application Engine to be deployed. These objects can reside either on
the I/O Server node or on any node with a platform in the Galaxy. If the DI Objects run on the I/O 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 FactorySuite A2 development package.) 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.
Historian Node
The historian node is used to run IndustrialSQL Server. IndustrialSQL Server stores all of the historical data and also
provides real-time data to clients such as ActiveFactory, SuiteVoyager, and so on. The historian node does not require a
Platform. The Application Server pushes the data to be historized to the IndustrialSQL Server using the manual data
acquisition service (MDAS).
Web Server Node
A web server consisting of SuiteVoyager Server could be included in any Galaxy. You can use the Win-XML
Exporter to convert InTouch windows to XML format, so that SuiteVoyager clients can access real-time data
from the Galaxy. In order to provide the means for the SuiteVoyager Server to access the Galaxy, a Platform is
required to be deployed on the web server node.
Page 6 of 40
261861553.doc
5. Configuration Examples
The following examples are included for the purpose of graphically illustrating how the Industrial Application
Server 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.
CLIENT SERVER CONFIGURATION WITH DEDICATED I/O SERVER NODE

RUNNING I/O SERVERS ON AOS NODES
COMBINING VISUALIZATION, AOS AND I/O SERVERS IN A SINGLE NODE (FULL PEER-TO-PEER)
COMBINING VISUALIZATION AND AOS ON THE SAME NODE (I/O SERVERS IN A SEPARATE
NODE)
I/O SERVER REDUNDANCY
USING A DEDICATED TERMINAL SERVER NODE
REDUNDANT TERMINAL SERVER NODE
TERMINAL SERVER LOAD BALANCING LICENSING WITH THE APPLICATION SERVER
RUNNING A TERMINAL SERVER ON AN AOS NODE
DETAIL ON WEB SERVER (SUITE VOYAGER) LICENSING WITH THE APPLICATION SERVER
DETAIL ON ACTIVEFACTORY LICENSING WITH THE APPLICATION SERVER
DETAIL ON DEVICE INTEGRATION LICENSING
DETAIL ON ADDING THE APPLICATION SERVER TO AN EXISTING INTOUCH APPLICATION
(UPGRADE TO INTOUCH 8.0 WITH PLATFORM)
DETAIL ON ADDING THE APPLICATION SERVER 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
Page 7 of 40
261861553.doc
6. Client Server Configuration with Dedicated I/O Server Node
Node
Quantity
License Item
Part #
InTouch View Client, v8.0
01-0182
Platforms for Industrial Application Server
19-0003
01-0182
19-0003
01-0182
19-0003
19-0003
19-0003
IndustrialSQL Server xx,xxx Tag, v8.0
17-013x
FactorySuite A2, Development Edition, v8.0
97-1069
19-0003
2
3
See Detail in Section 15
Device Integration, I/O Server License, v8.0
04-2036
Industrial Application Server, xx,xxx IO, v1.0
19-000x
* The Industrial Application I/O license is for the entire Galaxy.
Page 8 of 40
261861553.doc
Order Summary Table- Client Server Configuration with Dedicated I/O Server Node
Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Note: See Detail in Section 15 for additional Web Server (Suite Voyager) licenses. The additional Platform
License needed for the Suite Voyager node is not included in this table.
Page 9 of 40
261861553.doc
7. Running I/O Servers on AOS Nodes
Node
Quantity
License Item
Part #
01-0182
19-0003
01-0182
19-0003
01-0182
19-0003
19-0003
04-2036
19-0003
04-2036
17-013x
97-1069
19-0003
2
3
4
5
8
*
*

1
19-000x
The Industrial Application I/O license is for the entire Galaxy.
Page 10 of 40
261861553.doc
Order Summary Table- Running I/O Servers on AOS Nodes

Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Page 11 of 40
261861553.doc
8. Combining Visualization, AOS and I/O Servers in a Single Node (full Peer-to-
Peer)
Node
Quantity
License Item
Part #
InTouch View Client, v8.0,
01-0182
19-0003
04-2036
01-0182
19-0003
04-2036
17-013x
97-1069
19-0003
5
*

1
19-000x
Page 12 of 40
261861553.doc
Order Summary Table- Combining Visualization, AOS and I/O Servers in a Single Node (full
Peer-to-Peer)
Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Page 13 of 40
261861553.doc
9. Combining Visualization and AOS on the same Node (I/O Servers in a Separate
Node)
Node
Quantity
License Item
Part #
01-0182
19-0003
01-0182
19-0003
17-013x
97-1069
19-0003
04-2036
19-000x
Page 14 of 40
261861553.doc
Order Summary Table- Combining Visualization and AOS on the same Node (I/O Servers in a
Separate Node)
Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Page 15 of 40
261861553.doc
10.
I/O Server Redundancy
Node
Quantity
License Item
Part #
1-3
01-0182
19-0003
19-0003
19-0003
17-013x
97-1069
19-0003
04-2036
10
04-2036
19-000x
Page 16 of 40
261861553.doc
Order Summary Table- I/O Server Redundancy

Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Page 17 of 40
261861553.doc
11.Using a Dedicated Terminal Server Node
Node
License Item
Part #
Terminal Server Platforms and TS sessions for Industrial Application Server
19-0005TP
InTouch for Terminal Services View Client , v8.0
01-0183T/TP
2-3
19-0003
17-013x
97-1069
19-0003
Quantity
3
04-2036
19-000x

Note 1: For Further information, refer to Licensing Requirements for InTouch for Terminal Services.
Note 2: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1).
Page 18 of 40
261861553.doc
Order Summary Table- Using a Dedicated Terminal Server Node

Quantity
License Item
Part #
Terminal Server Platforms and TS sessions for Industrial

Application Server
19-0005TP
01-0183T/TP
19-0003
17-013x
97-1069
04-2036
19-000x
Page 19 of 40
261861553.doc
Redundant Terminal Server Node
12.
Node
1-2
Quantity
6
License Item
Part #
19-0005TP
01-0183T/TP
Terminal Services for InTouch, v8.0, Failover System
01-2040TP
3-4
19-0003
17-013x
97-1069
19-0003
04-2036
19-000x

Note 2: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1 and 2).
Page 20 of 40
261861553.doc
Order Summary Table- Redundant Terminal Server Node

Quantity
License Item
Part #

Application Server
19-0005TP
01-0183T/TP
19-0003
17-013x
97-1069
04-2036
19-000x
01-2040TP
Page 21 of 40
261861553.doc
Terminal Server Load Balancing Licensing with the Application Server
13.
Node
License Item
Part #
19-0005TP
01-0183T/TP
01-2040TP
4-5
19-0003
17-013x
97-1069
19-0003
1-3
Quantity
9
04-2036
19-000x

Note 2: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1,2 and 3).
Page 22 of 40
261861553.doc
Order Summary Table- Terminal Server Load Balancing Licensing with the Application Server
Quantity
License Item
Part #

Application Server
19-0005TP
01-0183T/TP
19-0003
17-013x
97-1069
04-2036
19-000x
01-2040TP
Page 23 of 40
261861553.doc
14.
Running a Terminal Server on an AOS Node
Node
1
License Item
Part #
19-0005TP
01-0183T/TP
19-0003
17-013x
97-1069
19-0003
04-2036
19-000x
Quantity
3
The Industrial Application I/O license is for the entire Galaxy.
Note 1: The Thin Client computers in the drawing are associated with the Terminal Server (Node 1).
Page 24 of 40
261861553.doc
Order Summary Table- Running a Terminal Server on an AOS Node

Quantity
License Item
Part #

Application Server
19-0005TP
01-0183T/TP
19-0003
17-013x
97-1069
04-2036
19-000x
Page 25 of 40
261861553.doc
Detail on Web Server (Suite Voyager) Licensing with the Application Server
15.
Node
License Item
Part #
1-2
19-0003
17-013x
97-1069
19-0003
SuiteVoyager Basic Portal, v2.0
09-0009
19-0003
SuiteVoyager Client Access License (quantity 1-300) concurrent, v1.0
09-0002
FSCAL2000 per Seat with MS SQL Server CAL single license1
17-0092TP
04-2036
19-000x
6
*
Quantity

Note 1: Optionally, a per-server, FSCAL2000 per Processor with MS SQL Server CAL, Part Number: 17-0098 can be used in lieu of the 3
FSCAL2000 per Seat with MS SQL Server CAL single licenses.
Note 2: The Thin Client computers in the drawing are associated with the Web Server (Node 5).
Page 26 of 40
261861553.doc
Order Summary Table- 15. Detail on Web Server (Suite Voyager) Licensing with the Application
Server
Quantity
License Item
Part #
19-0003
17-013x
97-1069
SuiteVoyager Basic Portal, v2.0
09-0009
SuiteVoyager Client Access License (quantity 1-300) concurrent, v1.0
09-0002
FSCAL2000 per Seat with MS SQL Server CAL single license
17-0092TP
04-2036
19-000x
Page 27 of 40
261861553.doc
Detail on ActiveFactory Licensing with the Application Server
16.
Node
1-2
3
Quantity
License Item
Part #
FSCAL2000 per Seat with MS SQL Server CAL, single license
17-0092TP
ActiveFactory Per Seat, v8.0
17-0142
19-0003
17-0142
01-0182
4-5
19-0003
17-013x
97-1069
19-0003
04-2036
19-000x
Page 28 of 40
261861553.doc
Order Summary Table- Detail on ActiveFactory Licensing with the Application Server
Quantity
License Item
Part #
FSCAL2000 per Seat with MS SQL Server CAL, single license
17-0092TP
17-0142
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Page 29 of 40
261861553.doc
Detail on Device Integration Licensing
17.
Node
Quantity
01-0182
19-0003
2-3
19-0003
17-013x
97-1069
19-0003
License Item
Part #
04-2036
04-2036
19-0003
19-000x
Page 30 of 40
261861553.doc
Order Summary Table- Detail on Device Integration Licensing

Quantity
License Item
Part #
01-0182
19-0003
17-013x
97-1069
04-2036
19-000x
Notes on DA Servers and DI Objects:

Data Access Servers (DA Servers) are executables that interface with DI Object (DI Network and DI Device
objects) in the Application Server environment or with any third-party client, via standard OPC client protocols.
DA Servers are the next generation of I/O Servers.
DI Objects represent the communication with external devices. DI Objects run on a local Application Engine,
and include DINetwork and DIDevice objects. A DI Device Object is an object that represents the actual
external device (for example, a PLC or RTU) that is associated with a DINetwork Object. It provides the ability
to diagnose and browse data registers of the DAGroups for that device. A DI Network Object is an object that
represents the network interface port to the device via the Data Access Server. It provides diagnostics and
configuration for that specific network card.
Page 31 of 40
261861553.doc
Detail on adding the Application Server to an Existing InTouch Application

(Upgrade to InTouch 8.0 with Platform)
18.
Node
Quantity
License Item
Part #
19-0003
19-0003
19-0003
19-0003
04-2036
17-013x
97-1069
19-0003
7
*

1
19-000x
Page 32 of 40
261861553.doc
Order Summary Table- Detail on adding the Application Server to an Existing InTouch
Application (Upgrade to InTouch 8.0 with Platform)
Quantity
License Item
Part #
19-0003
17-013x
97-1069
04-2036
19-000x
By upgrading to InTouch 8.0 and adding a Platform, this option allows the existing InTouch nodes to
communicate via Message Exchange and to be part of the same Galaxy Namespace.
Page 33 of 40
261861553.doc
Detail on adding the Application Server to an Existing InTouch Application

(No Change to Existing InTouch)
19.
Node
Quantity
License Item
Part #
(No new software)
N/A
(No new software)
N/A
(No new software)
N/A
19-0003
04-2036
17-013x
97-1069
19-0003
7
*

1
19-000x
Page 34 of 40
261861553.doc
Order Summary Table- Detail on adding the Application Server to an Existing InTouch
Application (No Change to Existing InTouch)
Quantity
License Item
Part #
19-0003
17-013x
97-1069
04-2036
19-000x
Page 35 of 40
261861553.doc
20.
Configuration Database (GR Node) on a Dedicated Computer
Node
Quantity
01-0182
19-0003
01-0182
19-0003
01-0182
19-0003
19-0003
04-2036
19-0003
17-013x
97-1069
2
3
4
8
*
License Item
Part #

1
19-000x
Page 36 of 40
261861553.doc
Order Summary Table- Configuration Database (GR Node) on a Dedicated Computer

Quantity
License Item
Part #
01-0182
19-0003
04-2036
17-013x
97-1069
19-000x
Page 37 of 40
261861553.doc
Standalone Development or Non-production System
21.
Engineering Station
Configuration DB
Node
Quantity
License Item
Part #
97-1069
Note: Allows a user to:

-
Develop and test Applications 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.
FactorySuite A2 Development Seat includes:

IDE (Integrated Development Environment), plus Dev I/O Platforms for Industrial Application Server - Not
licensed for Runtime use
InTouch Development 60K Tag, v8.0
-
Version 8.0 supported on MS Windows XP, Windows 2000 Professional, Server or Advanced
Server
InTouch options include Recipe, SPC Pro, SQL Access
InTouch v8.0 alarm logging supported on MS SQL Server 2000/MSDE 2000. MSDE 2000
included.
MS SQL Server 2000

I/O Server Pack, OPCLink, DA Servers
IndustrialSQL Server (Develop 70K tag; Use 500 tag), v8.0
- ActiveFactory per Seat, v8.0
FactorySuite Client Access License 2000 (FSCAL2000) per seat mode with MS SQL Server 2000 CAL (can
also be used for MS SQL 7.0*)
InControl, InControl Objects, and InControl I/O Drivers, v7.11
Page 38 of 40
261861553.doc
22.
Off-Line Multi-Developer Environment
Node
Quantity
License Item
1-3
97-1069
19-0003
17-013x
Part #
Page 39 of 40
261861553.doc
23.
Glossary of Terms
Please see FactorySuite A2 Industrial Application Server Glossary of Terms document.
Page 40 of 40

Licensing Industrial Application Server Rev D

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Licensing Industrial Application Server Rev D

Uploaded by

Copyright:

Available Formats

261861553.

INVENSYS WONDERWARE CORPORATION

Licensing Guide for the

Copyright 2003 Wonderware Corporation

Invensys Wonderware Corporation

GENERAL GUIDELINES FOR LICENSING THE FACTORYSUITE A2 SYSTEM.................................................4

STEPS IN THE ESTIMATION OF A FACTORYSUITE A2 LICENSE WITH THE APPLICATION SERVER.....5

DEFINITION OF NODE TYPES DESCRIBED IN THIS DOCUMENT.....................................................................6

CLIENT SERVER CONFIGURATION WITH DEDICATED I/O SERVER NODE..................................................8

RUNNING I/O SERVERS ON AOS NODES.................................................................................................................10

10. I/O SERVER REDUNDANCY.........................................................................................................................................16

Invensys Wonderware Corporation

FactorySuite Development 8.0 or higher

2. General Guidelines for Licensing the FactorySuite A2 System

Invensys Wonderware Corporation

3. Steps in the estimation of a FactorySuite A2 License with the Application Server

Invensys Wonderware Corporation

4. Definition of Node Types described in this Document

Invensys Wonderware Corporation

CLIENT SERVER CONFIGURATION WITH DEDICATED I/O SERVER NODE

Invensys Wonderware Corporation

6. Client Server Configuration with Dedicated I/O Server Node

InTouch View Client, v8.0

Platforms for Industrial Application Server

InTouch View Client, v8.0

Platforms for Industrial Application Server

InTouch View Client, v8.0

Platforms for Industrial Application Server

Platforms for Industrial Application Server

Platforms for Industrial Application Server

IndustrialSQL Server xx,xxx Tag, v8.0

FactorySuite A2, Development Edition, v8.0

Platforms for Industrial Application Server

See Detail in Section 15

Device Integration, I/O Server License, v8.0

Industrial Application Server, xx,xxx IO, v1.0

* The Industrial Application I/O license is for the entire Galaxy.

Invensys Wonderware Corporation

InTouch View Client, v8.0

Platforms for Industrial Application Server

IndustrialSQL Server xx,xxx Tag, v8.0

FactorySuite A2, Development Edition, v8.0

Device Integration, I/O Server License, v8.0

Industrial Application Server, xx,xxx IO, v1.0

Invensys Wonderware Corporation

7. Running I/O Servers on AOS Nodes

InTouch View Client, v8.0

Platforms for Industrial Application Server

InTouch View Client, v8.0

Platforms for Industrial Application Server

InTouch View Client, v8.0

Platforms for Industrial Application Server

Platforms for Industrial Application Server

Device Integration, I/O Server License, v8.0

Platforms for Industrial Application Server

Device Integration, I/O Server License, v8.0

IndustrialSQL Server xx,xxx Tag, v8.0

FactorySuite A2, Development Edition, v8.0

Platforms for Industrial Application Server

See Detail in Section 15

Industrial Application Server, xx,xxx IO, v1.0

The Industrial Application I/O license is for the entire Galaxy.

Invensys Wonderware Corporation

Order Summary Table- Running I/O Servers on AOS Nodes