For controls engineers who program the OBELISK: build strategies block-by-block in the browser wiresheet with live values, bind discovered I/O, organise a site with folders and naming that lasts, engineer honestly for dead sensors with null, master point paths and pickers, capture the semantic model that pays at handover, engineer alarms, histories and schedules with discipline, and package proven work as Program Catalogue templates with the .sgo backup as the engineering artefact. Everything happens in a web browser — nothing to install.
For systems integrators and head-end engineers putting an OBELISK under a BACnet supervisor or Modbus head-end: what the B-BC profile really implements (read Protocol_Services_Supported first), exposing points with semantics-driven mappings and units, reading efficiently with RPM and COV, archiving TrendLogs with ReadRange that resumes by sequence, routing alarms and acknowledging them so acks attribute, DCC/ReinitializeDevice etiquette and the time-master decision, full backup/restore over BACnet from the OWS, and BACnet/SC, SNMP monitoring and the IT security conversation.
For installing technicians: mount the controller and STACK I/O, get the three ethernet ports right, commission point-by-point with timed overrides and printed evidence, generate wiring diagrams and the Commissioning Schedule, run Modbus RTU/ASCII or BACnet MS/TP on COM1/COM2 (one protocol per port), stand up the BACnet server, poll remote BACnet/IP and Modbus TCP devices with the fieldbus client, and hand over with backups you can trust — downloaded, pushed off-device by SFTP, and the signed change-over SD card fitted in the running controller. Everything happens in a web browser — nothing to install.
For building operators: read the controller's health at a glance, understand live values, handle alarms properly, change occupancy schedules, answer comfort complaints with trend data, and keep the controller secure. Everything happens in a web browser — nothing to install.