Earlier this year, Concurrent Real-Time hosted the first-ever Real-Time Summit, bringing together engineers, simulation specialists, and technical leaders from across the aerospace, defense, and high-performance computing industries.

Held in Fort Lauderdale, the multi-day event was designed as a forum for deep technical discussion, collaboration, and direct engagement between customers and the engineering teams behind Concurrent Real-Time’s software and systems.

Unlike traditional conferences, the Real-Time Summit focused on creating an environment where engineers could openly discuss real-world challenges, share insights from their own projects, and explore emerging technologies shaping the future of real-time systems.

Throughout the summit, attendees participated in a mix of technical sessions, workshops, and product discussions that explored topics such as deterministic Linux performance, FPGA-enabled simulation platforms, and advanced debugging techniques.

One of the most valuable aspects of the event was the opportunity for engineers to speak directly with the developers and system architects responsible for the technologies they use in their own environments.

These conversations provided valuable insight into how real-time systems are being deployed today from simulation labs and hardware-in-the-loop environments to mission-critical aerospace applications.

Hands-on workshops proved to be one of the most popular elements of the summit. These sessions allowed attendees to work directly with Concurrent Real-Time tools and hardware while discussing best practices with both peers and the internal engineering team.

Topics covered included:

  • Real-time Linux system tuning and performance optimization
  • Integrating FPGA technology into simulation workflows
  • Debugging complex real-time environments
  • Building scalable simulation architectures

For many attendees, these interactive sessions provided an opportunity to explore new approaches and tools that could improve their own development environments.

Common themes included:

  • Managing increasing system complexity
  • Ensuring deterministic performance in demanding environments
  • Integrating simulation tools with evolving hardware architectures
  • Accelerating development timelines while maintaining reliability
  • Accelerating development timelines while maintaining reliability

These conversations not only highlighted the technical challenges engineers are solving today but also helped inform the direction of future product development.

The overwhelmingly positive response from attendees confirmed the value of creating a dedicated space for engineers and technical leaders to connect, collaborate, and exchange ideas.

The Real-Time Summit is planned to become an annual event, continuing to bring together the real-time systems community to explore emerging technologies, share lessons learned, and shape the future of deterministic computing.

Related Articles

  • Diagram showing software staying the same while hardware changes: Guest OS + Application on RedHawk KVM-RT Host, with Hardware Gen 1 retired, Gen 2 in production, and Gen 3 planned refresh.

    Preserving Legacy Real-Time Applications Through Virtualization

    Preserving Legacy Real-Time Applications Through Virtualization Real-time applications often remain in service much longer than the hardware on which they were originally developed. Test systems, industrial controls, simulation environments, and data-acquisition platforms…

    Read more

  • Diagram comparing native RedHawk Linux (left) and RedHawk KVM-RT virtualization (right) with application layer and real-time workload on both sides.

    Native Real-Time Linux vs. Real-Time Virtualization: Which Architecture Fits Your Application?

    Native Real-Time Linux vs. Real-Time Virtualization: Which Architecture Fits Your Application? Virtualization is now common in enterprise computing, but timing-sensitive systems introduce requirements that conventional IT workloads do not share. An application may…

    Read more

  • Diagram of NUMA placement: keep Cores, Memory, and PCIe device in one node (local placement). Cross-node placement is discouraged (Node 0 and Node 1).

    How CPU Shielding, NUMA, and Interrupt Affinity Affect Real-Time Virtual Machines

    How CPU Shielding, NUMA, and Interrupt Affinity Affect Real-Time Virtual Machines Running a real-time operating system inside a virtual machine does not automatically create a deterministic environment. The virtual machine still depends…

    Read more