SNE configuration - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide

Brand
Metasys
Product name
SNE10 Network Engine
SNE11 Network Engine
SNE22 Network Engine
SNE Supervisory Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active
Language
English

SNE configuration is preparing the engine with the Site Management Portal UI and the SCT to operate on a specific Metasys network site, and communicate with, monitor, and control specific BAS field devices on that site. Configuration also includes preparing the SNE to compile, generate, and communicate information about site status, alarms, events, and trends.

You can typically accomplish SNE configuration by downloading a pre-built archive database (from the SCT) that contains the device objects, object references, attribute values, logic, graphics, user information, and other references and data required for the SNE to perform its specific tasks on the network.

Alternatively, you can create and edit an archive database online in the Site Management Portal UI, but it may be more convenient to create and edit the SNE archive database offline in the SCT. When you download the database, the values in the archive database overwrite the existing values on the commissioned SNE. Refer to the SCT: System Configuration Tool Help (LIT-12011964) for information on creating and downloading archive databases.

After you configure an SNE with an archive database, you can set up the email, Syslog, and SNMP DDAs and create specific alarm and event notifications for delivery to specific email, Syslog server, and network management destinations.

Here is an overview the steps to commission and configure the SNE:

  1. Add and configure a site. Refer to Metasys SCT Help (LIT-12011964).

  2. Add and configure the engines in the site with the SCT, including any third-party integration. If you are configuring an integration for an SNE that requires the engine's USB port, you need to enable the USB port in the user interface.

  3. Complete building the offline archive database in the SCT. [For all of these steps, refer to Metasys SCT Help (LIT-12011964)].

    1. Set Advanced Security Enabled attribute.

    2. Add integration trunks, field devices, and field points.

    3. Add programming logic using the Logic Connector Tool.

    4. Configure alarm and trend extensions and audit logs.

    5. Configure alarm destinations: email, Syslog, and SNMP DDAs.

    6. Build graphics with User Graphics Tool.

    7. Configure User Views and Tailored Summaries.

  4. Install, wire, and power the engine. Refer to the appropriate installation guide for the engine model you are installing. (See Related documentation.)

  5. Prepare the engine for connectivity to the Metasys system network. See Detailed Procedures for instructions on how to connect an engine in various network scenarios and to set up some basic engine parameters.

  6. If the engine is not the designated Site Director, demote it from Site Director status. See Designating an SNE as a child of a Site Director.

  7. Change the engine's computer name value and assign an IP address, if necessary. See Computer name. The engine is now ready to receive an archive database download from the SCT.

  8. Use the Manage Archive Wizard in SCT to download the database to the engine. Refer to the Metasys SCT Help (LIT-12011964).

  9. If there are only engines on the site, designate one of the engines as the Site Director. If the site has an ADS or ADX server, that server is automatically designated as the Site Director. Refer to the ADS/ADX Commissioning Guide (LIT-1201645).

  10. Using SCT, create a backup of the archive database, which includes the security database. Refer to the Metasys SCT Help (LIT-12011964).

  11. Log on the SNE to verify operation.