ZForms - Forms Guide

Overview

Forms-based Messaging (FBM) is a feature enhancement to the Zonar Messaging application. Zonar Messaging is a simple messaging system between Dispatchers and their Drivers through Ground Traffic Control and Samsung tablet. The FBM feature updates messaging to use predefined forms. FBM is designed to replace our customers paper forms with an electronic form. This document covers the different processes involved in developing a form for a customer. Also covered are available forms in the template library.

FBM Benefits

• Email-style folders for convenient message management within Ground Traffic Control and on the Samsung tablet (e.g. Inbox, Sent, Archive, etc).
• Predefined forms for data consistency.
• Replaces our customer's paper forms.
• Offers simple route-dispatch solution.
• Facilitates bulk message handling via message CSV import and export (e.g. Fleet dispatching).

All About The Forms

The Forms Template Library

Customers who are signed up for “ZForms” have access to all of the forms available in our template library. A demonstration of each form in the template library will be given by the Configurations team to help the customer determine which forms would be beneficial.

The template library is a collection of forms that are commonly used in a variety of transportation verticals with related functions but are not focused on specific applications. These forms are also designed to give the customer a starting point with minimal development time.

These forms will be offered as generic templates and considered the base forms.

Base Forms

During the forms creation process, the customer determines if a form in the template library will work for their needs as a “Base Form.” The customer can request optional modifications to fit their specific requirements, such as placement and size of certain fields. This optional customization can also include duplication of existing fields. Customers who are able to stay within these requirements maintain a “Base” forms creation level.

Custom Forms

If a customer requests additional functionality not covered in the forms available in the template library or requests a new form that requires additional fields, expanding a form’s functionality, the form creation level becomes “Custom”.

Forms can also be created from scratch, creating a new form type. These forms will also be considered at the “Custom” level.

The configurations team will be happy to work with the Customer to create any custom form they need for an additional cost.

What Makes Up A Form

There are two types of forms; a Driver Form that originates from the driver side (2020 or other tablet). The other type is a Dispatcher form, originating from within Ground Traffic Control. It is possible to define which form will be used to reply to the original form. Understanding which side of the system the form will be completed and sent from is key to the success of the custom form.

Each form contains an array of “Controls” which are defined and labeled accordingly.

A “Control” is a single form object that can be placed and moved within the form screen. Controls are the basic building blocks of all forms. The available Controls are:

 

1. Input Field: The input field type allows for direct input of text, which can have specific requirements such as: maximum character length, numeric value, date and time, email, etc.
2. Dropdown List: This field is used to allow for quick entry of pre-determined items such as delivery material, location where package is left, etc.
3. Text Area: The text area field is used for entering short mixed input text and numbers.
4. Paragraph Text: Free form text can be entered into the form, such as operator notes, etc.

5. Static Label: Allows for the display of static text, such as instructions, guides, formatting instructions, user agreements, etc.
6. Switch: This field is used for positive and negative responses such as a “Yes/No” answer to specific questions like “Was the delivery successful”, “Was water added”, or an “Up/Down” answer to what position was the plow.
7. Signature Field: The signature field allows for the capture of a signature on the tablet. Used for customer delivery confirmation, driver verification, etc.

Note: The last two fields, Signature & Switch, are only available for forms on the tablet that an operator completes.

FBM also has two special fields available including “Magic Fields” and “Carry-over Fields.”

Magic Fields are used to add special formatting to an input field. This allows them to auto-populate for the user. These fields can be populated with the following data:

• Time: Populates with the current time.
• Date: Populates with today’s date.
• Driver Name: Populates with the Driver’s First and Last name.
• Driver Tag ID: Populates the driver’s Login ID for the tablet.
• Device ID: Populates with the GPSID the tablet is currently attached to.
• Asset Number: Populates with the “Asset No.” as associated in Ground Traffic Control.
• Odometer: Populates the current odometer reading in miles.

Carry-over Fields are specially formatted fields that will automatically populate the entered data into the same field on the reply form. For example: A dispatcher enters “1600 12^th Ave.” in an address input field and sends the form. When the driver taps the reply button, the address field in the reply form will contain “1600 12^th Ave.”

Template Library Forms

Below are the currently offered forms in the Template Library. A brief description and possible uses for the form is included. This library will continue to grow as customers request new forms.

Trip or Route Assignment

Description	This form is used to assign a specific trip or route to a driver. It can be used to assign a preset route, customer route, or can be used for transporting a load from one location to another. Loads depend on the market being served and could include freight, people, goods, etc. Multiple stops can be included for routes that require pickups and drop-offs. There is a starting point and endpoint that denotes the start and end of the trip.
Form Fields	Trip assignment forms require the driver reply forms for the trip acceptance, stop notification, and pick up or drop-off status. Information included: Driver, Asset Route #, Customer (Input Fields: Text and Carry Overs to Reply Form) # of Stops (Input Field: Number) Accept / Reject (Switch) For each stop: Stop Number / Location, Stop Type (Origin / Destination / Interim), Arrival / Departure Times
Sample

Load Assignment Manifest

Description	This form assigns one or more loads to a driver. This may be associated with an assigned trip with multiple pickups and/or drop-offs.
Form Fields	Each load is itemized separately and includes the following information: Invoice No., Customer, Order # (Input Fields: Text or Numbers) Contents, Quantity, Weight / Volume (Input Fields: Text or Numbers) Shipper / Origin: Address (Input Fields: Text) Receiver / Destination: Address (Input Fields: Text)
Sample

Delivery Receipt

Description	This form is used to confirm delivery of goods to the receiving customer.
Form Fields	Information included: Invoice #, Order #, Quantity (Input Field: Numeric) Customer, Delivery Location, Contents (Input Field: Text) Delivery Condition (Drop-down List) Date, Time (Input Field: Date or Time) Customer Approval / Signature (Signature Field)
Sample

Time Sheet

Description	This driver form implements a simple clock-in or clock-out timesheet. The driver sends the form twice, once at the beginning of their shift to clock-in and one at the end to clock-out.
Form Fields	Information Included: Driver, Date, Time (Magic Field) Punch (In/Out), Job Code, Route, Notes (Drop Down List and Text Field)
Sample

Trip Report

Description	This form can be used as a summary or completion report for the driver.
Form Fields	Information Included: Trip #, Billing # (Input Fields: Numeric) Start Time, Stop Time (Input Fields: Time or Date) For each intervening stop: Route / Location (Input Field: Text) Arrival and Departure Times (Input Fields: Time or Date) Odometer (Input Field: Numeric) Miles (Input Field: Numeric)
Sample

Work Order

Description	This form can be used as an operator’s report of work completed on a jobsite.
Form Fields	Information Included: Order # (Input Field: Numeric and Carry-over) Customer (Input Field: Text and Carry-over) Location (Input Field: Numeric) Arrival and Departure Times, Hours Logged (Input Field: Time and Date) Description of Work Done (Paragraph Text) Parts Repaired, Replaced, Required, Used, On Order (Input Field: Numeric, Text, Dropdown List)
Sample

Form Creation Notes And Instructions

These are a basic outline of how forms are created and the rules used in form creation. For further questions or ideas, contact zonar-configurations@zonarsystems.com

1. Forms are created graphically, dividing the form into a table of columns and rows.
2. All controls must be a minimum of one column and one row and cannot exceed twelve (12) columns and eight (8) rows.
3. In a standard format, the minimum size of a control must be four (4) to six (6) characters, depending on the size of characters used. If the column is expanded to twelve (12), the maximum characters per row is seventy (70).
4. Form messages can be exported to CSV or printed to PDF via the Ground Traffic Control interface.
5. Any field that is required should have an asterisk at the end of the static label associated with the field.
6. A signature captured on the tablet takes up twelve (12) columns wide by five (5) rows tall. It is viewed as an image on the dispatcher side. Signatures are not viewable in the CSV export.