SCT is used for offline configuration of system engines and servers . The SCT assists in all phases of engineering, installing, and commissioning of devices that make up the BAS. The key features and functions that SCT provides include the following:
- The NAE/NIE Update Tool is bundled
with SCT. When you install SCT, the NAE/NIE Update Tool is also installed in the background.
At SCT Release 13.0 or later, the tool is renamed to the NAE Update Tool. To launch the NAE
Update Tool, navigate to Note: From SCT Release 14.0, you can use SCT Pro in lieu of the NAE Update Tool because all of the NAE Update tool functions are available in SCT Pro.
. The NAE Update Tool does not have a desktop icon and you cannot uninstall
the NAE Update Tool without also uninstalling SCT because the tool is bundled with SCT.
- SCT uses the same user interface format as the Site Management Portal UI. This similarity makes the transition between online and offline access intuitive.
- SCT supports sites back to Release 5.2, except in cases where there are wireless supervisor devices on the site.
- SCT creates and restores site archive backups. Site archives with supervisory controllers and servers from Metasys Release 5.2 or later can be managed with SCT Release 10.0 and later.
- Multiple site archives can be managed in one local instance of SCT.
- SCT can fully manage a
mixed-release site with supervisory devices at different versions. You can add and manage
supervisory devices from Metasys Release 5.2 and later. Note: To perform a code download for site devices, you need to have the appropriate release version of device's image stored on the SCT computer. The device being updated through download must be at an equal or lower release than the Site Director.
- The Manage Archive function lets you upgrade a device from a previous release to a later release. Once you upgrade a device, Manage Archive coordinates the upload, download, upgrade, and synchronization of the devices on a site.
- As part of the upload function, SCT provides the ability to upload the Controller Application Files (called .caf files) from field controllers attached to the supervisory device into the archive database. The supervisory device must be at version 6.0 or later. During the upload process, SCT creates or updates the Resource extension for the field controller.
- SCT provides import database and export archive database functions. These capabilities eliminate the need for Tools for different releases that were created against different versions of Microsoft® SQL Server® software. SCT can import archives that were created with any supported version of SQL Server software (that is, SQL-independence). For archives created prior to Release 5.2, continue to use vTools as a resource when working with Metasys systems. (Note that you should not use the export database function as a substitute for backing up the archive database periodically.)
- SCT also provides a Site Discovery feature that lets you create the archive database from an online system when the archive is not readily available or corrupt, the existing archive is outdated, or the archive has not been maintained. For devices at Metasys Release 5.2 or later and FX devices, the Site Discovery feature creates the archive at the SCT release version and discovers the devices as their physical device release version. For devices earlier than Metasys Release 5.2, the devices are treated in the archive as 5.2 version devices.
- SCT can update the software disk image of a supervisory engine, offering a convenient alternative to the NAE Update Tool. As a prerequisite to this option, the images of the supervisory engines that you want to update must be stored on the SCT computer.
- You can use SCT to download software patch files to NxE55-2, NxE55-3, and NIE59 supervisory engines that are currently at Release 6.5 or later. The NxE55-0, NxE55-1, NxE3x, NxE4x, NxE55-3, and NxE2x engines require a full image download using the Download Code option built into the SCT to deliver complete image files.
- As a configuration step for downloading an image or patch for an NxE, select which Ethernet adapter the SCT computer uses to perform the operation using the menu item.
- When you have uploaded the .caf file from a field controller, you can use the Export CAF File option in SCT to export this file from the SCT archive database to the computer for use with the Controller Configuration Tool (CCT). An option is also available to export every .caf file from all field controllers on a single Field Bus.
- SCT allows you to create and manage the User Security System database for a site. The security databases for all the devices on a site are optionally uploaded and downloaded as part of the manage archive functionality. A selection called SCT Security is available under the Security Copy feature that lets you copy the existing set of SCT users to any supervisory engines on the site.
- Starting at 7.0, installations that have SCT installed on the same machine as the server have separate security databases for user access credentials for SCT and the SMP.
- Diagnostic features are available to review the upgrade process logs, assess if an archive has points that have been created that are no longer used or unbound, and summarize the makeup of the features and objects that have been created on each engine in a site's archive.
- Multiple users can access a single database at once, enabling simultaneous updates. However, keep in mind that simultaneous database updates exhibit a last user wins behavior. For example, User A and User B open the same focus view for an engine. User A makes an attribute change and saves the change. User B makes an attribute change and saves the change. User A's changes are gone, superseded by User B's changes.
SCT includes a Certificate Management option that you can use to configure a network engine for secure, trusted communication. Supported operations for network engines include requesting, importing, exporting, downloading, and uploading certificates. To configure the ADS/ADX/OAS for secure communication, you use the certificate management functions within the operating system. For details, refer to the Metasys Server Installation and Upgrade Instructions (LIT-12012162) .Note: From Metasys Release 8.1, the Metasys server and all network engines are installed with self-signed certificates by default. You only need to use the SCT Certificate Management functions if you want to deploy trusted certificates.