How to get Dispatcher Signature on the OFP?
This section explains the option to insert a signature with a date and time to the OFP, including the possibility to include these in the CrewBriefing version of the OFP. This is designed primarily for the Dispatcher to be able to provide a ‘signed’ OFP (FlightLog).
To enable adding a Signature, the following must be completed:
Make a signature scan that is saved as a .png file within the ‘Signatures’ folder.
This folder is found within the pps8sharedfolder and within the accounts sub-folder under the individual user. See the file path shown below in the image for the actual location to save the file.
Note: The scan image should have a maximum height of 42 pixels!
The AS0PAE is the user account (see image below) that requires the signature. The PNG file must be saved with the same name as the user account e.g. AS0PAE.png
Corporate Data: Mandatory Signature
Corporate Settings has options regarding adding a Signature, see the image below:
Prompt for options
The option for Mandatory Signature is Off by default, but when it is changed to Prompt for options during the planning process, in the Dispatch Guide Item, then the red signature prompt is provided where the user can choose to upload to CrewBriefing with a signature or not.
When the user clicks the Upload to CrewBriefing with Signature the signature prompt changes colour to green and the signature and date/time is added to the OFP, providing the appropriate Star Codes have been used in the FlightLog layout.
Auto On
If the user has chosen the Auto On option for the Mandatory Signature within Corporate Settings (as shown to the right), then the signature prompt in the Dispatch Guide Item is shown green in colour and already has a tick mark for Upload to CrewBriefing with Signature.
In the image above, the lower tick box can also be ticked to not include the signature, in which case the prompt box will remain green indicating that a selection has been made. However, if all ticks are removed then the box will be shown in red to indicate that it requires the attention of the user.
Star codes* on OFP
The Log Layout needs to have the Star Codes added to show the signature and the date and time, see below:
**SIGN
Inserts the scanned signature .png file stored in the ‘Signatures folder’, the file path is previously described in this section. The PNG file name must be saved as a combination of the account and user e.g. if the account is I02 and the user is IB, then the file should be named I02IB.png
*SIGNOFFDAYTIME
Inserts the date and time in format “YYYYMMDD – hhmm”. This is provided in ‘local’ date and time dependent to the user.
Flight Log layout Editor
The 2 Star Codes are shown below in an example of a Flight Log layout editor.
The result of inserting the 2 Star Codes is shown below.
