Operate sites and native applications

The customer portal is organised around two questions:

• What is happening at this place? Open a network for the building, yard, venue, or site.
• What is happening on this box? Open an enabled device and use Controls, Status, or Diagnostics.

Native applications add tailored content to those existing places. They do not add a separate product section to the sidenav.

Each customer enters through its vendor-branded portal host.

Today brings current alerts and unavailable devices together before an operator chooses a site or device.

Find the right place

Use the main navigation in this order:

1. Today for work that needs attention now.
2. Networks for a building, yard, venue, plant, or other operating place.
3. Devices for inventory, placement, and one physical unit.
4. Account for your own profile and security.

A network is the customer-facing place where combined application work appears.

Network detail is the shared place page; open its native workplace when the task spans several devices.

Understand Ready and Enabled

An online device that is not yet assigned to a network is Ready. It is in inventory and waiting to be placed. An Enabled device belongs to a network and can take part in native application work at that place. A device that is offline and unassigned is Dormant.

The plan allowance stored by the service is separate from these operator states. Assign a Ready device to the correct network before expecting it in an application workplace.

Use Devices to distinguish inventory waiting for placement from units already enabled at a site.

Use the device tabs

An enabled device can show three tabs:

• Controls contains the vendor-designed Device Class UI and any native application layer for this device.
• Status contains identity, location, presence, and connection quality.
• Diagnostics contains connection tests and permitted recovery actions.

Status answers which unit this is and whether it is connected.

Diagnostics tests the device and its dependencies. It is separate from an industrial gateway recording analysis.

Choose the device or network surface

Native application	On the network	On device Controls
Industrial gateway	Plant attention for this site	Gateway status, I/O mapping, and traffic analysis
HVAC schedules	Building zones and schedules	This controller and its local context
Camera access	Site cameras and checks	This camera and its vendor controls
Remote signage	Venue screens and content health	This screen and its player state
Energy site	Site circuits, board, generator, and solar state	This meter, generator, or solar controller
Paid Wi-Fi	Venue vouchers and sessions	This access point
Grain outload	Yard load tickets, tags, and bay sync	This bay or gateway class UI
Silo monitoring	All silos at the yard	This silo sensor and its level

Industrial gateway

Open the enabled gateway and stay on Controls. The workbench sections are Status, I/O mapping, and Analysis. There is no Plant Protocol Gateways sidenav entry.

The protocol workbench lives on the gateway device beside its vendor class UI.

I/O mapping connects protocol addresses to customer-readable values.

Analysis inspects completed recordings and frames. Device Diagnostics remains the connection-test surface.

HVAC schedules

Open the building from Networks for all zones and schedules. Open one controller for the state and controls of that box.

The network workplace combines zones and schedules for one building.

Device Controls stays scoped to this controller.

Camera access

Use the network workplace for site cameras and checks. Use device Controls for the live or recorded experience supplied by that camera's Device Class.

The site view combines camera roles and the entrance-check workflow.

The device page remains the place for this camera.

Remote signage

Open the venue for all screens, expected content, player state, and exceptions. Open a screen device for that player's controls.

The venue view separates healthy screens from those needing attention.

Device Controls is scoped to this screen player.

Energy site

Use the site workplace for circuits and the optional generator and solar systems. Open one device for the meter or controller that reports those values.

The network view combines the installed energy roles for one site.

Device Controls stays scoped to this meter or controller.

Paid Wi-Fi

Use the venue workplace for vouchers and access sessions. Use device Controls for this access point and its vendor-supplied controls.

The venue view keeps customer access work together.

The device page remains scoped to this access point.

Grain outload

Use the yard workplace for load tickets, tag publication, driver-code sync, and exceptions. The bay and site gateway keep their vendor Device Class UI on Controls.

The yard view combines completed work, exceptions, and site data publication.

Device Controls remains the box-level surface for the bay.

Silo monitoring

Use the yard workplace to compare all silos. Open a sensor device to inspect the level and controls for this silo.

The network view combines the silos that belong to one yard.

Device Controls stays scoped to this silo sensor.

Manage your account

Account language and security do not add product navigation. Open Account for your profile and Security for password and multi-factor authentication.

Account settings belong to the signed-in person.

Security keeps password and multi-factor controls together.

Security changes use a focused modal without adding another navigation destination.

Related

• Customer portal
• Product Applications
• Device Classes
• Networks and tags