Integration & Communication

Cactus Communication Server (Cactus CS)

One of the challenges – and also one of the big opportunities – is to gain insight from the great mixture of systems used for planning, operation and maintenance.

How are the different sub-systems used? What are their capacity utilisation and maintenance needs, and how can the system be optimised? Can the infrastructure owners obtain synergies by linking the different sub-systems together? How can we create the conditions to enable the greatest traffic precision, the optimum traffic density and the most appropriate customer communication?


Make the systems smarter

Cactus CS lays the foundations for making all systems smart whatever their age or system type. Cactus CS uses a common descriptive model for all connected systems; regardless of the type of sub-system, traffic type or track object to be connected, Cactus CS creates common interfaces with standardised and open protocols.


Other benefits of Cactus CS

Cactus CS is a system with world-leading performance and system architecture. This means that the aspects of the system to do with scalability, automated testing, plug-and-play, configuration, flexibility, robustness and availability are extremely well developed.

  • Easy to reconfigure when modernising existing systems or introducing new systems and new infrastructure.
  • Scalable – suitable for both regional and national systems.
  • Meets very strict demands for robustness, performance and availability.



How does the system meet the requirements for continuous operation?

The system can be configured for redundancy, distributed redundancy, automatic load-balancing and geographical distribution according to the customer’s wishes. All in all, the system meets extremely demanding requirements:

  • The system is designed for absolute reliability and continuous operation, and all maintenance can be carried out with the system in use.
  • If the system is run on n servers, it will be well-defined how it will run on n-1 or n-2 servers (for a national traffic management system, n could typically be between 15 and 40).
  • The system can be configured for the desired behaviour in a disaster scenario (moving all active communication to a new data centre, distributing communication across all servers).