REGISTRIEREN

Jobbörse

Finde Jobs in deiner Nähe – ob vor Ort, hybrid oder remote.
  • Ähnliche Jobs zu: Brand Building Purchases - Working Student
XX
Senior Integration Engineer - Building Systems & DataOKTO Integrated Services • London, England, United Kingdom
Jetzt Bewerben
XX

Senior Integration Engineer - Building Systems & Data

OKTO Integrated Services
  • GB
    London, England, United Kingdom
  • GB
    London, England, United Kingdom
Jetzt Bewerben

Über

*Senior Integration Engineer - Building Systems & Data*
*Location: *Based in either London or Lisburn. Project-based travel between the two — typically a few days at a time, not long-term relocation. Frequent site work on live projects.
*Engagement: *12-month initial contract, renewable (B2B, weekly GBP)
*Day rate: *£800 – £900 per day, outside IR35. Travel, accommodation and subsistence covered on site-based work.
*About OKTO:*
OKTO Integrated Services has spent 33 years delivering complex multi-system integration on projects where the technology has to be invisible and the user experience uncompromising - luxury hospitality (Hilton Waldorf Astoria at Admiralty Arch, The Peninsula London), superprime residential (Mayfair Park Residences, 80 Holland Park, Forbes House) and high-profile corporate clients (Manchester United, Allstate). We are now extending this discipline into critical infrastructure and building two of our own products: CIDE-OS (Critical Infrastructure Digital Estate Operating System) and Strata Shell, the operational intelligence interface that runs on live building data. Strata Shell was demonstrated at IHEEM running live hospital operational data. This role sits inside that direction of travel.
*The role:*
This is an integration engineer role with the centre of gravity on data. The buildings already exist; the BMS, SCADA, lighting, power and life-safety systems are already there. Your job is to make them speak - cleanly, semantically, and in a form that Strata Shell and CIDE-OS can use.
You take raw BACnet, Modbus, OPC UA, KNX and proprietary API data from heterogeneous building systems, normalise it through an MQTT layer, tag it against Brick Schema, surface it as a queryable graph, and pump telemetry into Azure Data Explorer where Strata Shell and Grafana render it for the people who run the estate. Live healthcare estate work is the largest current example of this discipline in practice: hundreds of thousands of points across multiple hospitals, brought online and made operationally useful in a 24/7 command centre.
You will be hands-on with both halves of this. The data layer is where most of your time goes - building MQTT brokers, designing topic structures, modelling Brick ontologies, writing the gateways that translate between protocols, and exposing the resulting graph through APIs. But you are also frequently on site - standing in front of the BMS head-end, talking to the controls engineers, validating that the data coming through actually reflects what the kit is doing, and fixing it when it does not.
This is not a data scientist role. It is not a pure data engineer role. It is an integration engineer role for someone who has spent serious time on the field side and has now moved into the data side - and still does both.
You will rotate across our active pipeline: healthcare digital estates, the Hilton Waldorf Astoria at Admiralty Arch, superprime residential, and corporate critical-environment work. The common thread is technical complexity - we are brought in for the work others find too difficult.
*What you will do: *
*Data integration & digitisation*
* *Translate field-layer protocols into MQTT* - building the gateways that take BACnet/IP, Modbus TCP/RTU, OPC UA, KNX, SNMP and proprietary REST APIs and publish normalised, tagged payloads to the broker.
* *Build and operate MQTT brokers* at building and estate scale - topic hierarchy, QoS, retained messages, persistent sessions, TLS, ACLs, and bridging into Azure or other cloud platforms.
* *Model buildings in Brick Schema* - class hierarchies, relationships, equipment groupings, point types. Apply Brick, Haystack, RealEstateCore or ASHRAE 223P as the project demands. Make the estate queryable, not just controllable.
* *Make the building data graph queryable* - SPARQL/RDF or equivalent, with the goal that any operator question ("which AHUs in Ward 4 are in fault?") returns a useful answer in one query.
* *Pump telemetry into Azure Data Explorer* or comparable time-series stores. Author the KQL (or equivalent) that Strata Shell and Grafana use to render operational state.
* *Integrate via direct API* - Tridium Niagara REST, Schneider EcoStruxure connectors, vendor cloud APIs, webhooks and GraphQL endpoints - where direct protocol access is not the right route.
* *Establish naming and tagging conventions* that survive twenty years of facilities turnover. The point names and ontology classes you choose today will be the column headers on someone’s dashboard in 2046.
* *Stand up integration test harnesses* - simulators, fault injection, end-to-end soak tests. Integration that has not been deliberately broken in test will break in production.
*Site & field integration:*
* *Work on site, frequently* - in plant rooms, at BMS head-ends, alongside commissioning engineers. You are not a remote data engineer. You are the person who validates that the byte coming out of the BACnet device actually matches the temperature on the gauge.
* *Integrate with existing BMS platforms* - Schneider EcoStruxure Building Operation, Tridium Niagara N4, Trend, Distech, WAGO and others - as data sources for the platform layer. You consume these systems; you do not need to be the vendor engineer for any one of them, but you must speak their language fluently.
* *Integrate critical power and plant* - generators, UPS, chillers, pumps, AHUs, FCUs - over their native protocols (Modbus, BACnet, SNMP, J1939) and surface their state into the platform.
* *Hold credible conversations* with the BMS Project Engineer, the M&E consultant, the lighting designer, the client’s IT team and the client’s facilities manager. You translate between them and the platform team.
* *Design and deploy edge gateways* - Mapped Universal Gateway, Tridium JACE, custom Linux-based gateways, or whatever the project demands. You decide what runs at the edge versus what runs in the cloud.
*Network, IT & security:*
* *Treat OT cybersecurity as a first-class concern* - hardening defaults, secrets handling, least-privilege access, certificate management and audit logging across the OT stack.
* *Navigate enterprise IT* alongside the client’s IT team - firewall rules, port allocations, certificate handling, VLAN segmentation and secure OT/IT segregation.
* *Design building networks to OT-grade standards* - IP addressing, switch configuration, wireless sensor integration.
*What you will bring:*
*Essential:*
* Proven track record building data integration pipelines from field-layer building systems into a platform layer - end to end, in production, on real sites.
* Hands-on experience with Brick Schema or equivalent semantic ontologies (Haystack, RealEstateCore, ASHRAE 223P) - class modelling, relationships, point typing in a real project.
* Deep practical experience with MQTT - broker selection and deployment, topic structure, QoS, security, bridging, payload design - not just "I have heard of it".
* Working knowledge of graph data - SPARQL, RDF, or comparable graph query patterns. You can model a building as a graph and query it.
* Hands-on with time-series telemetry - Azure Data Explorer / KQL preferred; InfluxDB, TimescaleDB or comparable accepted. Authoring Grafana dashboards against this data.
* Fluent in the building protocols: BACnet/IP, Modbus TCP/RTU and OPC UA are the everyday floor. KNX, DALI, M-Bus, DMX, SNMP and J1939 as the project demands.
* Practical experience with API-led integration - REST, GraphQL, webhooks, middleware - against vendor platforms (Tridium, EcoStruxure, vendor cloud APIs).
* Comfortable on site - in plant rooms, at BMS head-ends, validating data against physical kit. This is not an office role.
* Strong programming foundation - Python or C# fluency for data pipelines, gateway logic, and tooling. Bonus for Lua, Node-RED, or JavaScript.
* Working knowledge of at least one major BMS platform as a data source - Schneider EcoStruxure Building Operation, Tridium Niagara N4, Trend, Distech or comparable.
* Cloud competence - Azure preferred (given OKTO’s stack), AWS or GCP accepted. IoT services, time-series ingest, identity and networking.
* Track record on regulated environments - at least one of NHS, healthcare, pharma, data centre, defence or Crown Estate.
* Practical OT/IT segregation experience - VLANs, firewall traversal, certificate handling, secure gateway deployment.
* Right to work in the UK and willingness to clear background checks for healthcare, Crown Estate and regulated client sites as required.
*Highly desirable:*
* Direct experience with Mapped Universal Gateway, Willow, PassiveLogic, KGS Buildings or comparable independent data-layer platforms.
* Azure Digital Twins or comparable digital-twin platform experience.
* Open-source contribution to Brick Schema, Project Haystack, or comparable ontology projects.
* Niagara N4 developer-level experience - not just configuration but writing modules and consuming the Niagara API.
* Specific MQTT broker experience - HiveMQ, EMQX, Mosquitto, AWS IoT Core, or Azure IoT Hub at building or estate scale.
* Experience integrating standby generators and UPS systems into monitoring stacks - Deep Sea / ComAp / Woodward gensets and APC / Eaton / Riello / Vertiv UPS.
* AVEVA System Platform, Inductive Automation Ignition or comparable industrial SCADA platforms used as data sources.
* AI-assisted development workflows (Copilot, Claude Code) for accelerating gateway logic, documentation and KQL authoring.
* BSc/MSc in Software, Electrical, Control or Building Services Engineering.
*Who you are:*
The technical bar above is the easy part to write down. What actually matters to us:
* *You take pride in your work.* The graph model you build today should still make sense when someone else queries it in five years. The gateway you commission should not need to be touched again unless the building changes.
* *You are self-driven to get it right.* Not right enough to pass acceptance - right. You chase the loose end nobody asked you to chase, because you know it will surface in production six months later if you do not.
* *You stand behind your work.* If the data stops flowing at 2am during a shift change, you want the call. You would rather know.
* *You put yourself out for the customer.* Critical infrastructure does not respect office hours. When a client has a deadline or a problem, you find a way - without needing to be asked twice.
* *You communicate honestly.* When a programme is slipping, when an ontology will not model what the client is asking for, when you do not know the answer - you say so early, not late. Surprises are expensive; honesty is not.
* *You sweat the details.* Tag names, class hierarchies, broker topics, point IDs, audit logs, version control. The boring things that decide whether an estate is queryable in twenty years or a forensic exercise.
* *You think in systems, not just devices.* You see the AHU, but you also see the data point, the Brick class it maps to, the alarm rule it triggers, and the operator who reads the dashboard in three years.
* *You bridge the field and the platform.* Most of what you do happens at a laptop, but you are equally at home in a plant room. You can talk to a commissioning engineer in their language and a platform developer in theirs - because you have done both.
*What we offer:*
* A senior seat at the heart of OKTO’s platform direction - Strata Shell, CIDE-OS, healthcare digital estates - not adjacent to it.
* Frequent on-site work on flagship projects - the Hilton Waldorf Astoria at Admiralty Arch, healthcare estate work, superprime residential, and corporate critical-environment work.
* Above-market compensation - we recruit on quality, not on rate-card.
* Travel, accommodation and subsistence fully covered on site-based contract work.
* Direct access to OKTO’s technical leadership - no agency layer between you and the engineering decisions.
* A small, technically serious team where the standard is quiet precision.
Pay: £800.00-£900.00 per day
Work authorisation:
* United Kingdom (required)
Work Location: On the road
  • London, England, United Kingdom

Sprachkenntnisse

  • English
Hinweis für Nutzer

Dieses Stellenangebot stammt von einer Partnerplattform von TieTalent. Klick auf „Jetzt Bewerben”, um deine Bewerbung direkt auf deren Website einzureichen.