ThinManager - IRT Forum 2021
•Download as PPTX, PDF•
0 likes•94 views
This document describes ThinManager, a platform for centralizing and distributing industrial content. It allows secure delivery of content like web pages, applications, and configurations to thin clients and devices. Content can be assigned based on users, groups, roles, locations, or devices. ThinManager provides benefits like reducing downtime through failover, improving efficiency with location-based delivery, and easier management through centralized administration and profile-based deployment to terminals. It replaces dedicated PCs with low-cost thin clients that have benefits in security, manageability, and total cost of ownership.
More Related Content
What's hot
What's hot (19)
Similar to ThinManager - IRT Forum 2021
Similar to ThinManager - IRT Forum 2021 (20)
Recently uploaded
Recently uploaded (20)
ThinManager - IRT Forum 2021
- 1. PUBLIC ThinManager® Centralizacija in napredna distribucija vsebin v industrijskem okolju Jože Perko, Peter Skopec, ControlTech d.o.o.
- 2. Content Delivery and Device Management ThinManager® Platform HMI ERP MES CMMS™ …AND MORE! ThinManager® provides secure configuration and delivery of content Content Types Web Content Delivery User X Group X Role X Configuration Devices Users Locations Industrial terminal IP Camera USB Camera Web Content Management Hardware
- 3. Dedicated PCs for Dedicated Applications Traditional Automation Network Level 3 Industrial Security Zone Level 2 Cell/Area Zone Level 0-1 Cell/Area Zone Active Directory FactoryTalk Directory Activation Manager Data Servers HMI, FTAE, FTLinx APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS APPS ANTI- VIRUS USB ACCESS MOVING PARTS OS
- 4. Replace PCs with Thin Clients and Manage Centrally ThinManager® Solution Level 3 Industrial Security Zone Level 2 Cell/Area Zone Level 0-1 Cell/Area Zone ... Active Directory FactoryTalk Directory Activation Manager Data Servers HMI, FTAE, FTLinx ThinManager Remote Desktop Services FT View SE Client Scalable Architecture FT View SE Client Studio 5000, etc. APPS ANTI- VIRUS OS
- 5. Managed Thin Client Benefits More secure: • No local storage – nothing is stored on device • Can eliminate access to the Windows Desktop • USB ports are disabled by default for everything except and keyboards/mice Lower total cost of ownership than PCs over the lifetime of the system: • Integrates with ThinManager® software for efficient centralized management • Less likely to fail because they don’t have hard drives or fans and they contain industrial grade components suitable for harsh environments • Easier to replace when they do fail, significantly reducing downtime • Smaller and require less power to operate and cool • Fewer client operating systems to manage
- 6. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 6 Any PC (or other Thin HW) as Thin Client Using PXE boot • Preboot eXecution Environment (PXE) is an Intel standard whereby an operating system can be delivered over the network • For TM compatible devices (x86 platform) Using WinTMC: • Installed on any Windows OS • Free download • Usable where local OS is needed
- 7. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 7 Mobile devices as Thin Client iOS devices • Using iTMC app • Free download Android devices: • Using aTMC app • Free download
- 8. Why Customers Use the ThinManager® Platform Reduce Downtime • Automatic Remote Desktop Server failover • Redundant networking options at thin client and server • Aggregate multiple content sources at 1 terminal Improve Operational Efficiencies • OT-Centric solution designed for the plant floor • Visualize content with tiling & virtual screening • Location-based content delivery (Relevance®) Ease of use • No local configuration of thin client required • Admin console and terminal to terminal shadowing • Industrial thin clients & broad touch screen support Configuration Wizards Easily manage and distribute your existing content without the need to re- engineer the existing solution Quick Replacement Most thin clients can be replaced by anyone in under 2 minutes without any loss of data or lengthy hardware validation process 1 2 3
- 9. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 9 ThinManager environment
- 10. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 10 ThinManager environment
- 11. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 11 ThinManager environment
- 12. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 12 ThinManager environment
- 13. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 13 ThinManager environment
- 14. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 14 ThinManager environment
- 15. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 15 ThinManager environment
- 16. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 16 ThinManager environment
- 17. PUBLIC | Copyright ©2020 Rockwell Automation, Inc. 17 ThinManager environment
- 18. ThinManager terminal is powered on Thin Client is Powered On
- 19. ThinManager Firmware is Delivered ThinManager firmware is delivered to terminal • The ThinManager firmware is delivered by the ThinServer service • The firmware is the ThinManager OS • It is delivered to a thin client right at boot time Firmware
- 20. Terminal Profile is Delivered Profile ThinManager Terminal Profile delivered • The Terminal Profile is also delivered by the ThinServer service • The Terminal Profile defines the terminal content to deliver • It also defines how to display or visualize the content • Modules for touchscreens, badge readers, etc. can also be added to the terminal profile
- 21. Terminal Profile Content Delivered Content assigned to Terminal Profile delivered • ThinManager can deliver content in 3 different ways: 1. Assign content to the terminal 2. Assign content to a user or user role 3. Assign content to a location (Relevance) Terminal Content
- 22. Firmware Firmware Failover and Redundancy Terminal Content Failover • Defined as multiple sources for your content • For example: multiple Remote Desktop Servers Redundancy • Defined as multiple installs of ThinManager • ThinManager installs automatically synchronized Terminal Content
- 23. MultiSession and Tiling Terminal Content MultiSession and Tiling • Delivering more than one content type to a terminal • Example: • 2 SCADA client instance • 1 SCADA HMI instance • 1 Terminal Shadow Terminal Content
- 24. MultiMonitor MultiMonitor • Up to 7 4K monitors can be connected to a single terminal 1. Left monitor: • 2 SCADA client instances • 1 SCADA HMI instance • 1 Terminal shadow 2. Right monitor • 1 Dashboard application instance • 1 IP Camera Terminal Content Terminal Content
- 25. Virtual Screening Virtual Screening • Evolution of MultiMonitor • Similar to tiling, but layout is configurable • Each Virtual Screen behaves like a physical display • Tiling is supported within each virtual screen • Can configure virtual screen swapping and full screen • Content overlays fully supported Terminal Content Terminal Content
- 26. User Based Content Delivery Terminal Content User logs in using Relevance User services • Relevance User credentials can reside within ThinManager or can be linked to an Active Directory account • Once authenticated, additional content can be delivered to the terminal based on the user or the user’s role • A badge or fingerprint can be associated with the user to simplify the login process User Content Terminal Content User Content
- 27. Location Based Mobility Relevance • Mobile Devices are managed exactly the same way as thin clients in ThinManager. • Each Location can be assigned content as well as a Location Resolver. • QR Codes • Bluetooth Beacons • WiFi Access Points • GPS • Location content can be geo-fenced to physically limit where the content can be accessed. • Example: QR Code on PLC panel is scanned by mobile device and an instance programming software is delivered to the tablet with the correct project file automatically opened. Location Content
- 28. Why Customers Use the ThinManager® Platform Reduce Downtime • Automatic Remote Desktop Server failover • Redundant networking options at thin client and server • Aggregate multiple content sources at 1 terminal Improve Operational Efficiencies • OT-Centric solution designed for the plant floor • Visualize content with tiling & virtual screening • Location-based content delivery (Relevance®) Ease of use • No local configuration of thin client required • Admin console and terminal to terminal shadowing • Industrial thin clients & broad touch screen support Configuration Wizards Easily manage and distribute your existing content without the need to re- engineer the existing solution Quick Replacement Most thin clients can be replaced by anyone in under 2 minutes without any loss of data or lengthy hardware validation process 1 2 3
- 30. www.rockwellautomation.com Hvala za vašo pozornost
Editor's Notes
- Script: Here we have a centralized Remote Desktop Server with ThinManager installed on it. The server has the client applications on it that we would like to distribute using ThinManager. As previously mentioned, ThinManager does not require or depend on Remote Desktop Services, but it is most commonly deployed with Remote Desktop Services.
- Script: The VersaView 5200 pictured here does not have a locally installed OS (could be described as a zero client in fact). When the VersaView 5200 is connected to a network with ThinManager present, it will receive the ThinManager firmware right when it boots up. The firmware is approximately 13MB in size, and on today’s networks, it is delivered and installed within seconds. Since the VersaView 5200 is ThinManager Ready, it can be assigned a Static IP address, or use DHCP. Value: No operating system stored on the device makes that device much easier to manage. Fewer operating systems to maintain and support.
- Script: Once the firmware is delivered, the VersaView 5200 will request its Terminal Profile from ThinManager. If this is the 1st time the device is booted, ThinManager will most likely not have a Terminal Profile assigned to the MAC address of this new device. Therefore, a list of available Terminal Profiles will be made available from which to select. Once assigned, ThinManager creates a marriage between the Terminal Profile assigned and the MAC address of the new device. Each subsequent bootup will not require assignment, as ThinManager will automatically recognize it. If the terminal is replaced, all that is required is the correct assignment of the Terminal Profile of the failed/replaced terminal. The new terminal will essentially assume the outgoing terminal’s identity and even reconnect to its content sources, which were not disrupted during this process. Value: The terminal profile is created and managed centrally. No configuration done at the terminal itself. This makes terminal replacement very easy – simply assign the correct profile to the replacement device. No re-building of client operating systems. This leads to enormous downtime savings.
- Script: Once the Terminal Profile is delivered, the associated content will be delivered to the terminal. In this example, an instance of the FactoryTalk View SE Client is delivered to the terminal. Content (called Display Clients in ThinManager) can also be assigned and delivered by User or by Location. In addition to Display Clients, you can also configure other characteristics of the terminal within the Terminal Profile: Terminal schedules can be defined if the terminal only needs to be available on certain days or during certain times of the day. The shadowing behavior can be set (i.e.: Enabled, Disabled, Ask, Warn). Modules (drivers) can be assigned to enable external device connection like touchscreens and/or badge readers, etc. ThinManager includes a number of other Modules that provide additional functionality to the terminal. Value: ThinManager terminals are significantly more secure than the PCs that they replace. No local OS to secure, and no Windows desktop to protect.
- Script: Failover is defined as having multiple sources available for your content. In the example above, a second Remote Desktop Server is added that can also host the FactoryTalk View SE Client. If the Primary goes down, the terminal will automatically failover to the Secondary Remote Desktop Server. Redundancy, on the other hand, is having 2 installs of ThinManager whose configurations are automatically synchronized. The main role of the ThinServer service is to deliver the Terminal Firmware and Terminal Profile. Once a terminal is booted and connected to its Content Sources, the ThinServer service could be shut down, and the terminals would continue to run. However, if the ThinServer became unavailable AND you attempted to boot up a terminal, it would not be able to boot because it would have no source from which to receive its firmware and profile. For this reason, many users opt for ThinManager Redundancy. There are 2 types of Redundancy available: Mirrored and Full. Both provide 2 separate installations of ThinManager whose configurations are automatically synchronized. Mirrored is a lower cost alternative that has a restriction. Namely, one of the ThinManager installations is designated as the Primary and it is from this and only this install that you can make changes to the ThinManager configuration. Full Redundancy does not have this restriction (i.e.: you can make ThinManager configuration changes from either installation – Primary or Secondary). Value: Failover reduces downtime and improves the maintainability of the system. Content servers can be taken offline for patching, etc. without affecting production. Redundancy also reduces downtime by providing a secondary source for booting thin clients.
- Script: ThinManager’s ability to aggregate multiple content sources using MultiSession is one of its most powerful and popular features. Any time more than one Content Type (Called Display Clients) is assigned and delivered, it is called MultiSession. Multiple Display Clients can be visualized simultaneously using Tiling Mode. ThinManager supports up to 25 tiles in a 5x5 grid on a single display. Tiling is optional – if it is not used, then there really is no limit to how much content could be delivered to a terminal. Remember that the majority of the processing required is not occurring at the terminal. Clicking on a tile will bring that tile full screen enabling interaction. There are a number of configurable ways to switch between Display Clients and to/from Tiling mode. The 2 SE Client instances are Remote Desktop Services Display Clients. The 1 SE Client instance is a Workstation Display Client. The 1 PanelView Plus Shadow is a VNC Display Client. Value: Multisession and Tiling really result in increased productivity by providing consolidated views of all of the content required by an end user, allowing them to maintain a pulse on the production system.
- Script: Because of ThinManager’s strength of bringing multiple content types together, it is often necessary to spread the content out across multiple physical displays. ThinManager supports up to 5 physical displays connected to a single terminal. MultiMonitor is often deployed in Control Room environments, where multiple PCs, keyboards and mice make it challenging to support and maintain. As an example, 3 five monitor thin clients could be used to drive 15 displays, and management is reduced to maintaining 3 terminal profiles in ThinManager. ThinManager also includes a module (which are like drivers), called the Shared Keyboard and Mouse module. that could be applied to the 3 terminals that would enable a single keyboard and mouse to control all 3 terminals and hence all 15 displays. Content (called Display Clients within ThinManager) can be assigned to each display by default (tiling is still supported), but it can also be configured to moveable by the user of the terminal so the Display Clients can be moved from one display to another. This behavior is completely controllable, so the ThinManager administrator can configure which Display Clients are moveable versus not. Similarly, a display can be configured to either be protected, so that it cannot receive additional Display Clients, or not. Value: MultiMonitor and Virtual Screening really simplifies Control Rom deployments, greatly simplifying the management and maintenance of the computing resources required in those environments. Numerous Control Room PCs can be replaced by thin clients all managed by a few terminal profiles in ThinManager.
- Script: Virtual Screening is the evolution of MultiMonitor in ThinManager. Instead of investing in multiple physical displays, end users may choose to invest in bigger, 4K displays. 4K = 3840x2160 in resolution (basically a 2x2 grid of 1920x1080 HD displays) A thin client with graphics support for 4K would be required to drive a 4K display. Content can overlap as well. Value: MultiMonitor and Virtual Screening really simplifies Control Rom deployments, greatly simplifying the management and maintenance of the computing resources required in those environments. Numerous Control Room PCs can be replaced by thin clients all managed by a few terminal profiles in ThinManager.
- Script: User Based Content delivery is 2nd way in which content can be delivered. Relevance Users (formerly known as TermSecure) provides the ability to assign and deliver content based a user or a user’s role. A User’s credentials can reside in ThinManager or linked to an Active Directory account (much like Windows Linked Users in the FactoryTalk Directory). ThinManager supports RFIDeas badge readers and Crossmatch fingerprint scanners, each of which can be associated with a Relevance User. ThinManager can also store a Relevance User’s password, or even rotate it automatically on a pre-defined schedule. Value: User Based Content delivery increases both Security and Productivity. Multi-factor authentication (badge plus password, or fingerprint plus password) results in a more secure environment, where a user receives only their designated content. Users can have their specific content delivered to them at any terminal managed by ThinManager. No need to run back to PCs for the content they need.
- Script: Unlike a ThinManager thin client, the ThinManager firmware is not compatible with most mobile devices, which have their own OS (iOS, Android and Windows). Instead of delivering the ThinManager firmware to these devices, a ThinManager Client (TMC) application can be used. iTMC = iOS, aTMC = Android, WinTMC = Windows. Each of these apps emulates a ThinManager thin client and can therefore be managed centrally from ThinManager. Similar to a thin client, each mobile device will require a unique Terminal Profile in ThinManager. Relevance User based content can be delivered to the mobile device (just like a thin client). Most importantly, Location based content can be delivered. Defining a Location in ThinManager is accomplished by assigning the desired content to it as well as assigning a Location Resolver. A Location Resolver basically tells ThinManager to which Location the mobile device has resolved. Permissions can also be assigned to the Location Resolver (i.e.: only Maintenance users can scan the QR Code on the PLC Panel and receive Logix Designer). ThinManager supports 4 Location Resolvers currently: QR Codes – these can be printed out using a number of free web based utilities. Bluetooth Beacons – think of these as proximity sensors for your mobile devices. They have a maximum range of 50 meters and can be purchased in battery or USB powered options. Beacons are often used to geo-fence content so a user cannot leave a certain area/zone with the delivered content. WiFi Access Points – ThinManager can detect which Access Point a mobile device is connected to and based on this connection either enable or disable access to content. GPS – for outdoor applications, GPS can be used to define a location. Mobile devices can also interact with thin clients in some very unique ways: Content delivered to a thin client can be transferred/redirected to a mobile device. Content delivered to a thin client can be shadowed by a mobile device. Content delivered to a thin client can be cloned and delivered to a mobile device. Value: Delivering location based content will also greatly improve productivity and reduce downtime by quickly delivering location based content to a user’s mobile device to help them more quickly assess equipment status and take corrective action.
- Slide is should be self explanatory.