Public transport networks play a vital role in connecting people with their workplaces, educational institutions, and other daily commitments. But these networks are dynamic, and disruptions to routes and schedules can impact commuters’ journeys. Staying updated about these updates is essential, as it helps individuals minimize the impact and arrive at their destinations with ease.
Updating a long-range transportation plan (TSP) is a complex process, and several milestones need to be completed before a final plan can be delivered. Funding opportunities, community interest, staff capacity, and other factors influence the timeline for completing a TSP update. In addition to relying on the traditional methods of updating their website, government transport departments can also utilize social media platforms to share immediate information about changes to routes and services.
When a TSP update is released, the Software Update Manager integrates the customer transports into the update procedure to reduce business downtime. For this, you create a buffer file, which contains all the transports to be included in the TSP update. During the roadmap step Configuration, you can use a dialog to provide the path and name of the buffer file. The transports from the buffer file are integrated into the TSP update during phase BIND_PATCH. In addition, you can override the default value of parameter VERS_AT_IMP by defining in this dialog if SUM should automatically create transport profile versions during import time. The resulting entries are validated later during phase ADJUSTPRP.