Utilizing the Estimated Departure Date on the Worksite
Overview: The Worksite page has recently received a new feature that will assist in plan and manage the reservations for your locations. The Estimated Departure Date field that is seen on the Arrival Preset section has now been added to the POB List area with updated functionality. Not only will it assist in managing your passenger reservations, it will also provide more accurate forecasted reports, bunk indicators, and lifeboat counts.
With the newest updates, the Estimated Departure Date entered for a passenger in the Arrival Preset area will carry down to the POB List when the passenger movement is applied. In addition to it carrying down, when a passenger has their request reservation created directly from their POB reservation, the Estimated Departure Date will automatically update to the date and time of that request/trip reservation.
With the new Estimated Departure Date field available, it is recommended that you hide the "Departure Date" column as part of your default hide/show columns. This will help prevent accidentally departing a passenger while still giving you the expected departure information needed for planning.
Estimated Departure Date for Arrival Presets
Passengers who are displayed in the Arrival Presets section have the Estimate Departure Date field available for entry if you have an idea of when they will be departing. This field in the Arrival Preset section only allows for manual entry as the departing POB Reservation for the passenger cannot be created and linked until the passenger is applied to the POB.
Setting this Estimated Departure Date here will provide accurate estimates for the Lifeboat Count tile, bunk indicators, Occupancy report on the Worksite, and the forecasted reports located on the Custom Reporting page.
Please note that the Estimated Departure Date field has no impact on the actual Departure Date for a passenger from your POB. Setting this date will not lead to any passengers being removed from the POB List in the future.
Estimated Departure Date for POB Passengers
Depending on the state of planning for the specific POB passenger, they may or may not have an Estimated Departure Date entered when they are on board.
If one was entered while they were in the Arrival Preset section, or if one was manually entered when they were on the POB List, it will appear as an editable field on their POB record. When this Estimated Departure Date field is editable, you will see the Departure Reservation field to the right displaying as (none) with no eyeball reservation icon.
Once a POB passenger has a request reservation created directly from their POB record, the Estimate Departure Date field will lock and become gray. The reservation eyeball will appear and the request name, and subsequent trip name, will appear. At this point, you will need to manage the request/trip reservations for that passenger to change their Estimated Departure Date being shown.
In the instance you've added a POB passenger to directly to a trip without making their reservation directly from the POB, you may see the eyeball and trip name while the Estimate Departure Date field is still editable.
If a passenger with an Estimate Departure Date does not leave by that date, they will not fall off of the POB List like they would if the Departure Date field would be entered.
It is recommended that you keep and maintain expected departure dates and reservations to ensure accurate reporting and planning continues.
To learn more about creating departing reservations directly from the POB, refer to the User Guide linked below:
https://helipass.screenstepslive.com/s/UsersGuide/m/66470/l/1298834-managing-request-from-pob-cob-list
0 Comments
Add your comment