Cactus Rail - Behind the scenes

Behind the scenes

The proven technology and the new architecture.

The volume of information in today’s management systems is increasing and placing greater demands on the operator. Well-designed control rooms and command centres therefore contribute to safer operation, more satisfied staff and a better and more attractive working environment.

A big advantage is that Cactus CCS uses a common model for all the underlying components, i.e. inde­pendent of the type of infrastructure objects used.

Instead, we handle them the same way


Some of the characteristics
  • Protocols between Cactus CCS and TMS or other system are standard – Cactus CCS can be implemented independent of system type or vendor.
  • Easy to reconfigure when introducing new protocols and new infrastructure.
  • Scalable – suitable for both regional and national facilities.
  • Manages the requirements of redundancy and availability.


The power of open source

Acknowledged open-source software packages are developed by countless developers all over the world – continuously improving security and new features and enchantments. Compare that with a software package created by a handful of developers.

We utilize an open-source software and adapt it to suit our needs. Since the code is open, it’s a matter of modifying it to add the functionality we want – something that cannot be done with proprietary software.

We use acknowledged open-source software and quality is handled in a rigorous process. It can then be used for building real-time data pipelines. It is scalable, fault-tolerant and wicked fast.



The power of microservices

Cactus CCS take advantages from a technology called microservices architecture, i.e. the complete task of Cactus CCS is divided into several dedicated components each with a strong encapsulation.

As opposed to more monolithic design structures, microservices:

  • Larger applications can remain largely unaffected by the failure of a single module.
  • Eliminates long-term commitment to a single technology stack. Dependency concerns will be far lighter than with monolithic designs, and rolling back changes much easier. The less code in play, the more flexibility.
  • Enable update and addition of functionalities while still maintaining high availability.


We call it industrial open source

If we use an open source framework we know that we need to take full responsibility for the framework for the entire product life cycle.

Our choice of technology forms the basis for satisfied customers, better control, effectivefollow-up and more efficient operation. By linking subsystems and getting the maximumbenefit from existing infrastructure, we can see new ways of creating world-class solutions for a smarter railway.