ApplicationServer 2014R2 RevA Presentation1

Application Server 2014
Application Server
2014 R2
2014 Invensys Systems, Inc. All Rights Reserved.

The names, logos, and taglines identifying the products and services herein are owned by Invensys Systems Inc. or its subsidiaries.
All other trademarks are property of their respective owners.
Module 1
Introduction
System Platform
Project Specific Work
Function Modules
System Platform
System Platform
Clients
Microsoft Technologies
+
Industry Standards
Schneider Electric Software Proprietary and confidential. 11/13/2015
System Platform Components

System Platform Clients
Historian
Client
InTouch
Information
Server
CAL
System Platform
Application
Server
Historian
Server
3rd Party
Data Sources
Information
Server
Software
Applications
Device
Integration
Servers
3rd Party
Controllers
Concepts and Terminology

Application Server
It provides a unified environment for visualization, plant history, device
communications and automation application integration.
Bootstrap
The base ArchestrA service which provides the base software required to
receive a platform.
ArchestrA IDE (Integrated Development Environment)

Application Servers development environment for configuring and deploying
the application (Galaxy).
Galaxy
Application Servers application, configuration information and project
database.
Galaxy Repository
Single computer and software that hosts and manage the Galaxy.
Application Server Highlights

Leverage the .NET Framework for the Automation World
Object-based application
One global networked namespace

Centralized configuration and security
Multi-user development environment
Component-based plant application model
Intake
Production
Line 1
Line 2
Discharge
Self documenting
Advanced system maintenance and diagnostics
System Platform Topology

Visualization Nodes
Device Integration
Servers
Engineering Stations
Automation Object
Servers
Controllers
Workstations
Galaxy
Repository
Historian
Server
License
Server
Information
Server

Visualization Nodes
IDE
Hist. Client
Hist. Client
Hist. Client
InTouch
InTouch
InTouch
InTouch
WinPlatform
WinPlatform
WinPlatform
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
IO Server
DA Server
WinPlatform*
WinPlatform
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Galaxy
Repository
Historian
Server
Information
Server
WinPlatform
WinPlatform
WinPlatform*
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
Galaxy
Repository
Historian
Server
Automation Object
Servers
Controllers
* Optional
IDE
Hist. Client
Device Integration
Servers
Workstations
License
Server
Information
Server

Visualization Nodes
IDE
Hist. Client
Hist. Client
Hist. Client
InTouch
InTouch
InTouch
InTouch
WinPlatform
WinPlatform
WinPlatform
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
IO Server
DA Server
WinPlatform*
WinPlatform
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Galaxy
Repository
Historian
Server
Information
Server
WinPlatform
WinPlatform
WinPlatform*
WinPlatform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
Galaxy
Repository
Historian
Server
Automation Object
Servers
Controllers
* Optional
10
IDE
Hist. Client
Device Integration
Servers
Workstations
License
Server
Information
Server
5 min
Lab 1: Creating a Galaxy
11
Automation Objects
Inputs/Outputs
Graphic symbols
Logic/Scripting
Documentation
Historical Information
Alarms and events
Security
12
Automation Objects
Templates and Instances
Instances derived from templates and inherit all the configuration
New templates can be derived from existing templates
Changes to templates can be propagated to derived objects
Templates allow the development of a library of standard objects
CV101
$Valve
CV102
CV103
13
Templates
14
Base Template
Derived Template
Core objects created with the

ArchestrA Object Toolkit
Templates created from another

template within the ArchestrA
IDE
Contain the base attributes and

functionality of the object
Inherits the attributes,

functionality and configuration
from the parent template
Read-Only configuration
Writeable configuration
Template Derivation
Templates
$Inlet
$UserDefined
$Valve
$Outlet
15
10 min
Lab 2: Creating Global Derived

Templates
16
System Requirements - Software

Development
(ArchestrA IDE)
Automation
Object Server
Galaxy
Repository
Windows Server
Windows Workstation
SQL Server
.NET Framework
Y
Y
**Refer to the readme file of the latest Service Pack or Patch for software editions and version numbers
17
System Requirements - Hardware
Compact
(1 500 I/O)
Small
(500 5K I/O)
Medium
(5K 50K I/O)
Large
(50K 400K I/O)
2.8 GHz
2.8 GHz
2.8 GHz
2.8 GHz
Cores
RAM
1 GB
1 GB
8 GB
16 GB
30 GB available
30 GB available
500 GB available
1000 GB available
Display
1024 x 768
1024 x 768
1280 x 1024
1280 x 1024
Network
100 Mbps
100 Mbps
1000 Mbps
1000 Mbps
CPU
Hard Drive
18

Galaxy
This refers to the total application model that resides in the Galaxy Repository.
IO Count
Number of I/O points being access into the Galaxy.
WinPlatform Count
Number of PCs in the Galaxy that will be part of the single namespace.
ArchestrA IDE
Integrated Development Environment for configuring the Galaxy.
19
Licensing
Product
Application Server
InTouch
Historian Server
Historian Client
Information Server
20
ArchestrA.lic
ArchestrAServer.lic
Y
Y
Virtualization
Support
Hyper-V
VMWare
VLANs for all node-tonode communications
Remote Apps
21
Overall Benefits
Lower hardware costs
Greater performance
Greater scalability
Higher availability
Greater reliability
Disaster discovery
Module 2
Application Planning
Automation Objects
Inputs/Outputs
Graphic symbols
Logic/Scripting
Documentation
Historical Information
Alarms and events
Security
23
Suggested Project Workflow

Identify Field Devices and Functional Requirements
Define the Naming Conventions
Define the Plant Model
Plan Templates
Define the Security Model
Define the Deployment Model
24
The Factory Layout
PRODUCTION
LINE 2
LINE 1
RECEIVING
25
PACKAGING
SHIPPING
Module 3
Application Infrastructure
The Plant Model

Plant
Section
Area
Section
Production Line
Section
Area
Production Line
Manufacturing Cell
27
Area
Production Line
Manufacturing
Cell
Manu
Area
AppEngine
WinPlatform
Bootstrap
28
DI Object
Area
DI Object
The Deployment Model
AppEngine
WinPlatform
Bootstrap
29
Area
AppEngine
DI Object
Area
DI Object
Area
DI Object
Area
DI Object
The Deployment Model
Template Derivation
Instance
Templates
CV101
$Inlet
CV102
$UserDefined
$Valve
CV103
$Outlet
CV104
30
20 min
Lab 3: Creating the Plant and

Deployment Models
31
Object viewer
Deployed
Application
32
15 min
Lab 4: Using Object Viewer
33
Automation Object communication to PLCs

Application Object
MX
Driver
Device Integration
Object
<topic>.
<device group>.
<scan group>.
<object>.
Generic DI Objects
Data point, register or

address on PLC
<item>
PLC1
IO Server
Application Object
PLC2
$DDESuiteLinkClient
DAServer
PLC3
OPC Server
PLC4
DAServer
PLC5
$OPCClient
Device Specific
DI Objects
DIObject
OPC
Single Node
34
Device Integration Products

IO Server and DA Servers
ArchestrA
Runtime
Communications between the Galaxy and field devices is achieved

through Device Integration Products
Supported protocols include DDE, SuiteLink and OPC
New internal architecture for DA Servers provides independency
between components
DDE
I/O Data Server
35
SuiteLink
DDE
SuiteLink
SuiteLink
OPC
IO Server
DAS
DA Server
Engine
PLC Protocol
PLC
PLC Protocol
Protocol
DA Servers and DI Objects

NIC
I/O Data Server
PLC_1
PLC_2
DHP
SLC_A
SLC_B
CNET
PLC5_A
PLC5_B
36
10 min
Lab 5: Configuring the DA Server
Device
Driver
Field Device
PLC Simulator
37
Connecting to the Field
Device
Driver
38
Field Device
Communication Protocols
VTQ*
Client
Server
DDE or SuiteLink
Node
Name of the computer where the server application is running.
Application
Name of the server application executable.
Topic
Name of the topic in the server application from which to receive data.
Node
Name of the computer where the OPC Server is running.
Server
Name of the OPC Server.
Scan Group
Name of the scan group in the OPC Server from which to receive data.
OPC
39
I/O Addressing
<DIObjectName>. <DeviceGroupName>. <ItemName>
40
Advanced Communication Management

Active On Demand
Attributes that are not actively being referenced by any client or object are not
scanned.
Active
Attributes are always in the active scanning state.
When the last reference to an attribute is unregistered (unadvised), the attribute
is deleted.
Active All
Attributes are always in the active scanning state.
When the last reference to the attribute is unregistered (unadvised), the
attribute is not deleted.
41
Lab 6: Configuring the Device

Integration Object
Galaxy
Device
Driver
Field Device
PLC Simulator
42
10 min
Module 4
Application Objects
$UserDefined Object
AnalogFA
AnalogFA.RawMin
AnalogFA.RawMax
Scaling
AnalogFA.EngUnitsMin
AnalogFA.Input.InputSource
AnalogFA.Input.Value
AnalogFA.EngUnitsMax
DiscreteFA.Input.InputSource
DiscreteFA.Input.Value
Boolean
44
Invert
DiscreteFA
Analog
Writeablility Categories
Same
Object
Calculated
Calculated Retentive
Object Writeable
User Writeable
45
Other
Objects
External
Users
25 min
Lab 7: Modeling the Heat Exchanger
46
Control and Propagation of Changes

Locking an attribute prevents changes
to that attribute on derived templates
and instances.
Locking an attribute locks that
attribute all the way down on the
derivation hierarchy.
Locking attributes helps to establish
standards in the Galaxy.
Unlocking an attribute releases the
locking control only one level down.
47
Control of Changes and Propagation of

Changes
CV101
$Inlet
CV102
$UserDefined
$Valve
CV103
$Outlet
CV104
Unlocked
Locked
Locked In Parent
48
15 min
Lab 8: Configuring Change Control and

Propagation
49
Containment
Allows more advanced structures to be modeled as a single object
All objects are still accessible as individual objects
Relationship can be build at the template or instance level
Tank
Agitator
Level Meter
Inlet Valve
50
Outlet Valve
Object Naming
Tagname :
Valve_001
Contained name:
Tank_001.InletValve
Hierarchical name:
Reactor_001.MixerTank.InletValve
Reactor_001.Tank_001.Valve_001
Reactor_001.Tank_001.InletValve
Tank_001.Valve_001
51
35 min
Lab 9: Creating the Mixer

AGITATOR
$Valve
$Motor
LT
INLET 1
PUMP 1
TT
OUTLET
INLET 2
PUMP 2
$Mixer
52
Module 5
Alarms and History
Alarm Subsystem
$Object2
$Object1
$Object3
Report their own alarms and events
$Area
$WinPlatform
$AppEngine
DISTRIBUTED ALARM MANAGER

CLIENTS
Alarm Subscribers
54
$DIObject
Alarms
Alarms are generate by the objects
Alarm providers make the alarms available
to external alarm subscribers
Available alarm subscribers allows:
Visualization and acknowledge of
alarms
Print alarms
55
Alarm Provider
$WinPlatform object as the Client Alarm Provider for the galaxy.
A single $WinPlatform can provide alarms from the whole galaxy.
Alarm providers can be limited to provide alarms for specific areas of
the galaxy.
Alarm Viewer
Area
WinPlatform
PROV
AppEngine
Alarm Printer
56
20 min
Lab 10: Configuring Alarms
57
Alarm Modes
Objects
Area
Container
Mode Settings
Area
Container
Contained
Enable
Changeable
Changeable
Disable
Disable
Disable
Area
Container
Contained
Enable
Enable
Changeable
Enable
Disable
Disable
Area
Container
Contained
Enable
Enable
Changeable
Enable
Enable
Changeable
Contained
AlarmModeCmd options:
Enable
Disable
Silence
58
Plant State Alarm

InProduction
Maintenance
Startup
Shutdown
Testing
59
Alarm Severities
Menu Location: Galaxy\Configure\Alarms and Events Configuration

Configure Alarm, Events, and Plant State
60
Schneider Electric
Software Proprietary and confidential. 11/13/2015
Alarm Count By Severities

AlarmCntBySeverities 0,0,0,0
Critical, High, Med, Low
Single Attribute within a object

All Attributes within a object
Containers include all Attributes
within objects within the container
Areas include all Attributes within
objects within the area
61
Schneider Electric
Software Proprietary and confidential. 11/13/2015
Alarm Shelved Attributes

AlarmShelved
AlarmShelvedCmd
AlarmShelveNode
AlarmShelveReason
AlarmShelveStartTime
AlarmShelveEndTime
AlarmShelveUser
62
Historization
Historian
Historian Server
63
Historization
$AppEngine object as the Historian client for the objects

An $AppEngine historizes only the objects that it host
$AppEngine also logs alarms through the Historian
Native support for Store & Forward
AppEngine
CLIENT
Area
WinPlatform
Historian
64
20 min
Lab 11: Configuring History
65
Module 6
Galaxy Maintenance
Importing and Exporting
Galaxy1
67
XXX.aaPKG
Galaxy2
20 min
Lab 12: Exporting and Importing Objects
68
Galaxy Dump
69
15 min
Lab 13: Configuring Instances Through a

.CSV File
70
Module 7
Security
Security
Development
Security
GENERAL
PERMISSIONS
Develoment
Testing
Troubleshooting
Environment
Runtime Security
Security Groups
Security
Classifications
72
ASSIGNED TO
ATTRIBUTES
OPERATIONAL
PERMISSIONS
Roles
BELONGS TO
ONE OR MORE
Users
Security Audit trail

The Galaxy generates an event for every user-generated write to an
attribute.
Events will be logged into Historian Server.
Use the v_EventHistory view in the alarm database to query events.
73
60 min
Lab 14: Configuring Security
74
Enhanced Electronic Signature

Handling: Done By/Checked By
Reason All Signed Writes present a reason for the action being signed to
the user from:
Field Attribute Description
Object Description
Custom String SignedWrite script function
Comment All signed writes allow for a user entered comment.
Reason and Comment stored in the electronic record in the Alarm/Event
database.
75
60 min
Lab 15: Using Security
76
Module 8
Redundancy
Application Redundancy
Non-Redundant System
The server handles all the data.
If server if lost, client lose
connection to all data:
InTouch
Historian
Other Application Object
Servers
Redundant System
Redundant server maintain

synchronized data through
dedicated network.
If the primary server is lost, the
backup server will take over.
The switch between the servers is
transparent to the clients.
78
ArchestrA
Runtime
Application Redundancy
Currently supported only in pairs
Second network connection (RMC)
ArchestrA
necessary
Configuration Terminology:
RMC
Primary AppEngine
Backup AppEngine
Runtime Terminology
Active AppEngine
Standby AppEngine
Active AppEngine refer to Standby

AppEngine as Partner.
79
AppEngine1
AppEngine1
(Backup)
WinPlatform1
WinPlatform2
Primary
Backup
Standby
Active
Standby
Active
Redundant Message Channel

Automatic Synchronization
Current data (Checkpoint)
ArchestrA
Alarm states and times

History store and forward blocks
RMC
Deployed objects and configuration

AppEngine status
Active
80
Standby
Supported Configuration
Peer to peer architecture
Each WinPlatform host a different
ArchestrA
AppEngine and Application Objects

No need for dedicated backup nodes
WinPlatforms can host more than one

AppEngine:
Backup for AppEngine1 is assigned to Node 2
Backup for AppEngine2 is assigned to Node 1
81
AppEngine1
RMC
AppEngine2
AppEngine2
(Backup)
AppEngine1
(Backup)
WinPlatform1
WinPlatform2
Redundancy Configuration
Windows Networking
1. Install 2nd network card.
2. Configure the ArchestrA connection to be accessed before the RMC connection.
3. Give the RMC connection a fixed IP address in a different Subnet than the ArchestrA
connection.
Application Server
1. Configure the WinPlatforms with their corresponding local RMC IP addresses.
2. Configure the AppEngine to be redundant.
3. Assign the AppEngines (Primary and Backup) to the WinPlatforms.
82
Lab 16: Configuring Application

Redundancy
83
50 min
DI Redundacy
Loss of the control network would cause
ArchestrA
Runtime
the server to lose connection to data.

The Redundant DI Object allows
communications through a Standby
network if the Active is lost.
The Redundant DI Object allows
Applications Objects to subscribe to a
single object that in turn can retrieve data
from either a Primary or Backup DI object.
84
CIP
DH+
DI Redundancy
Application
Objects
RDIO
DIO_1
AppEngine1
DAServer (A)
WinPlatform1
CIP
Control Networks
DH+
85
DIO_2
DAServer (B)
20 min
Lab 17: Configuring the Redundant DI

Object
86
Module 9
Introduce to QuickScript.NET
Execution types
Shutdown
Start up
OffScan
OnScan
Execute
88
Reconnect to DDESuiteLinkClient
89
15 min
Lab 18: Adding Auto Reconnect to

DDESuiteLinkClient
90
Switch back script for Redundancy
91
Primary
Backup
Active
Standby
StandBy
Active
10 min
Lab 19: Switching back to the Primary

Redundant Node
92
I/O References
XX =
student number
PLCSim.Tagname.M1XX_XX_XX
DataSource
93
String
Relative References
Me
MyContainer
MyArea
MyEngine
MyPlatform
94
Control Structures
IF THEN ELSEIF ELSE ENDIF
FOR TO STEP NEXT
FOR EACH IN NEXT
WHILE ENDWHILE
95
2014 Invensys Systems, Inc. All rights reserved.

The names, logos, and taglines identifying the products and services of Schneider Electric are proprietary marks of Schneider Electric
or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners.

ApplicationServer 2014R2 RevA Presentation1

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

ApplicationServer 2014R2 RevA Presentation1

Uploaded by

Copyright:

Available Formats

Application Server 2014

2014 Invensys Systems, Inc. All Rights Reserved.

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Platform Components

Schneider Electric Software Proprietary and confidential. 11/13/2015

Concepts and Terminology

Schneider Electric Software Proprietary and confidential. 11/13/2015

Concepts and Terminology

ArchestrA IDE (Integrated Development Environment)

Schneider Electric Software Proprietary and confidential. 11/13/2015

Application Server Highlights

One global networked namespace

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Platform Topology

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Platform Topology

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Platform Topology

Schneider Electric Software Proprietary and confidential. 11/13/2015

Lab 1: Creating a Galaxy

Schneider Electric Software Proprietary and confidential. 11/13/2015

Alarms and events

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

Core objects created with the

Templates created from another

Contain the base attributes and

Inherits the attributes,

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

Lab 2: Creating Global Derived

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Requirements - Software

Schneider Electric Software Proprietary and confidential. 11/13/2015

System Requirements - Hardware

Schneider Electric Software Proprietary and confidential. 11/13/2015

Concepts and Terminology

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

Alarms and events

Schneider Electric Software Proprietary and confidential. 11/13/2015

Suggested Project Workflow

Define the Naming Conventions

Define the Plant Model

Define the Security Model

Define the Deployment Model

Schneider Electric Software Proprietary and confidential. 11/13/2015

The Factory Layout

Schneider Electric Software Proprietary and confidential. 11/13/2015

The Plant Model

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

The Deployment Model

Schneider Electric Software Proprietary and confidential. 11/13/2015

The Deployment Model

Schneider Electric Software Proprietary and confidential. 11/13/2015

Lab 3: Creating the Plant and

Schneider Electric Software Proprietary and confidential. 11/13/2015

Schneider Electric Software Proprietary and confidential. 11/13/2015

Lab 4: Using Object Viewer

Schneider Electric Software Proprietary and confidential. 11/13/2015

Automation Object communication to PLCs

Data point, register or