Preparing for Installation

About KMC Commander Gateways

The KMC Commander® IoT (Internet of Things) gateway and Automation Platform consists of an IoT gateway with embedded software as well as a secure connection to the mobile accessible Cloud. (The gateway hardware is also known as a “box.”)

Reviewing the Pre-Installation Checklists and Minimum Requirements is crucial for successful installation.

Recommended Installation Sequence

The recommended installation and configuration sequence is:

  1. Complete initial login and registration (in the installer’s office or staging area) for login and license confirmation as well as software updates. (See Connecting Wi-Fi and Making Initial Login.)

  2. Permanently install the gateway hardware on site. (See On-Site Installation.)

    Note: Although all steps can be done on-site, performing initial login before on-site installation is highly recommended to provide confirmation that the installer can log in at the job site, that the licensing is correct, and that all software updates have been completed.

  3. Complete the following minimum configuration processes, which must be performed on site (or performed as local via VPN):

  4. Configure dashboards, schedules, trends, and alarms.

    Note: These may be configured from the Cloud after the on-site installation.

Minimum Requirements

Installation requires the following minimum hardware and connections:

  • Laptop, tablet, or PC with wireless (Wi-Fi) connection and a Google Chrome or Safari browser

  • Internet connection (via Ethernet cable)

  • Power supply (see Connecting Power)

  • Mounting adapter (see Mounting the Gateway)

Information required to complete installation includes:

  • Customer license information

  • Network topology and a list of all points of interest in all controllers to be monitored

  • Relevant open outbound ports and network addresses and information from the building’s IT department

    Note: See the KMC Commander IT/Network Information Technical Bulletin. (See Accessing Other Documents.)

  • See also Pre-Installation Checklists

Pre-Installation Checklists

The following checklists describe what system integrators should do to prepare to install a KMC Commander system.

Crucial Information

With the Customer and IT Department

For a successful KMC Commander installation, support from the building’s IT department is crucial. The IT department must open the required outbound ports and provide the network information needed for the customer to connect to the Internet. See the KMC Commander IT/Network Information Technical Bulletin. (See Accessing Other Documents.)

Review the above Crucial Information with the end customer and IT department representatives, noting:

  • KMC Commander initiates all messaging with Cloud services.

  • Ports and services used by KMC Commander are shown in the KMC Commander IT/Network Information Technical Bulletin to use for outbound rules.

  • No firewall inbound rules are needed.

Determine the network topology for Internet access, asking these questions:

  • Are there existing outbound policies?:

    • If so, rules should be added to allow outbound traffic on specified ports. (See the technical bulletin above.)

    • Alternately, the cellular KMC Commander model option (Dell only) could be used.

  • What method is needed for Internet access?:

    • If Ethernet/LAN, do they want KMC Commander to have static or dynamic IP addresses?

      • If static, what are the gateway, subnet mask, and DNS?

    • If Wi-Fi (as a client), what are the SSID and credentials?

    • If cellular, which carrier will be used? Will there be good signal strength inside the building in the installation location?

With the Customer

Determine network topology for BACnet devices:

  • Are there BACnet MS/TP devices?

    • If so, a BACnet router (BAC-5051E) will be needed to connect to the Ethernet network.

  • Are there BACnet IP devices on the same subnet as KMC Commander?

  • Is the BACnet network separate from the one with Internet access?:

    • If so, using a static (rather than dynamic) IP address is recommended for the Ethernet port on the KMC Commander IoT gateway that will communicate with BACnet.

      • If static, what is the network subnet mask, gateway, and IP address?

Determine project users and account permissions:

  • Who are your technicians who will be involved in the install and/or future support? Put them in the Cloud project server.

  • Who are the users for the customer? Put (at least) the administrators in the Cloud project server. (Administrators can add other users later.)

Get Ready for Installation on the Job Site

Determine readiness for remote access by KMC technical support if help is needed:

  • Note the Service Tag number for the KMC Commander IoT gateway when it is received.

  • Is TeamViewer or some other remote method available?

Review the KMC Commander installation videos on the KMC Commander YouTube channel to become familiar with the basic installation process.

Written details of the installation process are found in these sections:

Note also Troubleshooting for if you need it.

Support Documents and Resources

Note: Documents, product design, and product specifications are subject to change without notice.

See Accessing Other Documents for details on accessing KMC Commander quick setup guides, data sheets, application guides, bulletins, and other important files.

For customer (Cloud) project data and control: app.kmccommander.com.

For customer administration: central.kmccontrols.com. (See the KMC Commander (Cloud) System Administration Application Guide.)

For background information, see the KMC Commander Solutions page and the KMC Commander playlist on the KMC Controls channel on YouTube.

For information about API (Application Programming Interface) integration, see api.kmccommander.com and API Integration.

See also Software Tools for network and installation troubleshooting.