2What’s New? User Account Synchronization Rename and Replace with DeltaVAdd Device Type with DeltaVMultiple PlantWeb Alerts per CategoryWindows User AccountsNon-Responding and Unknown DevicesOnly Foundation Specified FilesClient SC Station CountTag CountSQL 2005HELP | AboutMicrosoft Operating SystemsDeltaV Zone MessageSureService Registration Utility
3User Account Synchronization DeltaV adds new DeltaV users to the AMSDeviceManager security groupAMS Device Manager polls DeltaV for the currently logged in user; allowing AMS Device Manager to always be in-synch with DeltaV
10User Account Synchronization When Enable Automatic Login… is selectedThe AMS user always matches the DeltaV userThe current DeltaV user is automatically logged into AMS Device Manager when AMS Device Manager is launched from the Windows Start MenuIt is not be possible to change the AMS Device Manager user from within AMS Device ManagerIt will only change if the DeltaV user changes
11User Account Synchronization When Enable Automatic Login… is not selectedThe current DeltaV user is logged in as the AMS Device Manager user if AMS Device Manager is launched from a DeltaV Application (in context or not in context)The user is prompted for user ID and password when AMS Device Manager is launched from the Windows Start MenuThe logged in AMS Device Manager user can change without the DeltaV user changingThe AMS Device Manager user does not change if the DeltaV user changesThe user timeout function is enforced
14Rename and Replace with DeltaV Prevent the user from manually renaming the AMS tag within AMS Device Manager for a device on the DeltaV hierarchyChanging this option is tied to the AMS Device Manager Admin privilege and is a system wide setting.
16Add Device Type with DeltaV The AMS Device Manager utility distributes the device files to the other AMS Device Manager stations for HART and FF.If one of the AMS Device Manager stations is on the DeltaV ProPlus, DeltaV then pushes the device files to the other DeltaV stations for HART and FFAMS Device Manager’s Add Device Type does not perform any licensing checksThe customer can run it whether or not AMS Device Manager is licensed
17Multiple PlantWeb Alerts per Category The same device can have simultaneous alerts of the same category (Failed, Maintenance, and Advisory)
18Windows User Accounts DeltaV user accounts use Windows passwords Administrators do not have to assign another password to these usersWhen users login directly to AMS Device Manager, they will use the same password as they do for DeltaV
19Windows User AccountsIn order to do this, it is necessary for users to recreate their AMS Device Manager accounts in WindowsThe use of Windows logins (passwords and ID’s) is optional
24Non-Responding and Unknown Devices Distinguish between device non-responding and device unknown (device not added to database because of license limit)
25Only Foundation Specified Files Required The device developer is only required to supply the registered DD fileIf they do not supply an AMS merge file, Window resource file, DDinstall.ini file, map file, or device icon for EDDL devices, Emerson provides a generic version of these filesIn this case, the user will have a subset of the typical AMS Device Manager functionality for the given EDDL deviceFeatures supported are configure, status/diagnostics, process variable, Audit Trail, and Alert Monitoring screens
26Client SC Station Count 4/1/2017Client SC Station CountSupports licensing 131 Client SC stations, in addition to the Server Plus stationTested to support up to 20 concurrent Client SC stations
28SQL 2005 AMS Device Manager v9.0 only works with DeltaV 9.3 This is due to SQL 2005Compatibility with DeltaV 8.4 and/or 7.4/7.3 systems is supported for stand-alone deployments only
29HELP | AboutDisplays the ‘Number Registered Tags’, ‘Number of Licensed Tags’, ‘Number of licensed stations’ and ‘Number of configured stations’.
30HELP | AboutAdded a Print button to print out all licensed options, number of registered tags, number of configured stations, current AMS Device Manager version.
31DeltaV Zones MessageMessage displayed when attempting to launch a device conditions screen from a DeltaV Operator station located in a different DeltaV zone from the device
32SureService Registration Utility AMS Device Manager makes available (via Generic Export) the following system profile information for inclusion in the Guardian product support service:Number of registered HART and FF devicesLicensed system interfaces (e.g. DeltaV, HART Mux, etc.)Version information
33Support Different Macro Cycles The device FHX file contains information so DeltaV can support cascade loops with sub-schedules running at different macro cycles
34Microsoft Operating Systems Supported on Windows XP and Windows 2003 Server