Skip to content

Integrated solutions · Engineering + Software

Engineering and software, delivered as one system.

The equipment, controls and wiring on site, and the software that turns their signals into decisions. One team designs both sides and owns every interface between them.

Cutaway of a plant room connected to a software layerA sectioned pump room: a pump skid with insulated discharge pipework, a pressure transmitter PT-101 on the discharge line, a wall-mounted control panel MCC-01, a cable tray and a wall-mounted gateway GW-01. An amber signal cable runs from the transmitter through the tray to the panel and gateway, then leaves the building through a wall gland and continues to a software layer outside, where a monitoring dashboard, a mobile alert and a maintenance work order stand side by side.ENGINEERING · ON SITESOFTWARE · HOSTED SERVICES AND APPSMCC-01GW-01Plant room 01 · PumpsLIVEP-101 discharge pressure4.2barPT-101Motor 11.8 A · Run 6 hWO-0142OPENInspect strainerAssetP-101SourceAlert 10:42DueThis week10:42ALERTPT-101 high4.9 barAcknowledge2CONTROL PANEL MCC-011PT-101 · PRESSURE3GATEWAY GW-014WALL GLAND · UPLINK1PUMP SKID P-1015DASHBOARD · ALERT · WORK ORDER
Illustrative plant room, values for illustration only · not a client installation
  1. 01Equipment and sensors. Pump P-101 with pressure transmitter PT-101 on the discharge line.
  2. 02Control panel. MCC-01 runs the pump, interlocks and alarms.
  3. 03Gateway. GW-01 collects panel data on the wall beside it.
  4. 04Uplink. One secured connection leaves the building.
  5. 05Software. A dashboard, a mobile alert and a maintenance work order.

The layer model

Four layers. Three interfaces. One owner for all of them.

Every integrated system we design is split into the same four layers. Each layer has a lead practice, and every boundary between layers is written down before anything is built: signal names, units, protocols and what happens when data stops arriving.

  1. Layer 04

    Software and user interfaces

    Dashboards, mobile alerts, maintenance workflows and reports. Designed around the decision each user has to make, not every value available.

    Lead practice Software & Digital Data & dashboards
  2. Layer 03

    Connectivity, cloud and APIs

    Gateways, secure transport, storage, event rules and integrations with business systems. The layer where both practices work side by side.

    Lead practice Shared Gateway hardware and firmware by Engineering; services and APIs by Software.
  3. Layer 02

    Control logic

    PLC programs, interlocks, alarms and local operator screens, traced to a written functional description. Safety stays local and never depends on the cloud.

    Lead practice Engineering Automation & control
  4. Layer 01

    Sensors, equipment and power

    Electrical supply, instruments, motors, meters and embedded devices, selected, wired and documented so the data above them can be trusted.

    Lead practice Engineering Electrical engineering

Where the practices meet

Integrated solutions for real-world applications.

Explore how our engineering and software capabilities can be combined to support industrial operations, energy management, intelligent infrastructure and connected technologies.

  • Internal demonstration
  • Capability concept
  • 01 / EquipmentInternal demonstration

    Connected equipment

    Pumps, compressors or fans reporting status, alarms and run hours to a web dashboard, with alerts routed to the person who acts on them.

    Engineering
    Sensors, panel signals, gateway
    Software
    API, event rules, dashboard, alerts
    Read the demonstration
  • 02 / EnergyCapability concept

    Energy monitoring

    Metering at distribution boards, with consumption shown by area and unusual use flagged for review.

    Engineering
    Meter selection, CT placement, wiring
    Software
    Data collection, reports, dashboards
  • 03 / BuildingsCapability concept

    Building automation interfaces

    Operator views and integrations built on top of existing building controls, without replacing them.

    Engineering
    Point lists, controller interfaces
    Software
    Operator screens, integrations
  • 04 / ProductsCapability concept

    Embedded products

    Connected devices designed with their firmware, configuration app and cloud back end as one product.

    Engineering
    Electronics, PCB, firmware
    Software
    Companion app, device management
    See the controller concept
  • 05 / OperationsCapability concept

    Remote operations

    Secure remote views of plant status, with clear limits on what can and cannot be changed from a distance.

    Engineering
    Control architecture, local and remote interlocks
    Software
    Secure access, audit trail
  • 06 / TestingCapability concept

    Test automation

    Test rigs that run equipment through a defined sequence, capture the results and produce the report.

    Engineering
    Test fixtures, instrumentation
    Software
    Sequencer, results database, report
  • How to read the labels

    Internal demonstration. Working solutions developed and tested.

    Capability concept. Proposed solutions and technical approaches.

Who leads what

One coordinated approach. Complementary expertise.

Our engineering and software teams work together on multidisciplinary projects. By coordinating design, interfaces, implementation and testing, we aim to deliver solutions with clear responsibilities, consistent documentation and reliable system performance.

Engineering Solutions leads

  • Electrical design, protection and drawings
  • Instruments, sensors and field wiring
  • Control logic, interlocks and local HMI
  • Embedded hardware and gateway firmware
Engineering Solutions

Coordinated together

  • System interfaces and data definitions
  • Integrated testing
  • Handover and support documentation

Software & Digital leads

  • Data model, storage and APIs
  • Dashboards, alerts and reports
  • Integrations with business systems
  • User access, hosting and updates
Software & Digital Solutions

One delivery thread

  1. 01Map equipment, users and system boundaries
  2. 02Define signals, APIs and responsibilities
  3. 03Prototype the critical interactions
  4. 04Implement and verify each layer
  5. 05Test the complete operational journey

Start an integrated project

Bring the whole system into one conversation.

Tell us about the equipment, the data you need from it and who has to act on it. We will come back with the layers we would design, the interfaces to agree and the questions to answer first.

Discuss the architecture See projects and demonstrations

Integrated inquiries are reviewed by both practice leads.