Skip to content
AXXA

Capability 03

Systems Integration

Most system failures happen at the interfaces. That is where we work.

01Introduction

Overview

A system is more than its components. Its behaviour depends on how those components discover each other, exchange data, handle delays and recover from failures. That behaviour has to be designed, not discovered.

We plan and execute integration incrementally, and we treat communication as an architectural concern: explicit data models, deliberate quality-of-service policies, and evidence that the system behaves correctly when the network does not.

02Engineering challenges

The problems we are typically asked to solve.

  1. 01

    Integration as a late, single event

    Subsystems are developed in parallel and meet for the first time near a milestone. Problems pile up exactly when there is least time to fix them.

  2. 02

    Communication that works in the lab

    Middleware is configured with defaults. Under real network conditions, load and node failures, messages are delayed, lost or arrive out of order.

  3. 03

    Quality-of-service nobody designed

    Reliability, durability, deadlines and history depth are set per topic by whoever wrote it. The system's real behaviour is emergent rather than specified.

  4. 04

    Mixed technology stacks

    Legacy protocols, new middleware, cloud services and embedded nodes must all interoperate, usually through ad-hoc bridges.

03Scope

What an engagement can cover.

  • Integration strategy, sequencing and environments from component to system level
  • Communication middleware selection, architecture and configuration
  • DDS system design: topic and type models, QoS policies, discovery and partitioning
  • Eclipse Zenoh for edge-to-cloud and constrained-network communication
  • Bridging between middleware, legacy protocols and services
  • Secure communication: DDS Security, TLS and access control in Zenoh, network segmentation
  • Networked embedded systems: timing, bandwidth and failure behaviour
  • Diagnosis of integration and communication problems in existing systems

04Technical expertise

Technologies and methods in practice.

Middleware
  • DDS (OMG standard)
  • Eclipse Cyclone DDS
  • Eclipse Zenoh
  • Publish/subscribe and request/reply patterns
Data & contracts
  • IDL type design
  • Serialization formats
  • Schema evolution
  • Topic and key design
Networking
  • TCP/IP and UDP multicast
  • Discovery and configuration
  • Bandwidth and latency budgets
Integration
  • Hardware-in-the-loop setups
  • Simulation and emulation
  • Incremental integration plans

05Deliverables

What you receive.

  1. D01

    Integration plan

    Sequenced integration steps, environments and entry criteria, so subsystems meet early and often.

  2. D02

    Communication architecture

    Data model, topic structure and QoS profile per data flow, with the reasoning for each choice.

  3. D03

    Middleware configuration

    Version-controlled, reviewed middleware configuration and deployment profiles.

  4. D04

    Fault-behaviour evidence

    Tests that demonstrate behaviour under packet loss, node restarts and overload, not only the nominal case.

06Related capabilities

Contact

Discuss systems integration for your system.

Describe the system and the challenge. We will tell you honestly whether and how we can help.

Start a conversation