TAC Vista

4.5 and 5.0

Key Features
Presentation and Demonstration
 Objectives

After the presentation and demo via

webinar, attendees will be able to
recognize key features that are new
with the release of TAC Vista 4.5 and
TAC Vista 5.0. They will also be able to
answer questions regarding these
features.

2
Whats New in
TAC Vista 4.50
Past vs. Present
 THE PAST: LTA ONLY

The TAC Xenta 511 and Xenta 527 could

function as an LTA for TAC Vista
Networks
Data points, alarms, trend logs, and
time scheduling information from these
devices could not be seen in TAC Vista
without creating connection objects
between the X511/527 and a TAC Xenta
280/300/401
The TAC Xenta 913 could not function
as an LTA
Signal values from Modbus, BACnet,
etc. in the X913 had to be connected to
a TAC Xenta 280/300/401 in order for
the data to be visible in TAC Vista

4
 NOW: TAC Xenta Servers

A TAC Xenta Server is any TAC

Xenta 511/527/913
Functions as:
LonTalk Adaptor (LTA) to TAC
Vista
Proxy
Different communication
protocols can be connected
to the Xenta Server and
presented in TAC Vista
Gateway
Signals can be communicated
between connected networks
The term Xenta Server is visible
in the TAC Vista database

5
 NOW: TAC Xenta Server

With the release of TAC Vista 4.50, TAC

Xenta 511, TAC Xenta 527, and TAC
Xenta 913 data points, trend logs,
alarms and time schedules (where
applicable) can now be viewed,
changed, and managed via TAC Vista
Workstation, Webstation, and/or
ScreenMate front-ends
Additionally, Online/Offline supervision
for Xenta Server devices is possible

6
 NOW: TAC Xenta Server

With the integration of these devices

into the TAC Vista database, the
following goals are accomplished:
TAC Xenta 527
Access control integration (I/NET)
TAC Xenta 511
Central management of distributed sites
TAC Xenta 913
Data from other systems (Modbus, BACnet,
etc) can easily be presented and managed
via TAC Vista

7
 THE PAST: XBuilder Not Accessible in
TAC Vista Workstation

XBuilder
Prior to Vista 4.50, XBuilder Project
was a stand-alone application
The XBuilder project and the
TAC Vista database were
completely separate
Controllers resided under the
TAC Vista Server object in
TAC Vista Database and
under the Xenta
527/511/913 in TAC XBuilder
project
All network configuration was
done by browsing to
appropriate databases
I/NET .sav file conversion and Vista
import was a two step Database
process
8
 NOW: Integration of XBuilder and
TAC Vista Workstation
XBuilder, the configuration tool for setting up
Xenta Servers, can be opened from within the
Workstation front-end
The XBuilder project files now reside in the
TAC Vista Server (i.e. TAC Vista database)
New Vista Database
menu in XBuilder
Possible to select
Save As, too

Network configuration is automatically

imported from TAC Vista to XBuilder
Folder shortcuts also enable the engineer to reuse
the logical structure created in XBuilder
9
 NOW: Integration of XBuilder and
TAC Vista Workstation

It is now possible for network

controllers to reside under the
designated Xenta Server object in both
TAC Vista and XBuilder
This is more user friendly because the
organization of the hardware is
standardized between the Vista database
and the XBuilder project
The old view where the controllers resided
under the TAC Vista Server object can be
restored if desired

10
 NOW: Integration of XBuilder and
TAC Vista Workstation

Importing an I/NET .sav file and

converting the file to .xml is now done
automatically
Reduced engineering time
Exposed SevenTrend signals
Alarm Configuration URL

11
 THE PAST: System
Architecture (pre 4.5.0)

Vista I/NET

XBuilder

LON

Domino
(511/527/913)

*Note: The Xenta 511 can not be used for I/NET integration.

12
 NOW: System Architecture
(4.5.0)

Vista I/NET

XBuilder

Domino
(511*/527/913)

*Note: The Xenta 511 can not be used for I/NET integration.

13
 THE PAST: No I/NET Integration
with TAC Vista

Prior to Vista 4.50, it was only possible

to use the TAC Xenta 527/913 as
gateways or I/NET OPC for
communication between I/NET and TAC
Vista
The TAC Xenta 527 was the only front-
end available that could easily provide
access to both TAC Vista and I/NET
data simultaneously

14
 NOW: I/NET Integration with
TAC Vista Server/Workstation

With the integration of the X527 and display of

all device information within its project, I/NET
security and HVAC systems can be managed
from TAC Vista Workstation
Includes Seven Trend data
Includes managing I/NET time schedules and alarms

I/NET Alarm views are

available in TAC Vista
Workstation by default
Additional database
column for displaying
key labels is now available

15
 NOW: I/NET Integration with
TAC Vista Server/Workstation

When making engineering

modifications to the I/NET system is
required (adding points, time
schedules, etc), the I/NET Host Tool is
simply launched from the Tools menu
in TAC Vista Workstation
Licensing determines which point
extension editors are available from the
I/NET Host Tool with regards to Security
and HVAC
Launching I/NET Host Tool starts I/O
Server on the PC

16
 THE PAST: Save Settings Only

Prior to Vista 4.50, it was only possible to select Save

Settings to determine the view in TAC Vista
Workstation upon login
This had to be completed at each individual
Workstation PC per user if the same settings were to
be viewed from different Workstation PCs
Settings are stored in the Windows registry for that user
Restricting user access was available on objects within
the Vista database and panes could be hidden from
those users using customized menus
Panes include List Pane, Folder Pane, Alarm Views,
Status Watch Pane, Event Views, etc.
It was not possible to limit user access to certain
options within the Vista panes

17
 NOW: Roaming User Profiles

User profiles that

designate which views
are visible to particular
users can be defined
Alarm View
Event View
Initial Graphic
Column Objects
A user profile can be
assigned to a user or a
group
Once the user profile is
defined, it now
automatically applies to
any workstation that the
user accesses
18
 THE PAST: Object Names

Prior to Vista 4.50, it was necessary to

use underscores (or other characters)
in object names that were more than
one word
The length of the object ID was limited
to 20 characters

19
 NOW: Possible to Use Spaces in
Object Names

It is now possible to use spaces in

object names with the exception of
variable names established in TAC
Menta
The length of the object ID is extended
from 20 to 40 characters

20
 THE PAST: Vista Alarm Features

It was only possible to clear the alarm pane

of all alarms (without having to acknowledge
them) by modifying a particular Vista Server
file in the Windows Explorer project directory
Disabled alarms were colored differently, but
still presented in the active alarm view
Alarm objects for LonWorks ASCs had to be
created manually
I/NET Alarms were not visible in the Vista
front-end directly from the I/NET .sav file

21
 NOW: Additional Alarm Handling
Features

Purging alarms is now possible

Disabled (Blocked) alarms are only visible in
the Disabled alarms view
Automatic alarm refresh after enable
(unblock) and purge
Xenta device alarm objects are created
automatically for ASCs under Xenta Server
I/NET alarm objects are created automatically
as they are triggered

22
 THE PAST: Time Synchronization

Because the controllers resided under

the TAC Vista Server object, the time
in the Xenta devices was typically
synchronized by the Server PC
(typically)

23
 NOW: Time Synchronization

Vista does not synchronize the Xenta

devices under a Xenta Server. They are
synchronized by the Xenta Server
Synchronizing Vista and a Xenta Server
can be achieved using:
External time server
Vista PC uses Xenta Server as time server

Vista generates an alarm if time is not

synchronized (default tolerance is 5
sec)
24
Overview of the New
I/NET Host Tool
 Changes in I/NET

When using TAC Vista 4.50 and presenting

I/NET information in the Vista front-ends, it is
not required that a full installation of I/NET
Seven is installed on the TAC Vista Server PC
The INET Host Tool is installed as part of the TAC
Vista installation process
I/NET Host Tool doesnt provide all I/NET
functionality because the capabilities are
available now in TAC Vista in conjunction with
the Xenta 527
Reduced menu set
No graphics
No AMT

26
 Changes in I/NET

Licensing for I/NET Host Tool can be

based upon customer need
Vista Security license file
Vista HVAC license file

Context sensitive launching of I/NET

Host Tool menus is based upon
purchased licenses
Windows user login is available when
started from Vista

27
 TAC Xenta
511/527/913 System
Version 2.40
Additional Features
 Changes in Domino Platform

Possible to purge alarms similar to I/NET

Can show multiple states on a signal
Trend logs from X300/X400 devices can be
viewed
Vista supports
Low web security (no certificates) selectable in
XBuilder
Low bandwidth for Xenta 911 and 913

Xenta 913 act as LTA for LonWorks

29
Whats New in
TAC Vista 5.0
Past vs. Present
 THE PAST: Graphics Editor (.ogc)

The Graphics Editor software was archaic and

not extremely user friendly
Advanced graphics designers were unable to
customize graphics as desired
Animation was not smooth
Associating point data to a graphic was
tedious
Symbol library was simple and static
Adding new symbols to the library was
difficult with regards to sizing and file
maintenance

31
 NOW: Graphics Editor (.tgml)

Customization is basically limitless

Designed for graphic designers with different
levels of ability
The new graphics editor is friendly for basic to
advanced level users
Graphics code (html) available for modification
Preview mode enables offline simulation with
capability of previewing based upon signal value
Animation is extremely smooth
Animated .gif/.bmp files not supported in 1st
release, but are to be available in future version
Point data bindings within the graphic (not
SNVT bindings) are associated in TAC Vista
Workstation front-end via drag and drop

32
 NOW: Graphics Editor (.tgml)

Components and Snippets library is comprehensive

and animation is pre-assigned to various graphic
components (fans rotate, colors change, etc.)
Creating new components and snippets is
extremely easy
Drag and drop image to Components/Snippets windows
within the editor
All Components and Snippets are stored in
C:\Documents and Settings\All Users\Application
Data\TAC Graphics Editor\Components
Sharing new components and snippets is
extremely easy
Drag and drop image into MSN Messenger and send
Drag and drop image to desk top to create a
.tgmlcomponent or .tgmlsnippet automatically
33
 NOW: Graphics Editor

TAC Vista 5 will support both .ogc (old) and

.tgml (new) graphic files
The old Graphics Editor is included in the full Vista
installation
It is possible to create new .ogc graphic objects if
desired
No need to upgrade existing .ogc files with which
the customer is satisfied
Upgrading .ogc files to .tgml files is easy
Simply opening the .ogc in the new Graphics Editor
will convert the .ogc to a .tgml
Some tweaking may be needed

34
 NOW: Graphics Editor Window

Objects Pane

Drawing Surface
Components Properties Pane
and Snippets
Pane
Bindings Pane

35
 TAC Graphics Exchange

New website for sharing

components/snippets, chatting about
graphics, and accessing how to
videos
TAC Graphics Exchange

36
FLEXNET Licensing
by Macrovision
 THE PAST: Aladdin Privilege
Administrator

Dongle and license file were required

for all users except the Engineering
dongle
Installation of the software and/or
license file was cumbersome

38
 NOW: FLEXNET Software licensing

Installation is EASY!!
Occurs as part of full TAC Vista Server
installation

Two Components
Software
Macrovision is the provider of the software
solution, FLEXNET
Hardware
Aladdin is the provider of the hardware
solution called HASP HL

39
 NOW: FLEXNET Software licensing

License models
Floating
Requires a license server
Node locked
License is locked to a specific piece of
hardware, component in a PC or TAC
hardware key/dongle (HASP HL)

Possible to have a license where no

dongle is required

40
 NOW: FLEXNET Software licensing

Dongle or No Dongle?
If no dongle is used and locking is required, the
license will be locked to the PC MAC address
This is done via the licensing.tac.com website
using the Entitlement ID or Activation ID
The license can only be rehosted 4 times per
year
See the TAC Licenses Installation Manual for
step-by-step
Locking a license to a dongle makes moving the
license server and licenses from one PC to another
more simple and can be done as often as desired
Dongles cost a little more

41
 Floating License

42
 Node locked license

43
 Upgrading to FLEXNET Licensing
and Dongles

All customers will require a new License File (.lic)

Dongle may be required if license locking option is
selected
USB, LPT
All TAC employees
and partners will
require a new dongle unless
using monthly demonstration
license obtained on
Exchange Online
In-house dongles are
a different color than
customer dongles
Note: TAC Vista clients check for a locally connected
Inhouse dongle. TAC I/NET Host Tool, however requires
the Inhouse dongle to be connected on the computer
where the TAC Vista Server is running

44
 Upgrade to FLEXNET Licensing and
Dongles

Customer licenses will need to be upgraded

Number of licenses needing to be upgraded depends on
the number of concurrent program usage required
Example: Lets say a customer has 10 licenses for
Workstation, but only uses 5 of them concurrently.
It may be most appropriate to only upgrade 5
licenses to Vista 5
Note: When upgrading to Vista 5, all software
modules that will be used will need to be upgraded
For example, having one PC with Workstation v4.5
installed and another PC with Workstation v5.0 on the
same network is not supported
All dongles will need to be replaced if option for license
locking to a dongle is required
Return old dongles to the TAC Manufacturing and
Logistics Division

45
 License Server

Applies to floating licenses only

Is an option for automatic installation when
installing TAC Vista Server and ToolPak
software
The license server and the licensed
applications communicate using TCP/IP
The default ports are 27000 27009
It is possible to set a custom port
All license files are normal text files that can be
viewed (and to some extent modified) in any text
editor

46
 FLEXNET Documentation

Additional documentation is available

from Macrovisions homepage
See the End User Guide at:
http://www.macrovision.com/pdfs/flexnet_
licensing_end_user_guide.pdf

47
 TAC Vista 5
Software Packages
 THE PAST: Old Packages

49
 NOW: Vista 5 Packaging

50
 NOW: Maintenance Agreement

Yearly fee of 15% of the full license

cost, the licensee is eligible for
upgrades to the latest version
Customers without a maintenance
agreement pay 40% of the full license cost
for upgrades to 5.0, 5.1, etc.
A change to the first or second digit in the
Vista version will require upgraded licenses

Notice period is 3 months and

termination has to be done in writing
to TAC AB order department
51
 NOW: Maintenance Agreement

Until April 30, 2007, existing licensees of

Vista are eligible to upgrade to Vista 5 by
entering the maintenance agreement only
Enables existing customers to get the latest version
for only 15% instead of 40%
Upgrade licenses are now ordered individually
No longer only one upgrade part
Eligible products for upgrade include:
TAC Vista 2000 or later
Any version of TAC I/NET
Satchwell VisiView

52
 NOW: In-house Subscription
Service

For engineering, training, and sales

personnel within TAC and partner
companies
Includes 1 dongle and, for every new
release, updated CDs
Cost is invoiced in advance every 12
months

53
Upgrading to
TAC Vista 5
 Upgraded Software and Hardware

55
 Upgrade Requirements

Database created before TAC Vista 4.01 can

NOT be upgraded directly to TAC Vista 5
Must first be upgraded to TAC Vista 4.5 and then to
Vista 5.0
Databases created using TAC Vista 4.01 or
later can be upgraded directly to TAC Vista 5
Some manual interaction is required to upgrade
SQL databases from Vista 4.3.0/4.3.1 and SQL
databases that are administered by customer
Webstation and ScreenMate licenses earlier
than version 4.3.0 require new licenses
Inhouse PSU enables browsing on the same
computer as the server software

56
 Upgrading Requirements

TAC Xenta 527/511/913 system version 5.0

requires the use of XBuilder version 5.0
When an Xenta 527/511/913 project created
in XBuilder v1.60 or earlier is opened in
XBuilder v5.0, the project will automatically
be upgraded
After the upgrade to XBuilder v5.0 has
occurred, Device Templates created in
XBuilder v5.0 or earlier need to be opened
and resaved in order to work appropriately
Device Templates are used in XBuilder for Modbus
and BACnet devices for example

57