Rail Vehicle Control Software Configuration via Switching Parameters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for modifying rail vehicle control software is time-consuming, personnel-intensive, and costly, requiring significant redevelopment, testing, and approval for each customer-specific modification.
Innovation Solution
A method that allows for the activation and deactivation of optional software functions in rail vehicles, which can be configured to meet customer-specific requirements without requiring extensive redevelopment or testing, by using switching parameters that can be set and transmitted securely.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customer-specific software modifications are implemented through traditional redevelopment and testing procedures, then software functionality can be adapted to meet customer requirements, but the process becomes time-consuming, personnel-intensive, and cost-intensive
Solution Approach 1:
The patent applies preliminary action by pre-defining a comprehensive set of optional functions and switching parameters during the software development phase. These optional functions are prepared in advance with their activation/deactivation parameters, so that when a customer needs customization, the software can be quickly configured by simply activating or deactivating pre-existing functions rather than requiring redevelopment and testing of new functionality.
Solution Approach 2:
The patent utilizes parameter changes by introducing switching parameters that can be modified to activate or deactivate optional functions. Instead of modifying the core software code for each customer requirement, the system changes parameter values (switching parameters) to enable different functional configurations. This allows rapid adaptation to customer needs through parameter modification rather than comprehensive software redevelopment.
2Adaptability or versatility
If traditional software modification methods are used for each customer-specific requirement, then software can be tailored to individual vehicle needs, but extensive testing and approval procedures are required for each modification
Solution Approach 1:
The patent applies preliminary action by pre-validating and approving all optional functions and their combinations during the development phase. The software is delivered with a complete set of pre-tested optional functions that have been validated to work together correctly. This eliminates the need for extensive testing of each individual customization, as the testing has already been performed in advance on the complete set of optional functions.
Solution Approach 2:
The patent implements universality by creating a universal software framework that includes a standardized set of optional functions that can be combined in various ways to meet different customer requirements. Rather than creating separate software versions for different customer needs, the system provides a universal base software with a library of optional functions that can be selectively activated, allowing one software product to serve multiple customer-specific requirements.
3Adaptability or versatility
If software modifications are performed through conventional redevelopment processes, then customer-specific functions can be implemented, but the process requires significant personnel involvement and resources
Solution Approach 1:
The patent applies self-service by enabling customers or their representatives to configure software functions independently through a user-friendly interface. The system provides self-service capabilities that allow users to activate or deactivate optional functions without requiring specialized software development knowledge or personnel. This reduces the personnel involvement needed for software configuration while maintaining full customizability.
Solution Approach 2:
The patent introduces an intermediary layer in the form of a configuration interface or tool that mediates between the user and the complex software system. This intermediary provides a simplified, user-friendly mechanism for configuring optional functions, shielding users from the underlying software complexity. The intermediary translates simple user actions into the appropriate software configuration changes, reducing the perceived and actual complexity of the configuration process.
Data Source
AI summary
A method for configuring control software in a rail vehicle. The control software, which is designed for a multitude of rail vehicles, implements basic functions that are required for the basic operation of the rail vehicles. The control software additionally implements optional functions required to execute client-specific requests. The specifications, combinations and functional sequences of the basic functions and optional functions are tested, validated, and approved before the functions are implemented in the rail vehicles, whereupon the basic functions and optional functions are made available in the rail vehicles. In a selected rail vehicle, at least one optional function is activated or deactivated using a switching parameter that is individually allocated to the optional function. The switching parameter required therefor is established outside the rail vehicle and is then transmitted to the selected rail vehicle.