FactoryTalk View SE applications

FactoryTalk Directory

that lets the parts of an application to find each other on a computer, or on the network. For example, to access graphic displays on HMI servers,

FactoryTalk View SE

clients use FactoryTalk Directory to find which computers on the network are hosting HMI servers.

HMI servers

that supply information to clients when they request it. Each application must contain at least one HMI server. HMI servers store HMI project components (such as graphic displays), and serve these components to clients. Each HMI server also manages a database of HMI tags, and historical data management (logging).

Areas

that let you organize a network distributed application and sub-divided it into logical or physical divisions. The use of areas is optional unless the application is to have more than one HMI server, in which case you must use areas because there can only be one HMI server per area.

HMI project components

such as graphic displays that provide a view of the processes the application is monitoring, HMI tags that can retrieve and store data about the processes, and data log models that let you specify which data is to be displayed and where.

FactoryTalk View

user accounts and access codes (permissions)

used to set up runtime access to HMI project components such as graphic displays and tags.

Data servers

that give clients access to information in programmable controllers, devices, and other data servers that comply with the OPC DA 2.05a, UA 1.02 or 1.03 specifications., without the use of HMI tags. You can also set up a redundant pair of host computers for the data servers in the application.

Some OPC servers contain tag databases of their own, like the tag database in an HMI server, while others reference the tag databases that exist in the programmable controllers themselves. This is the case with

FactoryTalk Linx

and a

Studio 5000

processor.

FactoryTalk Security

which is installed as part of the FactoryTalk Services Platform, and you can set up to authenticate user identities and authorize user requests to access resources managed by the FactoryTalk Directory. When you install the

FactoryTalk View SE

on a computer for the first time with the standard FactoryTalk Directory mode, in the FactoryTalk Directory Network, all users that are members of the Windows Administrator group on any local computer that is connected to the FactoryTalk Network Directory, will have full access to the directory and to

FactoryTalk View

.

FactoryTalk Directory, an HMI server, HMI project and HMI client

all located on the same computer. For a local station application, the HMI server and HMI project are created automatically when you create the application. The HMI project is given the same name as the HMI server.

HMI project components

such as graphic displays that provide a view of the processes the application is monitoring, HMI tags that can retrieve and store data about the processes, and data log models that let you specify which data is to be displayed and where.

FactoryTalk View

user accounts and access codes (permissions)

used to set up runtime access to HMI project components such as graphic displays and tags.

Data servers

. You can add non-HMI data servers to a local station application. These do not have to be located on the same computer as the rest of the application's components.

FactoryTalk Security

which is installed as part of the FactoryTalk Services Platform, and you can set up to authenticate user identities and authorize user requests to access resources managed by the FactoryTalk Directory. When you install the

FactoryTalk View SE

on a computer for the first time with the standard FactoryTalk Directory mode, in the FactoryTalk Local Directory all users have full access to the directory and to

FactoryTalk View

.

All computers participating in a particular network distributed application share a common FactoryTalk Directory located on a network server.

The name for any area, data server, or HMI server at a given level in the FactoryTalk Directory should be unique.

Names for the following

FactoryTalk View Studio

components do not support extended ASCII characters or Unicode characters: applications, areas, HMI servers, data servers, HMI tags,

FactoryTalk Linx

shortcuts,

FactoryTalk View Studio

application files (. SED), and all

FactoryTalk View

application components, including graphic displays, parameter files, macro files, events files, derived tag files, and data log files.

There can be more than one application on a network, but the HMI server can only participate in one application at a time.

When adding a third-party OPC data server to a network distributed application, it is best to place the data server in its own area, separate from the area in which the HMI server resides. This avoids unnecessary OPC requests and reduces the overall number of OPC transactions between FactoryTalk Directory and the OPC data server.

FactoryTalk Linx

is optimized for use with all products in the

Studio 5000

controller family including ControlLogix, CompactLogix, FlexLogix, DriveLogix, SoftLogix, and GuardLogix controllers.

For a more detailed discussion about

FactoryTalk View SE

applications, see Chapters 6 and 7 in the

FactoryTalk View

Site Edition User's Guide

.