NORME ISA95 (Pyramide du CIM “Computer Integrated Manufacturing”)

1
SCADA ET MES une répartition fonctionnelle
SCADA
▪ Acquisition de données du contrôle-commande
▪ l'affichage des synoptiques animés qu'ils en forment en temps réel de l'état de l'installation
▪ la gestion des alarmes
▪ Recettes de supervision «envoi à l'automate des listes de consignes pour l'exécution d'une opération automatisés»

MES (Système d’exécution des fabrications)

▪ C’est un system d’information permettant de relier, des équipements de surveillances,
des contrôleurs de système de fabrication complexe avec le flux des données utilisé
dans L’usine. Son rôle principal est d’assurer une exécution efficace des OFs et une
amélioration des résultats de productions.
▪ MES est utilisé comme une couche fonctionnelle entre le ERP et système de contrôle de
processus dans l’usine
▪ Acquisition des données de production
▪ La planification détaillée « ordonnancement la gestion des ressources »
▪ Gestion des ressources
▪ lancement et le suivi des OF
▪ Traçabilité / Suivi des lots
▪ Analyse de performance en particulier le TRS (Taux de rendement synthétique)
2
MES: Réseaux
▪ Respect MES Networks Design
▪ Controls network
▪ Plant Production network
▪ Business network
▪ Corporate wide area network (WAN)
▪ Controls network
o Contains all machine controllers [PLC (programmable logic controller), DCS (distributed control system), SCADA
(supervisory control and data acquisition), etc.]
o It might contain several segments distributed throughout the plant
o This network allows separation of the controls system from the rest of the network for security and bandwidth
issues
o It is characterized by a high volume of traffic, usually more or less constant
o Generally, supervisory control systems (InTouch) or MES clients should not be on the Controls network
o The Operation Integration Servers (OIS) should be on the Controls network. The OIS must also be able to connect
to your Application Server
▪ Plant Production Network
o Is the main MES network. It will host or provide access to all MES servers.
o The direct access clients (Engineering station, Supervisor station, and Operator stations) usually will be on this
network.
o Allows controlled access to the shop floor systems.
o Office users are not on this network, as they might download large files that could interfere with data acquisition
or access to the system.
o This network is characterized by relatively few clients, controlled access, and moderate traffic.
o It is usually on the Internet but might have some restrictions.

3
MES: Réseaux
▪ Plant Business Network
o is the main network for most non-direct production staff
o Some users will require access to the MES Report Serve
o In some circumstances, the Engineering Stations and Supervisor Stations will be on the Plant Business network
o is characterized as open, with many clients and varying traffic loads that might cause it to be slow at times.
o It is usually placed on the other side of the firewall from the Production network
o It might be part of the corporate WAN with or without a firewall

▪ Corporate Wide Area Network (WAN)

o Is distinguished by its physical location, which is usually off site but connected through a direct or dedicated line
o The ERP system (e.g., SAP) will reside on the Corporate WAN or Business network.
o The Database Server (for the ERP interface) requires access to it, usually through the firewall.
o The Corporate WAN is characterized by a slower connection. However, it is generally a stable and reliable connection

❑ Network Interconnections
Assuming your MES servers are all on the Plant Production network, the following servers will
require access to servers outside this network:
• Database Server: Plant Business Network or Corporate WAN for the ERP interface
• Application Server/OI Servers: Controls the network for the PLC data acquisition
• Database Server: Plant Business network or Corporate WAN for user reports access
Getting data outside your domain or on a different network might cause issues related to
crossing the firewall and users rights on both networks.
The basic idea is to have the server placed on the network where it is most used and have a
router that connects the network or network segments. This router would allow cross network
communications while isolating traffic and limiting access based on configuration. 4
 Make MES Middleware calls to MES database via a web service

require s user access to SQL server and the MES Database

Architecture de MES Installed manually (MES Web Access User Guide)

Wonderware 3.MES Web Access

Centralized Repository
used to import windows AD groups SID
Include OS group SID
installed on a separated server(recommended)
Database
4.Development Librairy (API DLLs) Enable communication between Client components and database
support executing archive, purge, restore jobs
start
5.MES Intelligence Reports Components middleware
stop middleware
Service Monitor restart middleware
used to configure almost all aspect of the MES system
used to
interact with the operational information Clear Parameters cache utility
configure (system utilization states, users, users License client api for accessing the license server
groups, privileges, languages....) MES Client
includes
Operations Capability object OCO installed on a separated server(recommended)
Utilization Capability Object UCO MiddleWare
Sample Recording Object SRO changing shifts
Application Objects cleaning up stale sessions
Data Editor Generating& changing the status of quality
sample
Operator runs middleware activities
.Net controls Service monitor
utility
Middleware Proxy includes
Entity Model Builder Should be only one running on a
Superviso system
r MES Service
is a web app that provides web base
2.Client Components access to MES
MES Web
Portal
6.PDF
1.Server components
Documentation

MES Components
5
Wonderware MES Architecture
MES Client Operator MES Client
InTouch w/
Supervisor .NET Supervisor Galaxy
Controls Repository
Reports Configurator
InTouch w/ Field I/O
MES API ArchestrA
IDE

Supervisory (P) Shop Floor (P) MES Admin

(P) AOS Platform (M)
Engineering Factory Operations
WS Connector Capability Obj
Server (M)
Utilization
Middleware Capability Obj
Server (M,S) Sample
Reports App Server Recording Obj
Database
Server (M or None) Server App Objects
w/ MES API

Key: M = Full Middleware P = Middleware Proxy S = MES Service

6
 Solution Installée
QAD

Operators
Engineering Workstation 6 Report Server
- Operator Client
DB Server
- MES Client - Intelligence Report
4 - Web Portal
- Historian Server - ArchestrA Developpement
- DB Server IDE - Galaxy Repository
- Licence Server

5 7 8

Application Server Application Server (Redondant)

1 1'
- OI Core - OI Core
2 - Middelware - Middleware 2'

3 3'

Licenses:
?
3' : MES-34-N-14R3:
1 : OIServ-51-N-17
Performance Load Bal

2 : MES-04-N-14R3:
4 : HstStd-54-N-17
Operations
3 : MES-24-N-14R3:
Performance
5 : AppSvr-04-N-17 8 : InSight Client SCADA

1' : OIServ-51-N-17 6 : SupClt-03-N-17

2' : MES-14-N-14R3: Système de code à barres

7 : Intell-11-N-14R3
Operations Load Bal

7
MES Component
❑ The Production Database Server
• Is usually the most critical server relating to performance in an MES System.
• Holds the MES database and is the central repository for the MES data.
• The MES database is supported on SQL Server.
• In large implementations, should be dedicated to MES due to high transaction volumes. There should be
no ERP databases, etc. on the same server.
• The Production Database Server typically runs the following databases:
⮚ MES database
⮚ Alarm database
⮚ Runtime database
Ideally, these databases should be run on their own server. However, in practice, if the Alarms and Historian databases are being
used only for MES, then they can be run on the Production Database Server.
• In a typical solution, it does not run the following:
⮚ Galaxy Repository
⮚ Intelligence Server database
⮚ Report Server databases

❑ Application (MES Middleware) Server

• Hosts the MES middleware used to communicate with and process all database transactions from the
clients
• When ArchestrA System Platform is used, the same server usually hosts both the MES middleware and
the ArchestrA System Platform Application Server. For these reasons, this server is being referred to as
the Application (MES Middleware) Server
8
MES Component (Application (MES Middleware) Server )
The MES Middleware
• Is a process that handles all client transactions to the database
• Manages background housekeeping
• Validates licensing
• Launches all scheduled jobs.
• The MES Middleware Proxy provides access to the MES middleware for clients
• The proxy is installed on each client station and on all MES middleware hosts
• The recommended number of MES middleware hosts for a medium-size system are:
o One for each Application Object Servers (AOS) server
o One for each Terminal Server
o One for Enterprise Integration: Enterprise Integration or Supply Chain Connector (SCC) (typically on the Database Server)
• Each MES middleware host acquires an MES Middleware count from the License Server
• MES processes will use the MES middleware defined by the MES middleware proxy where they
are running. This means all MES processes running on a computer will use the same proxy and thus are
all connected to the same MES middleware
Where to Run the MES Middleware Host
• The typical locations on which to run the MES middleware host are either the Application Server (with
ArchestrA System Platform) or standalone (no ArchestrA System Platform )
• It is recommended that the MES middleware host not be run on the Production Database Server
• In a production environment, it is recommended that the MES middleware host run on the Application
Server

9
 MES Component Services
▪ Is a program that is set up to run
continuously as a service, and does not
require you to log in to Windows
▪ Manages the background tasks in MES that
are not done by:
• An application object
• A program that you are running
• An MES control embedded in an InTouch
symbol
▪ The MES Service performs several functions,
such as the following:
• Generates samples and updates status for quality
specifications.
• Generates shifts for any set of entities.
• Maintains tables in the MES database.
▪ The MES Service is notified if you make the
following configuration changes within MES
Client:
• Altering sample plan frequencies
• Unlinking frequencies from sample plans
• Changing the sample plans that are linked to
Quality Management (QM) specifications or their
linked characteristics
▪ MES Service Scheduled Tasks
▪ Every Minute (Starting Within Half a Second)
• Updates the current shifts for each entity if the shift changes
• Checks for the beginning or end of Daylight Saving Time, and automatically
adjusts the Report time zone difference from GMT
• Runs the sp_BG_Minutely_Tasks stored
• Performs Supply Chain Connector imports and exports based on time
• ….
▪ Every Hour
• Runs the sp_BG_Hourly_Tasks stored procedure to ready the first jobs of a
work order if its release date and time has passed
• Asks the License Manager for the current licensing and updates the internal
licensing structures
▪ Every Day
•
Runs the sp_BG_Daily_Tasks stored procedure to project the entities' shift
schedules for the next few days.
• Runs the sp_BG_Daily_Tasks_Custom stored procedure if it exists.
• Deletes historical data records that are older than the value specified in the
Days to keep data 0=never delete general parameter.
• Cleans up the QM context data, which is older than the value specified in the
How long to keep old context information (in days) general parameter
▪ Interval Specified by the General Parameter
• Runs the sp_u_Sample_ReadySamples stored procedure to change the status
of QM samples
• Runs the sp_u_Sample_UpdateStatus stored procedure
• …...
10
MES Component
The MES Service
The MES Service is a service that:
⮚ Cleans up shifts and sessions
⮚ Runs the Supply Chain Connector (SCC) schedules
⮚ Executes minutely, hourly and daily tasks.
⮚ Generates future quality samples for time, shift, and production unit count frequencies.
⮚ Changes quality sample states based on passage of time

Report Server
⮚ provides the content to operators in the plant, office users, and corporate users.
⮚ Its source of information is from the Production Database Server.
⮚ Typically your Production Database Server is on the Plant Production Network while the office users
are on the Plant Business Network and it is not uncommon for a firewall to be between them.
⮚ The Report Server is not considered a production server. That is, it can go down without
interruptions to production and without losing production data.
⮚ Installations that run large reports or do data mining on the MES database should perform these
operations on an Archive database and not the actual Production database
⮚ Extracts data from MES database, transforms it, and populates the Intelligence database
⮚ Reports
 Production by Entity  Utilization by Entity
 Line Production  Utilization Analysis
 Genealogy by Work Order  OEE Analysis
 Utilization Timeline  Mean Time Between Failures (MTBF)
11
MES Component
MES Web Portal Server
The MES Web Portal Server hosts the web pages for both configuring and operating equipment line
performance monitoring. This server may reside in the corporate domain or plant domain depending on
its usage. This server should have a dedicated MES Middleware Server for managing all the client
transactions.
Used to:
• Monitor the status of a line’s work orders, jobs, and entities
• Change the status of a work order
• Reassign a work order to another line
• Start and stop jobs
• Add or reduce production for a job
• Manage entity events
• Mark jobs as complete
Galaxy Repository (GR) Node Server
⮚ The GR Node is the computer where the Galaxy Repository resides.
⮚ It is a SQL Server database in which all of the galaxy configuration data is stored
⮚ The GR should be available to the Galaxy.
⮚ It is recommended that the GR Node Server be on the Report Server or on the Engineering station.
⮚ It is recommended that the GR Node Server not be on any of the production servers
12
MES Component
Archive Server
It is recommended the Archive database reside on its own server.
The Archive database holds a copy of the production MES database.
Data is copied on a regular basis from the MES database to the Archive database on a time
and Work
Order basis. This data then can be used in reports or to restore most of the production data
if the production server is lost.
Terminal Server
Terminal Server has the following advantages:
It provides ease of setup and maintenance of applications. Instead of installing the MES
client on many systems, you install it once on the Terminal Server. The clients operate in a
controlled Windows environment. All the clients run under the same version of Windows
and same patch level. It can reduce hardware costs. It should reduce maintenance costs.
It provides the ability for redundancy.
Resources are shared, so if your clients need a significant number of resources, they are
available.
This typically applies to the CPU for which full capacity is not needed all the time. It is very
scalable. Although there is a limit to the number of clients per server based on the
application, you can add additional memory or CPUs to the server until you reach your
limit. Then additional Terminal Servers can be added to meet your needs
13
MES Deployment
Engineering Stations Supervisor Stations
An Engineering station is a system that is A Supervisor station is where work orders are
configured by someone with expert knowledge of scheduled and/or the activities of the operators are
the system. The activities range from: monitored. Supervisors are different from the office
users in that their PCs are close to the shop floor and
• Configuring the systems
have direct access to the MES Server.
• Performing maintenance and system shutdowns A Supervisor station is different from an Operator
• Adding users station in that in addition to the Operator application
(MES Operator or InTouch), the Supervisor station has
• Deploying Operator stations
access to the MES Client
• Debugging problems
• Changing configuration Applications Used
• Adding content • MES Client
• Setting import/export schedules • MES Operator (or custom Operator UI), if used
• Web browser to access MES Web Portal, if
Applications Used used
• MES Client • MES Supervisor
• ArchestrA IDE • InTouch Application, if used
• InTouch WindowMaker and WindowViewer • MES Intelligence Reports
• Intelligence Server Administrator features
• Web browser to access MES Web Portal, if
Operator Stations
used Are the PC or thin clients used to control, monitor, or
record information from the process.
The GR Node (the GR database) can be run on the Both client server (so-called fat clients) and thin client
Engineering station. This frees up resources on the architectures are fully supported, with one not
Report Server. recommended over the other.
14
MES Client
▪ Define users and groups
▪ Define shift schedules
▪ Define machine state and reason
▪ Assign passwords and group
privileges
▪ Define global system parameters
▪ Define custom attributes
▪ Configure global specifications
▪ Configure Entities
▪ Configure Language strings
▪ Configure Items and item classes
⮚Specify Item states and grades
⮚Specify UOM for an item or
characteristic
⮚Configure work orders and jobs
⮚Configure a process
⮚Manage jobs
⮚Maintain MES database
⮚Configure sample plan and
frequency
⮚Define characteristics
⮚Configure quality specification
15
MES Objects and .net Controls
▪ OCO, UCO, and SRO objects
and “Operator” .net
controls
⮚ OCO, UCO, and SRO objects
Allow for automation of
Utilization, Operation, and
Quality transactions From
Application Server to the MES
database
⮚ .net Controls allow for
customized InTouch windows
that communicate to the MES
middleware and database.
MES Operator
▪ Operator is the production
employees interface to the MES
system
• Routing display of running job
• Set Work order priorities
• Start and stop jobs
• Recording production and
consumptions items
• Set Utilization states of an entity
• Sign off and record operation
steps
• Record job specification
• Maintaining Inventory
• Tracking labor times
16
Standard Topology Overview

17
Standard Topology Overview
This system includes MES with System Platform. It uses the Standard Configuration.
The Application Server has the following connections:
• To the Controls Network, to communicate with the process equipment. This is typically done
via Operation Integration Servers (OIS). It is very common to have a separate OIS server.
• To the Plant Production Network, to access other MES servers.
The Database Server has the following connections:
• To the Corporate WAN, to provide access to the ERP system.
• To the Plant Production Network, to access other MES servers.
The Report Server and Web Portal Server also include multiple logical connections, as
office users need to connect to them and they need to connect to MES Servers.

18
 MES Wonderware Installation
Operator Client
Web Protal
Report Server
MES Middleware/DB 1mainteance
Server
MES Databse MES Role-Based Installation
MES Service
MES Middleware
MES Middleware
Proxy
DataBase server with MES Limited version of intelligence
MES Client
none of the MES roles will install intelligence
MES Supervisor
select customize option to manually select the intelligence component
MES Data Editor
MES Middleware 3.Intelligence
Proxy
Configuration Client
Application Objects (OCO, SRO, a combination of MES features specific to a node's role in multi nodes system
UCO)
MES .Net more than one role can be selected for install on a node
Controls
MES Entity Model
Builder
2.provides
MES DLLs
MES Middleware
select role based groups and components for install on a node
Proxy
ArchestrA
customize the install by selecting specific components
Development
4.Roles available 1.setup tools
allows

MES Role-Based Installation

19
 Vérification des Prérequis software pour
chaque composants à installé
• Microsoft .NET Framework 4.7.1 For All Roles
• Exemples:
• Database Server with MES role
• Microsoft Message Queue (MSMQ) Server
• Safenet Sentinel License Driver version 7.6.8 or higher
• Operator Client role
• Microsoft MSMQ Server
• Web Portal role
• Microsoft MSMQ Server
• Microsoft Internet Information Services (IIS) 7.5 or higher
• MES Middleware/DB Maintenance Server
• Microsoft MSMQ Server
• Safenet Sentinel License Driver version 7.6.8 or higher
• ArchestrA Development role
• Microsoft MSMQ Server
• Application Server version compatible with the current version of MES
20
 Installation 1
• you must have administrator privileges for the Windows Operating system on the node on which the
software is being installed
• Run install
• Select the roles whose products and components you want to install on the local node

21
 Installation 2
• To install the License Server and Manager components or the
Intelligence Server, Intelligence Model Builder, and Intelligence Data
Adapters components as part of the MES installation, you have to
choose the Customize Installation option and then manually select
these components
• Intelligence and the MES Intelligence Reports component must be
installed on the same node as SQL Server Reporting Services (SSRS).
Otherwise, the Quality Characteristic Detail report SPC
Chart will not work
• When the installation is finished, you are prompted to configure
products and components that require configuration before they can be
used
• Activating the MES Product Licenses
Before configuring the MES components in the post-install Configurator, the
MES product licenses must be activated so that the MES middleware and
MES Service can be started
22
 Activation des Licenses
• To activate the MES product licenses
• If the License Server has not already been configured, use the post-install Configurator tool to
configure it
• Use the License Manager to activate your MES product licenses
• Configuring the License Server Component

• Activating the Product Licenses

23
Configuring MES Components 1

24
Configuring MES Components

• Creating or Migrating MES Databases (65)

• Configuring MES Middleware Communication with MES
Databases (75)
• Configuring the MES Middleware Proxy (95)
• Configuring MES Web Portal (97)
• Configuring and Deploying MES Intelligence Reports (107)

25
Creating or Migrating MES Databases

The databases can be on the

The MES Database same or different SQL Server
User account and rights Setup component database servers to support
Is the first step in Sql Server database production, restore,
to create database must settings in the
configuring new MES should be available test, development, and other
be known Configurator allow you
to: types of databases

Dump the MES

Create the MES
database scripts to disk,
production database, Migrate an existing MES
so they can be
and optionally a restore database to the current
customized and used to
database, for a new MES version
create a custom MES
installation
database

26
Configuring MES Middleware Communication with MES Databases

• The DB/MW Communication component is used to create the database connection strings that the MES middleware service
uses to access MES databases

27
 Resides on a single network computer (on any computer)
you cannot store parts of a galaxy db on several computers
GR,Galaxy Repository is the name of the single
Computer where the galaxy DB is located

Galaxy Database
is the set of unique object and attribute identifiers
The namespaces and the values of its identifiers define Platforms
a Wonderware Application server application
Engins
can be accessed by clients of the configuration system
Templates
Application Server namespace allows app server objects
and process data to be referenced by scripts and Instances
animation links from any computer in the Galaxy Attributes

Galaxy Namespace is a collection of

Represents the entire Production environment
turned of by default computers
you can limit what users can do Components that run application
you can add more users Including
you can add more security roles and groups Persistent information is stored in a Galaxy database

Includes security What's a Galaxy

Galaxy
Historian
• Historian Server est le logiciel le plus utilisé au monde pour l’historisation et le traitement des
données industrielles et de production
• Incluant Microsoft SQL Server, Historian se singularise des autres systèmes d’historisation temps
réel en fournissant un accès universel aux données, un moteur relationnel puissant et une intégration
étroite avec Microsoft Office
• Caractéristiques
⮚ Collecte automatique et manuelle des données
⮚ Compression des données archivées
⮚ Aucune dégradation des temps de réponse en exploitation
⮚ Moteur d'événements intégré
⮚ Restitution des données suivant différents modes pour une meilleure performance
⮚ Sous-systèmes de calculs intégrés (moyennes, sommes, min, max...)
⮚ Haute disponibilité sans contrainte informatique
⮚ Outils d'analyse prêts à l'emploi (Courbes, tableau...)
⮚ Outils d'analyse pour Excel et Word
• Domaines d’Applications

Industrie * GTB/GTC * Infrastructures * SCADA * MES

29
 WondeWare Historian
• The Wonderware Historian is a high-performance real-time database for historical information. It combines the power and
flexibility of a relational database with the speed and compression of a true process historian, integrating the office with the
factory floor or any industrial operation

• Wonderware Historian is designed to collect a wide variety of plant data, at full resolution and very high data rates, ensuring
that decision-makers at all levels will have the historical information they need to drive vital productivity improvement
initiatives. Wonderware Historian offers unparalleled scalability and can be configured as a single data collection and
aggregation system, or as a part of a larger, tiered architecture offering the ability to implement sophisticated summary and
replication systems. Hundreds of times faster than standard database systems and with the ability to save data in a small
fraction of the space, Wonderware Historian also has built-in data retrieval modes which understand the questions you need
to ask of your process to enable detailed, focused information and reports to be rapidly obtained. With the added power and
versatility of Wonderware Historian Clients, accelerate your decision-making process and provide access to the right
information when a problem is identified, or an opportunity uncovered. Wonderware Historian is a core component of the
Wonderware System Platform

• Key Benefits
⮚ Designed for all industrial manufacturing and infrastructure operations
⮚ Generate actionable information for faster, more accurate decision-making
⮚ Unify information from multiple manufacturing and HMI/SCADA systems
⮚ Flexible architectures scalable for any sized application
⮚ Fully integrated with the award-winning Wonderware ArchestrA architecture and Wonderware System Platform30
Installing and Configuring WonderWare Historian
https://www.youtube.com/channel/UCL5FLDMS7WjqlqI0kvwgRVQ

1. Installing SQL Server for Wonderware Historian

31
Configuration Install patch

32
Configuration
• it’s a series of stored procedures and queries to create a database
inside of Ms Sql Server, the name of that database is going to be called
RunTime

33
 Install a License for W H Server

• Use ArchestrA License Manager • Configuring Data Acquisition Server for W H

• Configuring Data Acquisition Server for Wonderware Historian

34
35
System Platform Licensing
https://www.youtube.com/watch?v=x2YXQyVP8lc&t=235s
● system platform is a bundle of software that contains:
○ Wonderware Application Server
○ Wonderware Historian Example of
○ Wonderware Information Server bundle quote
○ Wonderware Device Integration ...
○ Since The Bundle contains individual software product, each product needs

it’s own licensing

the architecture for the system that goes along with the example quote

The application server license is always

installed on the galaxy repository
computer
36
Application Server Licensing
• In a Wonderware system platform application all the configuration is contained in the Wonderware application server
• metrics that is used to determine the Wonderware Application Server licensing
● IO : is the number of variables that we are reading from an external device
● Number of computers :that are participating in the application these computers represent what is called platforms in the Wonderware Application
Server licensing.
• Application server platform is really concerned with computers and will be hosting data while providing server type functionality :
○ Might be hosting Objects this type of platform is called is called AOS “ Automaton Object Server ”
○ Might be hosting the system configuration this type of platform is called a galaxy repository or GE
○ Might be hosting historical data this type of platform is called a historian
○ Might be hosting multiple HMI sessions this type of platform is called a terminal server or remote desktop server

❏ the base application server only comes with 4 platforms so for our system to be licensed correctly we need to add two
❏ The application server license once you have provided the i/o count and platform count to Wonderware you'll receive the
license
❏ The application server license is always installed on the galaxy repository computer
❏ The application server license does not have to be installed on any other computer

37
Device Integration Licensing
➢ Also called data access servers or DAServers, they allow the Wonderware software to communicate to the PLC's and devices
➢ You can have multiple DAServers in your application if you're communicating to different vendors PLC's or devices
using different communications protocols
➢ You may also have two DAServers of the same type in the application to provide redundancy or failover capability
➢ Each computer where the DAServer is installed must have a device integration license, however one device integration license can enable
multiple DAServers on one computer so in your application you install the DAServer as part of the computer
➢ The device integration license can run on the AOS nodes
➢ Customers can choose to put the DAServer on a computer by itself
The AOS computer runs objects
➢ If you have a need for redundancy you will get a second device integration license
that represent pieces of
equipment or functions to be
performed

Historian Licensing
➢ On the wonderware application server you can enable any variable to be historize to the Wonderware historian
➢ the Wonderware historian configuration for the variable and the variable data is pushed from the wonderware application server to the
historian
➢ the Wonderware historian is licensed based on the variables configured in the historian when it recalls these variables tags
➢ when you enable a variable in the wonderware application server to historize it's data this adds one tag to the Wonderware historian
license count
➢ The wonderware historians stores data so that other computers can come in and access it
➢ The Wonderware historian client software product is one way to gain access to the data in the Wonderware historian
➢ Access to the data in the Wonderware historian is licensed by the people and devices that connect to access the data
➢ the license for the Wonderware historian goes on the actual computer that is running the software

38
Informaton Server Licensing
➢ The wonderware application server and historian have data in them that may be of interest to managers supervisors schedulers or
raw material vendors you would use the wonderware information server to make that data available through the web portal
➢ You may also have data in other systems or databases that you would like to make available through the web as well
➢ The Wonderware information server is licensed as a server, the license enables the website to be active and running
➢ Just like the Wonderware historian users and devices will consume information from the Wonderware information server web
portal
➢ The number of clients is licensed as part of the Wonderware information server client licenses
➢ when you purchase Wonderware system platform you are given a license for the Wonderware information server web portal
however the system platform license does not come with any Wonderware information server client licenses
➢ this license is always installed on the computer running the Wonderware information server

39
other software packages HMI inTouch
➢ this is the software that displays the graphics and screens to the users to allow them to interact with the system
➢ the Wonderware application server gets its data from the PLC's and devices in the plant, the computer running the HMI connects
to the Wonderware application server and displays the data
➢ the HMI can be configured to allow the user to provide supervisory control to the application by writing values back from the HMI
to the PLC's or devices
➢ the Wonderware inTouch for system platform software is licensed for every user that will run the HMI application
➢ As an application gets larger and larger you can add additional HMI computers to the system
➢ if you have people that are familiar with terminal services or remote desktop services you can add a Terminal Server computer to
the application this allows thin clients to connect to the terminal server and run the HMI application
➢ for redundancy and failover capability you can also add an additional Terminal

40
Wonderware Development Studio
➢ is usually purchased with the Wonderware system platform license
➢ is used to configure the application server, historian information server and the inTouch for system platform software
➢ all of the configurations are stored in the galaxy repository computer
➢ the wonderware development studio is recommended to be installed on a separate computer and it will access the
application server configuration on the galaxy repository over the network

41