FactoryTalk View SE Network Station

Architectures Considerations
 FactoryTalk View SE Network Station Architecture Examples

Contents
Network Scope FactoryTalk View SE Station Considerations ................................................................. 3
Network Scoped FactoryTalk View SE Stations with FactoryTalk Directory and local and remote
RSLE Data Servers. .............................................................................................................................. 3
Network Scoped FactoryTalk View SE Stations separate FactoryTalk Directory and local and
remote RSLE Data Servers................................................................................................................... 4
Multiple FT View SE Station Applications per FactoryTalk Directory ..................................................... 5

FT View Network Station Considerations

 FactoryTalk View SE Network Station Architecture Examples

Network Scope FactoryTalk View SE Station Considerations

Network Scoped FactoryTalk View SE Stations with FactoryTalk Directory
and local and remote RSLE Data Servers.
Architecture specifications:

• Remote RSLE Data Servers (Max of 5 in Application)

• Factory Talk View SE Network Station can access data from Historian ME and SE on the FT
View SE TrendX
• Share FactoryTalk Directory network security
• FT View SE Network Station Maintain
• No remote client connectivity
• No FT View Studio remote connectivity

Typical FT View SE Network Station with FTD on the same machine and local/remote RSLE

FT View Network Station Considerations

 FactoryTalk View SE Network Station Architecture Examples

For a FactoryTalk application that has one FT View SE Network Station and one FT Historian SE
(FTHSE) server can be configured as:

• One FactoryTalk Directory-Network (FTD-N) scope with two applications (one FT application
for FT View Network Station and a separate FT application for FT Historian)
• Both products to a share a common FTD-N application

The question is for this type of architecture with one FTD-N, do we recommend using one or two
FactoryTalk applications

• There is no advantage either way, with everything in one application there is less to manage.
The only reason to lean a one direction would be if FTHSE (or more aptly, FTTM) required
access to the HMI tags - in which case we'd want to go same application.

FT View SE Network Station allows multiple RSLinx Enterprise and OPC data servers (including RSLinx
Classic), running on different computers.

You can also set up a redundant pair of host computers for each data server in the application.

Network Scoped FactoryTalk View SE Stations separate FactoryTalk

Directory and local and remote RSLE Data Servers.

Typical FT View SE Network Station with separate FTD on the same machine and local/remote RSLE

FT View Network Station Considerations

 FactoryTalk View SE Network Station Architecture Examples

Multiple FT View SE Station Applications per FactoryTalk Directory

For architectures consisting of two or more FT View SE Network Station, these can share a common
FTD (multiple FT View Network Station per FTD)

• E.g. One FTD can have multiple FT View Network Station (v7.0)
• Note: this multiple application per FTD only applies to FT View network station, and does
not apply to any other FT products.

For an architecture that consist of two or more FT View SE Network Station applications in one FTD,
and FT Historian SE, FTTM, or other FactoryTalk enabled product, where should the FT Historian SE
be located

• In its only FTD application

• Be referenced in all of the Network Station FTD applications

With FT Historian SE (or other FactoryTalk enabled products) in its only FT application (three or more
applications within one FTD, as in this example), and with the data servers reference in each of the
FT applications, data is shared across applications

The recommendation is that any time we have more than one FactoryTalk View SE network station,
separate application for all the other stuff (e.g., FT Historian SE, FTTM, etc.) This will keep it cleaner
(no wondering, "Which app did I stick that Historian in?) and would allow for downtime of other
applications without affecting "the other stuff.“

Factory Talk View SE Network Station does not:

• Allow sharing of HMI screens or data to other View SE Stations

• Allowing sharing of FTA&E to other View SE Stations.

Factory Talk View SE Network Station does

• Allow sharing of RSLinxEnterprise servers

FT View Network Station Considerations

 FactoryTalk View SE Network Station Architecture Examples

Two View SE Station Applications in One FactoryTalk Directory

FT View Network Station Considerations