Skip to content
{{}}

Field · Systems integration

Protocols and systems integration

BACnet, Modbus, MQTT, oBIX and REST between systems that were never meant to talk. A project here is staffed with project lead and integration and software, and runs through the same five steps as every other field, from a written specification.

Reviewed

Talk to us about a project All fields

Typical jobs

  • Gateways and drivers
  • Point maps that survive a handover
  • Integration audits
  • Data out of a station into a platform

Who is on the project

  • Project lead
  • Integration and software

Projects

  • A station connector API — A write-capable JSON API inside a Niagara station with a fleet dashboard in front of it, under-privileged by design.

The work and notes behind it

The core

The same five steps as every field

  1. 1

    Read

    Get the data off the system as it really is: the protocol, the decoder, the export, the jar. Measured, not taken from the manual.

  2. 2

    Name

    Map it to one data model with your names and tags, so the next system and the next engineer can find it.

  3. 3

    Act

    Write back only where it is meant to: priorities, schedules, commands. Every write is scoped and reversible.

  4. 4

    Show

    Put it in front of the person who needs it: a graphic, a dashboard, an alarm, an agent answer.

  5. 5

    Hand over

    Source, notes and access in your name. Support afterwards if you want it, and nothing that only we can keep alive.

Other fields

{CTA}