TIS Release Notes

v3.8.4.2 Deployed on 01/06/2026

Change Requests (CRs / CRQ):

  • [TIS2020-3371] – Synchronization of the company agreements with the outbound interfaces
    Follow-up fixes and refinements to the company agreement synchronization feature introduced in a previous release.
  • [TIS2020-3477] – Optimize Outbound Interfaces
    Follow-up fixes and refinements to the redesigned Outbound Interface Overview page introduced in a previous release.
  • [TIS2020-3576] – Landing page changes
    Redesigned the TIS landing page following the removal of the legacy login section.

    • The header has been removed and the remaining elements reorganized.
    • The left side now features a scrollable News section and a static FAQ and Contact Us section.
    • The display now shows total number of active users instead of currently logged-in users.

Tasks:

v3.8.4.1 Deployed on 26/05/2026

Change Requests (CRs / CRQ):
  • [TIS2020-3371] – Synchronization of the company agreements with the outbound interfaces
    Introduced a semi-automated workflow for linking company agreements with outbound interfaces. When requesting or editing a company agreement, users can opt in to data exchange via a new checkbox. Selecting it triggers a notification to TIS admins, who can then link the agreement to a specific outbound interface. Linked agreements remain intact when edited, ensuring continuous data flow.
  • [TIS2020-3411] – Wagons and Containers issues and further optimizations
    Continued improvements and optimisations in the wagons and containers logic based on analysis of additional GPS data.
    Improved association of wagons to trains, reducing missing associations where IM data is available.
  • [TIS2020-3450] – Task List for Approvals
    Introduced a new "Tasks" menu entry that provides company administrators with a centralized list of pending approvals, including user registration requests, company agreement requests. Email notification links now redirect to the task list, and tasks display a pending/done status with a visual red-dot indicator for open items.
  • [TIS2020-3470] – Show Nearby Trains based on current location
    Added a GPS-based "Nearby Trains" feature. Users can tap a GPS icon button on the map to center the view on their current location and display all running trains within a configurable radius (default 20 km). Available on both desktop and mobile in Advanced and Mobile views. Location permission is requested on first use.
  • [TIS2020-3479] – Excluding locations from train search
    Refined the train search panel to only propose locations that have been used in trains, reducing irrelevant location results and improving search accuracy for both current and historical trains.
  • [TIS2020-3486] – Prevent deletion of company agreements (set validity end period instead)
    Company agreements can no longer be deleted. Instead, users can expire an agreement by setting its validity end time to the current system time. Expired agreements are displayed in a visually distinct style.
  • [TIS2020-3494] – Change retention logic for MESSAGE table
    Reduced the retention period for stored XML messages in the MESSAGE table from 45 days to 14 days. The simplified retention logic improves database performance while still covering the operational need for resending past messages to newly involved companies.
  • [TIS2020-3477] – Optimize Outbound Interfaces
    Redesigned the Outbound Interface Overview page with a hierarchical and organized company → queue → interface structure.
  • [TIS2020-3500] – Prevent blocking of processing when receiving lots of messages for same train
    Improved message processing logic to detect and automatically recover from worker queue saturation when very high volumes of messages for the same train are received. The system now remains stable and message flow is restored automatically even under excessive load from a single source.
  • [TIS2020-3504] – Improve grouping of trains (multiple trains at same location) on map
    Improved the labelling and visual presentation of train groups on the map when multiple trains are located at the same position.
  • [TIS2020-3511] – Visibility of registered users
    Added a new "Registrations" page for company administrators, showing the status of users who have not yet completed the full registration process. Statuses include Rejected, Pending Azure, Email Confirmed, and Pending Email Confirmation. Company admins can also delete registration entries to allow users to re-register.
  • [TIS2020-3519] – Collect statistics about number of trains sent via interface/queue/company
    Introduced data aggregation for counting the number of trains sent per outbound interface. Data is aggregated daily and monthly for use in reporting.
  • [TIS2020-3539] – Retention time for user registrations and expired company agreements
    Added configurable retention periods (default 1 year) for user registrations and company agreement requests based on status (pending, accepted/done, rejected). Removing pending registrations or agreements also removes the corresponding task.
  • [TIS2020-3469] – Remove linkable flag of train sections after 24–48h if there is no counter part available
    Train sections that remain unlinked after a configurable period (24–48h) are no longer considered linkable. Previously, sections ending in a linking region retained their linkable flag indefinitely, even when no matching counterpart existed. Removing the flag improves the accuracy of linking statistics by excluding trains that have no realistic linking opportunity.
Bug Fixes:
  • [TIS2020-3468] – Intermediate Section Linking
    Fixed an issue where trains were automatically unlinked after receiving running information for an intermediate section. The intermediate section insertion logic has been optimized to prevent incorrect unlinking of previously established train associations.
  • [TIS2020-3521] – RFC Layer error messages
    Resolved an issue where users with a previously saved RFC layer received persistent error messages upon login. The error could not be cleared through the UI. Handling of legacy RFC layer selections has been corrected so that invalid saved layers no longer cause errors.
  • [TIS2020-3524] – NPE when viewing interruptions
    Fixed a NullPointerException that occurred when certain users navigated to the overview of interruptions.
  • [TIS2020-3527] – Company Agreements for a company with location restrictions
    Fixed an issue where a terminal with a location restriction could not see trains covered by a company agreement because the OTN on the relevant section did not fall within the expected range. Train visibility through company agreements now correctly accounts for location-restricted companies.
  • [TIS2020-3534] – Authorized Company cannot see 'Add new Agreements'
    Fixed an issue where an authorized company (granted access via "Add new Agreement") could view trains on the map but could not see the corresponding agreement in the Company Agreements menu.
  • [TIS2020-3535] – Company page not editable with Edit own Company right
    Fixed a permission issue where company administrators with the "Edit own Company" right were unable to edit their company's page. The page now correctly allows editing for users with the appropriate permissions.
  • [TIS2020-3553] – TCRMessage error
    Fixed an error in TCR message processing that caused a NullPointerException when creating interruption notification emails.
  • [TIS2020-3550] – Duplicate entries for multiple locations
    Fixed a display issue where certain locations (e.g. in Bern) appeared as duplicate rows (2–3 entries each) on the train detail page.
  • [TIS2020-3555] – Red Dot on Incident Management menu
    Fixed an issue where the unread-message indicator (red dot) on the Incident Management menu could not be cleared even after marking all messages as read. The read/unread tracking logic has been corrected.
  • [TIS2020-3563] – Wrong date format in the frontend
    Fixed a display issue where dates were shown in American format (MM/DD/YYYY) instead of the expected European format in certain parts of the UI.

v3.8.3 Deployed on 23/03/2026

Change Requests (CRs / CRQ):
  • [TIS2020-3411] – Wagons and Containers issues and further optimizations
    Implemented additional fixes and optimisations in the wagons and containers logic based on analysis of new GPS data.

    • Improved association of wagons to trains, significantly reducing missing associations where IM data is available.
    • Addressed identified bugs and optimised the association algorithm to reduce gaps between consecutive train associations that previously prevented stable linking.
  • [TIS2020-3500] – Prevent blocking of processing when receiving lots of messages for same train (e.g. IM 1224)
    Improved message processing logic to avoid system stalls when very high volumes of messages for the same train are received.
  • [TIS2020-3309] – ETMN Communication Platform
    Introduced the initial version of the ETMN Communication Platform, enabling users to contact relevant operational partners directly from within TIS. The feature supports context-based contact selection and integration with Microsoft Teams for faster coordination.
Bug Fixes:
  • [TIS2020-3033] – Worker queue filled up and blocked message flow
    Fixed an issue where the message broker could become saturated and block message processing in production. Handling has been improved so that message flow is restored automatically and the system remains stable even when queues approach capacity
  • [TIS2020-3429] – Dangerous Goods icon not loading
    Resolved an issue where the Dangerous Goods icon was missing for certain trains in the UI.
  • [TIS2020-3466] – No visible train path for historical trains
    Fixed a display issue where routes for historical trains were not shown on the map.
  • [TIS2020-3483] – Visual regression in linking dialog and on agreement approval page
    Corrected layout regressions in the manual linking dialog and on the company agreement approval page. Spacing and alignment have been improved.
  • [TIS2020-3484] – Location(s) of interruption missing on train detail page
    Fixed an issue in the Incident tab on the train detail page where “Locations of interruption” remained empty despite a recorded incident location.
  • [TIS2020-3508] – Layout on user registration screen broken
    Improved the layout of the user registration screen on larger desktop displays.
  • [TIS2020-3514] – Missing Company Group flag in “Add new Agreement” function
    Re-enabled the “Company Group” flag in the “Add new Agreement” screen for company administrators.
  • [TIS2020-3520] – Internal error – No polyline features for RFCs
    Resolved an internal error that occurred when RFC layers were enabled.
  • [TIS2020-3525] – Company Admin cannot edit accounts – /api/traffic-control-centers forbidden
    Fixed a permission issue where company administrators received a 403 Forbidden response when editing accounts, resulting in a blank screen. Permission handling has been corrected so that account editing now works as expected.
Tasks:

v3.8.1 Deployed on 16/02/2026

  • [TIS2020-2962– RNE TIS Single Sign-On
    The Single Sign-On integration with RNE’s Azure-based identity service has been further stabilised, improving authentication reliability and ensuring smoother user access across environments.
  • [TIS2020-3307] – Linking by Train Identifier
    Train information can now be linked using shared Train and Path Identifiers in addition to existing rules. This improves linking reliability in complex operational scenarios.
  • [TIS2020-3364] – (Matched) running status report message cause issues in outbound processing
    Concurrency bottlenecks in outbound backlog handling have been removed. XML processing and backlog workflows now run more smoothly, reducing the risk of blocked outbound threads.
  • [TIS2020-3401] – Wrong undocumented delay
    The calculation of undocumented delay has been optimized to prevent unrealistic or misleading delay values where negative delays are provided.
  • [TIS2020-3422] – Actual not matched against the planned
    Actual messages are now matched more accurately to planned entries, preventing duplicate timeline rows and ensuring clearer operational views.
  • [TIS2020-3453– RFC layers change in RIS
    RFC layers have been updated according to the latest RIS corridor configuration.
  • [TIS2020-3459] – Improve performance of forecast qualifier calculation
    METAQ forecast qualifier calculations now process sender and location groupings more efficiently, reducing load on large datasets and improving responsiveness.

Bug Fixes

  • [TIS2020-3460] – Company admin cannot approve agreement from agreement list
    Company administrators can again approve agreements directly from the agreement list, restoring the intended approval workflow.
  • [TIS2020-3142] – Transport Device optimisation for train association and visualisation
    SenderReference-based linking now keeps GPS data, wagons, and containers correctly aligned with the active train. GPS messages are no longer permanently tied to completed trains. Follow-up services can now receive correct GPS associations, improving continuity of location tracking.
  • [TIS2020-3262] – ETMN: additional TCM info
    Defects in handling train composition data have been fixed. Locomotives, wagons, dangerous goods indicators, and containers now display consistently according to user rights and visibility rules.
  • [TIS2020-3433] – Bidirectional agreement doesn’t work
    The Bidirectional Agreement setting is now saved correctly and remains active after configuration changes.
  • [TIS2020-3440] – Trains not linkable
    A defect preventing valid train linking at configured locations has been corrected. Eligible trains can now be linked successfully.
  • [TIS2020-3442] – Error in Browser console on empty incident overview
    A browser console error occurring when no recent incidents were available has been removed. Archived incidents remain accessible and the page loads cleanly.

v3.8.0.1 Deployment on 26/01/2026

Main Enhancements & Improvements:

  • [TIS2020-2962– RNE TIS Single Sign-On
    TIS now supports integration with RNE’s central identity (Azure) for Single Sign-On. This lays the foundation for users to access TIS and other RNE tools with one unified account, simplifying user management and improving security.
    A follow-up email will be sent to all impacted users with instructions on how to proceed.
  • [TIS2020-3294] – Company Agreement Improvements:
    Company agreements have been extended and refined to better support complex setups:

    • When requesting an agreement, users can optionally request it for the entire company group, automatically creating the corresponding individual requests in the background.
    • Outgoing notification emails now clarify when group-based agreement requests are created and list the affected agreements.
    • Expired agreements are now visually highlighted and can be filtered via a dedicated “Expired” column.
  • [TIS2020-3039– Implementation of PassengerTrainCompositionMessage
    TIS has been extended to process and distribute PassengerTrainCompositionMessage according to the latest available schema.
  • [TIS2020-2985] – Modification of the TrainIdentifier Procedure
    The internal train identifier handling has been adjusted to better respect identifiers provided by Infrastructure Managers (IMs):

    • If a Train Identifier is provided for the first segment, TIS now preserves this identifier and only falls back to existing derivation rules when it is not available.
  • [TIS2020-3379] – Add monitoring of active database sessions and session run times to Check MK
    Additional monitoring has been added for database activity, including the number of active sessions and their run times. This helps identify performance issues earlier and keep TIS stable under high load.

Performance Improvements:

  • [TIS2020-3361] – Wrong current location of the transport device
    The calculation and display of the current location of transport devices on the map has been corrected and optimised.

Bug Fixes:

  • [TIS2020-3415] – PDM for one network invalidates PSNM for another
    A defect was fixed where processing a PDM from one network could unintentionally invalidate a PSNM from another network for the same train. The message handling logic has been adjusted so that updates are correctly isolated per network and message type.

v3.7.1.2 Deployment on 21/01/2026

Bug Fixes:

  • [TIS2020-3427] – Invalidated timetables
    Timetable data for some train sections was incorrectly cleared when new timetables arrived for other infrastructure managers on the same train, causing sections to lose valid timetables and become unlinked. The fix adjusts timetable message handling so that updates only affect IMs included in the new timetables, preventing unintended timetable invalidation and preserving correct section linking.
  • [TIS2020-3262] – ETMN: additional TCM info
    Dangerous goods indicators and details were sometimes shown incorrectly or not shown at all. The hotfix adjusts how dangerous goods data is applied so that this information is displayed consistently.

v3.7.1.1 Deployment on 09/12/2025

Change Requests (CRs / CRQ)

  • [TIS2020-3262] – ETMN: additional TCM info
    More information from train composition messages is now shown in ETMN (e.g. locomotives, wagons, dangerous goods indicators and containers), giving a more complete overview of train details.
  • [TIS2020-3326] – Company Page does not allow to create alpha numeric Company codes
    The company page now accepts company codes that contain both letters and numbers, so you can align TIS company codes with your internal coding rules.
  • [TIS2020-3338] – Thresholds for forecast application and sending
    Forecasts are now only applied and forwarded when they meet configurable quality thresholds. This reduces noise from low‑quality or unreliable forecasts.
  • [TIS2020-3339] – Location search with different station/city languages
    Location search has been improved so stations and cities can be found using different language variants (for example “Vienna” and “Wien Hbf”), making searches easier for international users.
  • [TIS2020-3346] – Improve Interruption Page (creation, overview and affected trains)
    The interruption page has been optimised. Creating interruptions, viewing their details and loading/filtering many affected trains is now faster and more responsive.
  • [TIS2020-3382] – Replace TIS2020 to TIS
    The product name shown in the browser and in shared links has been updated from “TIS2020” to “TIS”, for a consistent and modern branding.

Bugs

  • [TIS2020-3168] – TrainComposition Message created NPE
    A technical error that could occur when creating train composition messages has been fixed, improving the reliability of composition handling.
  • [TIS2020-3354] – Infinite scroll glitch
    An issue where endless lists could jump backwards or behave strangely has been resolved. Infinite scrolling now behaves smoothly.
  • [TIS2020-3355] – OTN-Group update failed
    A problem that caused errors when updating OTN groups has been fixed. Changes to OTN groups are now saved correctly.
  • [TIS2020-3363] – Can see train via url but not search
    A bug where a train was accessible via direct link but did not appear in search results has been corrected. Search is now consistent with direct URLs.
  • [TIS2020-3365] – Unable to move the map
    The map can be moved again even when linking candidates are displayed. Panning and interacting with the map works as expected.
  • [TIS2020-3366] – Email preparation errors
    Frequent errors during the creation of system emails (due to a problematic template) have been fixed. Notification emails are now generated more reliably.
  • [TIS2020-3391] – RSRM in ‘PENDING’ state for over an hour
    RSRM messages that were stuck in “PENDING” for long periods are now processed correctly. Linking to locations and trains happens within the expected time.

Issues / Tasks

  • [TIS2020-3360] – Update Backend dependencies
    Core backend components have been updated to newer versions. This is mostly invisible to users but improves security, stability and future maintainability.
  • [TIS2020-3421] – Production Deployment 3.7.1.1
    Technical work to deploy the 3.7.x version line into production, including configuration and memory tuning. This ensures a stable rollout under real‑world load.

Sub-tasks

  • [TIS2020-3351] – Rewrite Segment Cache access
    Internal handling of route segment data has been reworked to access cached information more efficiently, supporting more stable and performant operation in dependent features.

v3.6.6 Deployed on 15/09/2025

CRQ

  • [TIS2020-3297] – Hide segments that connect to locations outside bounding box
  • [TIS2020-3300] – Outbound Interface National/international flag
  • [TIS2020-3337] – Adding a flag to enable/disable NETA forecasts on the outbound interfaces

Bugs

v3.6.4 Deployed on 25/08/2025

CRQ

  • [TIS2020-2841] – Prepare new VM for background services
  • [TIS2020-2953] – TCRMessage – IMT automatic data exchange
  • [TIS2020-3130] – TIS Mobile 2024: Performance – Train Search on Startup and Default Limit (Mobile)
  • [TIS2020-3141] – Optimization of geofencing
  • [TIS2020-3142] – Transport Device optimization for train association and visualization
  • [TIS2020-3155] – Request of Company Agreements new functions
  • [TIS2020-3193] – Linking limitation where location is repeating
  • [TIS2020-3254] – Restricting visibility of TIS Company Admin
  • [TIS2020-3263] – User role change regarding Two-Factor Authentication (2FA)
  • [TIS2020-3277] – ETAAccuracy TRF AddOn
  • [TIS2020-3286] – Info for user in case of network loss
  • [TIS2020-3289] – PlayStore button on the landing page
  • [TIS2020-3299] – TIS Mobile Connection loss error handling

Bugs

v3.5.5 Deployed on 16/06/2025

Story

Issues

  • [TIS2020-3264] – Train Performance – Incorrect informative message displayed

CRQ

  • [TIS2020-3120] – TIS Mobile 2024: Train Search – Simplified Search Field (Mobile Only)
  • [TIS2020-3121] – TIS Mobile 2024: Train Search – Result as Map Only (Mobile Only)
  • [TIS2020-3122] – TIS Mobile 2024: Train Search – Use Departure and Current Date in Time Window
  • [TIS2020-3123] – TIS Mobile 2024: Train Header Information Display Panel
  • [TIS2020-3124] – TIS Mobile 2024: Train Display on Map – Circle with Direction
  • [TIS2020-3125] – TIS Mobile 2024: Train Display on Map – Clustering of Trains
  • [TIS2020-3126] – TIS Mobile 2024: Train Display on Map – Trains at Same Location (Desktop/Mobile)
  • [TIS2020-3127] – TIS Mobile 2024: Click Train on Map (Desktop/Mobile)
  • [TIS2020-3128] – TIS Mobile 2024: Train Route Display for Selected Train (Desktop/Mobile)
  • [TIS2020-3129] – TIS Mobile 2024: Follow Train on Map
  • [TIS2020-3130] – TIS Mobile 2024: Performance – Train Search on Startup and Default Limit (Mobile)
  • [TIS2020-3131] – TIS Mobile 2024: Performance – Cache Network Topology and Company in Local Storage
  • [TIS2020-3132] – TIS Mobile 2024: Performance – Reduce Map Details (Mobile)
  • [TIS2020-3133] – TIS Mobile 2024: PWA
  • [TIS2020-3134] – TIS Mobile 2024: Prevent Screen from Turning Off (Mobile)
  • [TIS2020-3138] – Adjust time zone in RSRMs according to reported GPS position
  • [TIS2020-3148] – TIS Mobile 2024: Performance – Technical improvements
  • [TIS2020-3173] – Train Running Forecast: inbound/outbound adaptions for multiple locations in message
  • [TIS2020-3181] – TIS Mobile 2024: Performance – Cache Translations
  • [TIS2020-3218] – Coloring based on train type
  • [TIS2020-3219] – Connection Diagram View

Bugs

Task

  • [TIS2020-3234] – Maintenance page improvement – Automatic redirect
  • [TIS2020-3266] – TIS Mobile 2024: Improvements Train Direction
  • [TIS2020-3267] – TIS Mobile 2024: Improvements Train Header
  • [TIS2020-3268] – TIS Mobile 2024: Improvements Train Search
  • [TIS2020-3269] – TIS Mobile 2024: Other improvements
  • [TIS2020-3271] – Add up to date screenshot with different formfactors
  • [TIS2020-3279] – TIS Mobile UI Improvements

v3.4.10 Deployed on 17/03/2025

Issues

CRQ

  • [TIS2020-2479] – Automatic unlinking of trains
  • [TIS2020-2991] – RailData TRI Version Update to v3.4
  • [TIS2020-3125] – TIS Mobile 2024: Train Display on Map – Clustering of Trains
  • [TIS2020-3134] – TIS Mobile 2024: Prevent Screen from Turning Off (Mobile)
  • [TIS2020-3181] – TIS Mobile 2024: Performance – Cache Translations

Bugs

  • [TIS2020-3186] – Message not sent after leading TID change
  • [TIS2020-3227] – Link to interruption in popup is broken
  • [TIS2020-3237] – Section and Performance table is not displaying the networks as before
  • [TIS2020-3238] – Can’t edit train details

v3.4.8 Deployed on 17/02/2025

Task

  • [TIS2020-3194] – Remove (big) unused indexes
  • [TIS2020-3184] – Move table/index defragmentation of big tables to specific times
  • [TIS2020-3203] – Use HTTPS when communicating with Nexus
  • [TIS2020-3214] – Hibernate uses inefficient query after update

Issues

CRQ

  • [TIS2020-2479] – Automatic unlinking of trains
  • [TIS2020-2761] – Reject messages where timestamps are out of range
  • [TIS2020-2999] – Unlink Functionality within Train Linking History
  • [TIS2020-3122] – TIS Mobile 2024: Train Search – Use Departure and Current Date in Time Window
  • [TIS2020-3129] – TIS Mobile 2024: Follow Train on Map
  • [TIS2020-3130] – TIS Mobile 2024: Performance – Train Search on Startup and Default Limit (Mobile)
  • [TIS2020-3131] – TIS Mobile 2024: Performance – Cache Network Topology and Company in Local Storage
  • [TIS2020-3132] – TIS Mobile 2024: Performance – Reduce Map Details (Mobile)
  • [TIS2020-3196] – Reorganize defragmentation tasks (Shrink Space)
  • [TIS2020-3197] – Reorganize index rebuilds
  • [TIS2020-3198] – Introduce a MESSAGE_BUFFER to prevent outages during defragmentation

Bugs

  • [TIS2020-3147] – New companies cannot be created via the UI
  • [TIS2020-3167] – Companies with status DELETED can be selected
  • [TIS2020-3183] – Companies in message interface filter
  • [TIS2020-3185] – Mismatch in data between application and database for historical train
  • [TIS2020-3187] – Message Statistics Incorrect
  • [TIS2020-3195] – Sync config from production config not working
  • [TIS2020-3199] – Translation defaults to ascii
  • [TIS2020-3208] – Kryo issues on RNE Test

v3.4.4 Deployed on 18/12/2024

Issues

  • [TIS2020-3089] – Limit set of allowed characters for outbound target queue name

Task

  • [TIS2020-3091] – Unlinking should take info from train linking history into account
  • [TIS2020-3139] – Change the default concurrent logins

CRQ

  • [TIS2020-2479] – Automatic unlinking of trains
  • [TIS2020-2761] – Reject messages where timestamps are out of range
  • [TIS2020-2984] – Referenced data to the Train Details
  • [TIS2020-3005] – SpaceTimeDiagram – Modifications
  • [TIS2020-3012] – Additional TrainLocationStatus from the Terminals to be taken into account
  • [TIS2020-3027] – Visibility of TIS Company Admin
  • [TIS2020-3064] – Extend search improvement for special characters to companies and more
  • [TIS2020-3096] – Time shifting based on actuals & forecasts

Bugs

v3.3.1 Deployed on 23/09/2024

Issues

  • [TIS2020-3068] – Chrome doesn’t autofill passwords
  • [TIS2020-3073] – Show error if request for trains to company without company admin

CRQ

  • [TIS2020-2999] – Unlink Functionality within Train Linking History
  • [TIS2020-3001] – PDM new Timing attributes for RunThrough status
  • [TIS2020-3005] – SpaceTimeDiagram – Modifications
  • [TIS2020-3050] – Exclude Messages from Train Edit from Message Time Validation (Cannot edit train details in UAT)
  • [TIS2020-3058] – Change logic for use of booked delta
  • [TIS2020-3059] – Improve Transport Device to train matching

Bugs

  • [TIS2020-3049] – Resetting search filter puts focus to wrong field
  • [TIS2020-3060] – Message Type “All” appearing in outbound interface filters
  • [TIS2020-3062] – National section split into 2
  • [TIS2020-3066] – Translation Table – Punctuality Performance
  • [TIS2020-3069] – Company admin could not verify Company Agreement
  • [TIS2020-3075] – Timing information in the basic view

v3.2.2 Deployed on 08/07/2024

Issues

  • [TIS2020-2972] – Distance mismatch between TRAIN, TRAIN_DETAIL and TRAIN_SECTION tables
  • [TIS2020-3019] – Trains not linked based on Location Pairs

CRQ

  • [TIS2020-2480] – Distance Calculation for Historical Data (DWH)
  • [TIS2020-2761] – Reject messages where timestamps are out of range
  • [TIS2020-2925] – Update of Section and Punctuality Performance report table
  • [TIS2020-2928] – Request for accessing single or multiple trains
  • [TIS2020-2968] – New TIS User entities
  • [TIS2020-2984] – Referenced data to the Train Details

Bugs

  • [TIS2020-3040] – Wagon and ContainersTab – Error
  • [TIS2020-3041] – Flipping of pages on W&C search page not possible
  • [TIS2020-3044] – W&C Count of Transportdevices different on UI and Database
  • [TIS2020-3046] – Transport Device Path Details
  • [TIS2020-3047] – Ordering of locations for Transport Device

Task

  • [TIS2020-2989] – Populating data into columns FIRST_LOCATION_ID and LAST_LOCATION_ID of TRAIN table

Sub-Task

  • [TIS2020-3020] – Performance Calculation for historical data (DWH)

v3.1.3 Deployed on 24/04/2024

Task

  • [TIS2020-2979] – Test Topology from TIS on UAT
  • [TIS2020-3007] – Change default value for “all location search” in search filter
  • [TIS2020-3015] – Change all instances to RIS Production as Topology/Company source

Issues

CRQ

Bugs

  • [TIS2020-2956] – Train not visible in the Spacetime Diagram
  • [TIS2020-2983] – Delta t volue +0 not displayed on TrainSearch Page
  • [TIS2020-2986] – Allow old OperationalTrainNumber element from 2.2.4 TCM messages
  • [TIS2020-2990] – Translation doesn’t update
  • [TIS2020-3004] – User error when searching historic trains

v3.0.0 Deployed on 19/02/2024

Issues

  • [TIS2020-2972] – Distance mismatch between TRAIN, TRAIN_DETAIL and TRAIN_SECTION tables

CRQ

  • [TIS2020-2561] – Ensure correct order when processing PDM+PSNM
  • [TIS2020-2845] – Transport Device Tracking: Connecting Transport Devices to Trains
  • [TIS2020-2869] – Different Section Identifier when using Start Date instead of Transfer Date

Bugs

Task