Implementation engineer track

Build the project's spatial hierarchy from organization down to space, so that every piece of equipment can later be assigned to a specific space, and reports, maps, and dashboards can rely on this same structure.

Define a device from the catalog or as a custom device, assign it to a space and group, and complete the basic connection settings.

Enable SNMP monitoring on a device, test the connection, and turn the required OIDs into data points with Walk.

Learn the Modbus TCP and RTU settings in the device form, and understand register logic, function codes, and byte order well enough to correctly set up meters, drives, and panels.

Know where every other protocol is configured, what information you need to get from the equipment team for it, and what its support status is in the current version.

Read the 16-digit ENID structure, define a control variable (ACV), and correctly set its formula, scale, acceptable range, alert limits, and statuses.

Use the protocol tester to get a real reading from an SNMP or Modbus TCP device, and use the device simulator to exercise the dashboard and alerts with sample data, without real equipment.

Build a 2D dashboard, place elements from the palette onto the canvas, adjust their appearance and layout, and save, duplicate, export, or delete the dashboard.

Bind dashboard elements to data points or a device, color them from the point's status, aggregate several points, and build a command button with password confirmation.

Build a 3D dashboard, place and adjust objects from the library, bind them to data and commands, and configure and save the scene's lighting, camera, and background.

Define a threshold limit with hysteresis for a continuous quantity, know exactly at what value an alert is raised and at what value it clears, and send a notification through a channel that actually works in practice.

Build an "if ... then ..." rule in the visual editor, test it with no effect on equipment, and know which mechanism to use for scheduling recurring work.

Tell apart the logic engine's three execution mechanisms, build a scheduled script, a state machine, and a scenario, and, before relying on them, check the logic in the test lab against simulated data.

Define a twin type for a complex piece of equipment (points, events, protocol mapping, and source), test it in the simulator, and publish its version.

Learn the menu map of the enterprise modules and, for energy, UPS, assets, and access control, know what each page shows and how to use it for monitoring.