20.11.02 Briefing Note: Difference between revisions
No edit summary |
No edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The sections below detail enhancements that will be deployed to acumen the evening of <b>14 November 2020</b>. | |||
The sections below detail enhancements that will be deployed to acumen | |||
Users will need to do a hard reload of the system to see these changes. Instructions can be found on the [[FAQ]] page. | Users will need to do a hard reload of the system to see these changes. Instructions can be found on the [[FAQ]] page. | ||
| Line 7: | Line 5: | ||
The relevant [[User Guide]] pages have been updated. | The relevant [[User Guide]] pages have been updated. | ||
= New Functionality = | |||
== Manual Call == | |||
= Manual Call = | |||
Trains are typically called or activated 1-2 hrs before departure. Until this happens, the train displays in the Planned Layer on the platform docker. <i>For more information, see [[Platform Docker Display#Planning Layer]].</i> | Trains are typically called or activated 1-2 hrs before departure. Until this happens, the train displays in the Planned Layer on the platform docker. <i>For more information, see [[Platform Docker Display#Planning Layer]].</i> | ||
| Line 20: | Line 17: | ||
<b>Note:</b> This also applies to manually calling Q or Y paths. | <b>Note:</b> This also applies to manually calling Q or Y paths. | ||
To manually call a train, simply right click on the train and select <b>Manual | To manually call a train, simply right click on the train and select <b>Manual Call</b> as seen below. | ||
::[[File:manual_call.png|450px]] | |||
<b>Note:</b> The system searches for activation messages twice a minute, so a user may need to wait up to 30 seconds to see their manual call action processed. | <b>Note:</b> The system searches for activation messages twice a minute, so a user may need to wait up to 30 seconds to see their manual call action processed. | ||
<b>Remember:</b> acumen does not publish any messages. The manual call is only applicable to acumen and will not affect the activation status of the train in any other systems. | <b>Remember:</b> acumen does not publish any messages. The manual call is only applicable to acumen and will not affect the activation status of the train in any other systems. | ||
= Bug Fix = | |||
== Overdue trains originating at docker locations == | |||
It had been observed that some trains originating at a docker location, would disappear from the forecast if they did not depart on time. | |||
This has now been fixed. If a train does not depart on time, then the box extends and the lateness changes. | |||
Latest revision as of 11:31, 16 November 2020
The sections below detail enhancements that will be deployed to acumen the evening of 14 November 2020.
Users will need to do a hard reload of the system to see these changes. Instructions can be found on the FAQ page.
The relevant User Guide pages have been updated.
New Functionality
Manual Call
Trains are typically called or activated 1-2 hrs before departure. Until this happens, the train displays in the Planned Layer on the platform docker. For more information, see Platform Docker Display#Planning Layer.
With this enhancement, users now have the option to manually call a train, bringing it from the planning layer to the forecast layer.
Once in the forecast layer, that train can be re-planned, have train notes applied, associations amended etc.
Note: This also applies to manually calling Q or Y paths.
To manually call a train, simply right click on the train and select Manual Call as seen below.
Note: The system searches for activation messages twice a minute, so a user may need to wait up to 30 seconds to see their manual call action processed.
Remember: acumen does not publish any messages. The manual call is only applicable to acumen and will not affect the activation status of the train in any other systems.
Bug Fix
Overdue trains originating at docker locations
It had been observed that some trains originating at a docker location, would disappear from the forecast if they did not depart on time.
This has now been fixed. If a train does not depart on time, then the box extends and the lateness changes.