SWIn – Smart Waggon Inspector

Smart Waggon Inspector (SWIn) is software designed to simplify and digitize incoming railcar inspections at rail sidings. OCR technology can be used to analyze and store the components of a container freight train. The software reads and stores the number of an ISO container in accordance with ISO 6346 and the UIC number of the railcar carrying the container in a freight train. The requirements for using the software are minimal because it can be accessed through a web browser on a standard smartphone or tablet.

The software simplifies the inspector’s work because the results do not need to be documented by hand, and the recognized numbers are stored automatically. Because the software is not a fixed installation, inspectors must still walk along the train and inspect each railcar when using SWIn. However, this ensures that the railcars and loading equipment can still be inspected for obvious defects during the digital incoming railcar inspection.

Learn More About SWIn

The software can record an entire train during the inspection and represent it virtually in the system. Individual railcar symbols provide a graphical representation in the user interface. Users can check at any time which railcars and containers have already been recorded and stored. Automatically recognized railcar or container numbers can be corrected manually if they are incorrect.

SWIn consists of a frontend, the user interface, that can be accessed through any common web browser as described above, and a backend, the database, that can run on Windows and Linux systems. Data is transferred only between the mobile device and the configured backend. Two configurations are available for hosting the backend:

• On-premises hosting: The backend is installed on site or integrated into existing systems. With this approach, the data does not leave the company’s own IT infrastructure.
• Central hosting: A centrally hosted database at Fraunhofer IML is used. The data is transferred to Fraunhofer IML, eliminating the need to configure systems on site. This simplifies installation and maintenance. The data is transmitted using secure encryption.

Because neither configuration relies on third-party systems, both provide continuous control over the flow of data. However, the software’s open architecture makes it possible to exchange stored data with third-party software when needed and transfer it to the customer’s own dispatching or billing programs. The software can also be customized to reflect a corporate design if required.

Data can be physically transmitted from the frontend to the backend via Wi-Fi or a cellular network such as 4G or 5G. In most cases, a cellular network is preferable because Wi-Fi coverage is limited. Several configurations are also possible in this case. The mobile device can be connected to the existing infrastructure through a VPN, or a secure interface, or API, can be provided.