35,000 users, several million system requests per day, and more than 400,000 test results annually. Managing automotive testing at this scale requires software capable of far more than planning and documenting individual tests.
At major automotive manufacturers, development and testing activities are spread across numerous locations, departments, and external partners. Test benches continuously generate measurement data, vehicles are tested under a wide range of conditions, and engineers access information from a variety of specialized systems.
This creates enormous volumes of data and complex dependencies. Even months later, a test result must still be clearly traceable to a particular vehicle, its configuration, the test procedure used, and the associated measurement data. At the same time, thousands of users need access to a common information base without compromising security, data consistency, or system performance.
Stuttgart-based Softwarehelden has designed its Cluu Automotive Test Management platform to address these requirements. Its architecture is built to manage large data volumes, connect existing IT systems, and support complex engineering processes across organizational boundaries.
The best way to assess whether a software platform is suitable for enterprise-wide deployment is to examine how it performs in production.
Cluu is already used by more than 35,000 users. Its production environments process several million requests every day and support the management of more than 400,000 test results annually.
But the number of users tells only part of the story. In large engineering organizations, IT landscapes have evolved over decades. Vehicle data, test orders, test bench schedules, measurement results, and defect reports are often stored in different databases and applications.
Cluu can bring these environments together. Individual installations have integrated up to 250 databases, while the platform manages more than 5,300 terabytes of data across referenced environments.
Cluu also operates in enterprise environments requiring continuous 24/7 operation. These figures reflect experience from different production installations rather than guaranteed performance for any single system configuration.
Much of Cluu's ability to support large enterprise environments comes from its underlying technical architecture.
The platform uses a three-tier architecture that separates the user interface, business logic, and physical data storage. At its center is the Cluu Backbone, which handles business rules, access control, and the relationships between information from different systems.
The backend architecture is based on independent .NET services. Existing applications can be integrated through REST, OData v4, and SOAP interfaces, along with SDK and CLI components.
Of particular interest to large engineering organizations is Cluu's virtual, graph-based data architecture. It allows information from different sources to be connected through meaningful relationships without requiring all data to be transferred into a new central database.
This is especially relevant in vehicle development. One system collects measurement data from a test bench, another manages vehicle configurations, and a third records defects. Cluu can connect this information through its underlying engineering context.
Engineers can therefore trace which vehicle and software configuration was tested, which measurement data was generated, and which issues resulted from the test. Existing specialist applications remain in place and continue performing their original functions.
The demands placed on the architecture become particularly apparent when managing measurement data.
Modern vehicle testing generates substantial volumes of information. High-resolution sensors, extensive ECU communication, and automated test benches produce files that must remain accessible and clearly identifiable over long periods.
Cluu addresses this challenge by managing the logical identity of a file independently of its physical storage location.
Whether measurement data resides on a local file server, a NAS system, object storage, or in the cloud does not need to be the engineer's primary concern. Cluu manages the associated metadata and maintains the relationship between the files and the relevant testing activities.
Automated data ingestion, metadata extraction, and version management support this process.
For development engineers, this simplifies everyday work. Rather than searching for a measurement file using its filename or storage path, they can locate relevant data based on the vehicle, test order, configuration, or other test information.
The architecture also makes changes to storage infrastructure easier to manage. Data can be migrated between supported storage technologies without fundamentally changing how every connected application accesses it.
As organizations grow, managing users, permissions, and system access becomes increasingly complex.
A test bench operator needs different information from a development engineer. External service providers may only be authorized to access specific projects. At the same time, changes to test data and approval decisions must remain traceable.
Cluu supports Single Sign-On, integration with Active Directory and Microsoft Entra ID, and rule-based access control. Multi-tenancy and multilingual user interfaces make it easier to deploy the platform across internationally distributed organizations.
The architecture also addresses operational requirements. Structured logging and OpenTelemetry-based monitoring allow IT teams to observe system health and technical processes. Depending on the organization's IT strategy, Cluu can run on customer-managed infrastructure or in suitable cloud environments.
The actual performance and availability of a specific installation naturally depend on its sizing, infrastructure, and operating model.
Digitizing the processes of a single testing department can often be accomplished with a relatively straightforward application. The situation is quite different at a global automotive manufacturer.
Here, numerous test laboratories, proving grounds, engineering departments, and external partners need access to information originating from different systems. At the same time, data and results must remain traceable throughout the development process.
Cluu is designed to support this collaboration. The platform connects the systems involved, manages relationships between their data, and provides shared capabilities for access control, search, and workflow management.
Softwarehelden's customer references demonstrate that this approach is already being used in major automotive engineering organizations. Its automotive customers include Volkswagen, Porsche, Audi, and Bentley.
This changes the role of test management in vehicle development. The software is no longer used solely to organize test orders and document results. It provides the connections between requirements, vehicle configurations, measurement data, and engineering decisions.
The larger an engineering organization becomes, the more valuable this common information base is. With thousands of employees and millions of system requests, the real challenge is no longer simply digitizing individual tests. It is making their results reliably accessible and usable across locations, departments, and systems.
We're happy to tell you more.
Let's have a chat together.
Experience Cluu in a free demo – via video call or on-site, tailored to your needs. If you're interested, we’re happy to explore development opportunities together.
Work with two of our developers for a week, get your own Cluu server (cloud or on-premises), and test all products for a full month. Together with our experienced team, we’ll bring the Cluu platform to life – tailored to your specific context.
9.600,- €
Request now