PakEnergy Support Portal

                                PakEnergy Transport Release Notes For September 2024 Build

Time Off/Vacation

• Prior to this release, companies were able to input vacation time for a driver, but this needed to be handled by a back-office team member.  Additionally, if a trucking company allows “X” amount of days off per year they are not able to keep track of this within the system.
• Outlined below are all the enhancements which have been made for time off/vacation requests.
  1. Drivers can submit time off requests from the mobile application and these requests will be immediately added to the setup > driver screen and dispatch > driver schedules
  2. Companies can determine which driver/asset schedules codes are tied to a “TIME OFF” request, create templates which can define by tenure year how many days the driver can take off and how many days can carry over and which drivers are associated to each template.
  3. When a time off request is submitted, the system can automatically generate an associated load/ticket so these tickets can be added to payroll settlements if the driver is paid for this time off.
  4. There is no impact to existing vacation records which were input prior to this change.  The VAC code has the TIME OFF flag turned on and will be associated to all drives so if users do not want to take advantage of the additional enhancements they can use the feature as is.

• To utilize the new feature, please start by going to the setup > definition > code tab.
  1. Create a new Driver/Asset Schedule code or leverage an existing code and turn on the TIME OFF true/false flag

1. Create a template (ie company drivers, contractor.  A template will be used to determine how many days a driver is allowed to take off for a given tenure year and which drivers are associated to this template
2. Select the drivers which are associated to the template

• On the setup > admin > company page (left hand column), a company can define their fiscal start month and if they want to auto create loads/tickets when a time off request has been submitted.

• On the setup > driver tab, the Vacation section has been relabled as TIME OFF TOTALS and TIME OFF ENTRIES
  1. The time off totals grid will show the user which driver/asset schedule codes have the time off flag turned on and are associated to the driver. 
  2. The user can select which fiscal year they would like to see the totals and entires.  Fiscal years available will be 2 years back, 1 year back, current year and next year.
  3. The user will be able to see which code/template are associatet to the driver and see a roll up of how many time off days have been used/planned, how many are available and how many are remaining per code.  The driver will also be able to see this information when submitting new time off requests on the mobile application.  
  4. *Please note total available days include carry over from the prior year if applicable.

1. In the time off entries grid, user can see all submissions by day for the current fiscal year selected.  They will be able to see the associated time off code, amount of day they are taking off (this can be input as a decimal, ie 0.25, 0.5, 0.75, 1), notes and if the loads/tickets are being created which associated BOL is tied to this time off request.   
2. When inputting a new time off entry, users will select the date range the time off request is for, which time off code is associated and notes.  Once entered the entries will show up in the grid below and users can modify each time off entry if there are changes needed.  
3. User will click save on popup and new entries will be added.
4. *Please note the time off totals does not update until user clicks save at driver level

1. Time off entries can also be input from the dispatch board > right click on driver and update status OR from the dispatch > schedule tab.   All three screens are linked and connected so a change on one screen will update the others

• Time Off On Mobile Device
  1. On the mobile application, the RTU button now includes TIME OFF submissions.

1. When a driver clicks RTU/Time Off, they can select from a TIME OFF requests or an RTU request
2. On the TIME OFF tab, a driver will be able to see all associated TIME OFF codes, Total Days Available, Total Days Remaining and Total Days Used.  They can also select from multiple fiscal years.  

1. When drivers click new submission, they will be able to define the start date, end date, the time off code and include notes.  Once driver clicks generate they will see the various day off entires and make any necessary adjustments to each day.  Once they click submit this will add TIME OFF entries to the portal.  
2. *Please note if creation of loads/tickets when a time off entry is created, the system will automatically generate loads/tickets for each day.   All of the dates (ie shift date, arrival, departure, completion) will be the date the driver is taking the time off request.  As an example if driver submitts a request for TIE OFF on 12/12/24 then all ticket dates will be 12/12/24 so this ticket will not show up for payroll settlements until this payroll cycle is run.

Tickets

• Two new attributes have been added to the ticket screen
  1. Externally Synced Flag: Yes/No.  This flag can be used as a query parameter to extract tickets which have not been externally synced.
  2. External Sync ID: Users can store an ID from an external system and associate to a PakTransport ticket #.

• Trucked By field: On setup > terminal level, a user can update the trucked by field which prints on the run ticket to be the first line of the terminal level run ticket header.  

Finance

• Four new components have been added for finance calculations
  1. Load Shift Count – This component will return the # of loads assigned to driver for a given shift
  2. Load Shift Sequence # - This component will return which order the load was done with a driver’s shift
  3. Drop Off Count – This component will return the count of drop offs for a given load
  4. Drop Off Sequence # - This component will return the sequence of drop offs completed for a given load

API

• With the two new fields, externally sync ID and externally synced flag, added to the Ticket Screen, API users can now extract only tickets which do not have the externally synced flag on/true, obtain these variables in the outbound ticket api and update these variables with the inbound ticket api.

• Hire date has been added to the inbound/outbound setup > driver api

Resolved Bugs

• On setup > pickup and setup > drop off screen if ALL subterminals were removed, the subterminals were still associated to the location.
• Calculations: Text fields were not logically working when used in an If/Then calculation.
• On dispatch board > open load grid, if column width were adjusted and saved within profile if the user used a mouse or trackpad and scrolled down, the column width would remain constant.
• Load and ticket import works with contract logic when an Account or operator has changed for a given pickup or drop off
• Geotab API Call to extract odometers has been updated from Geotab’s DiagnosticOdometerAdjustmentId to now use DiagnosticOdometerId.   The adjustment ID field attempts to calculate odometer if driver is offline and it appears this does not always work properly.  Geotab informed us to use this variable to be more safe/accurate – DiagnosticOdometerId.
• Load Creation: When creating new loads, if a user selected a scenario to determine the pickup and drop off associated to the load, the load creation pickup and drop off fields were not auto populating form scenario level
• On load > import load, the duplicate confirmation validation was not providing user a validation error.