It is important to follow these steps in order to activate the Public Works feature in your database.
Collecting information
Ordering equipment
Configure the database
Route completion configuration
Complete Geotab documents
1-Collecting information
It is recommended to have a project manager to ensure the implementation and installations of the project.
Review List of Compatible Spreader Controllers
Have on hand the requirements for material management reports
Have list of snow removal areas available for import
If applicable, obtain list (GIS / shapefile) of roads
If not, identify snow removal areas in an area type
2 - Ordering products
You must order the following products in order to use the public works solution with a spreader controller:
GO9 device with applicable pricing plan, as required
T-harness, as required
IOX-WRKS
Controller specific integration cable
Integration cables are specific to the make and model of the spreader controller head.
To ensure that the proper integration cable is used, please refer to this guide: Public Works Controller Integrations
NOTE: The IOX-WRKS cable is required to obtain data from the spreader controller.
However, not all MyGeotab Public Works features require data communication via the IOX-WRKS cable. Therefore, the hardware requirements depend on your customer's needs.
3 - Database Configuration
Create a group called: Public Works
Create a zone type called: Public Works
Associate the fields with the type: Public Works
This ensures that public works specific zones are properly categorized for future reporting.
Add the Public Works group to all Public Works related vehicles and zones
Since Public Works configuration is a complex process of preparation, information gathering, configuration and installation, it is understandable that the above steps may be performed throughout the preparation process before and after installation.
4 - Geotab Service user account
IMPORTANT: Geotab's public works support team will create a service account as part of the public works process for any customer with spreader controllers.
This user account is for IOX-WRKS firmware updates. Dealers and customers should be aware of this user in MyGeotab - please DO NOT DELETE the following user account from your user list:
Name : mdmaccount
E-mail : mdmaccount@geotab.com
5 - Route Completion configuration
Warning: if you are using your existing zones please follow the steps in the document here rather than step 5 and 6 of this document.
The service group is a group that is automatically associated with a rule through the shapefile or zone upload process. Vehicles must be assigned to this group.
Once the shapefile or zone file is uploaded, the group selected during the upload process becomes a parent group for the route groups and the rest of the data grouping structure configured in the shapefile or zone file.
To create a group, follow these steps:
Go to Rules and Groups in the MyGeotab main menu.
Select Group from the drop-down list
Under the Group Tree page, navigate to a parent group.
Add a subgroup to the Enterprise Group and click Save.
NOTE: If multiple groups are needed for different tasks, they should not be under the same branch. Vehicles can be added to multiple groups at creation or later.
6 - Importing the GIS file (shapefile)
In case you use your own GIS tool to generate a collection of geospatial shapefiles (Shapefile) the file must contain the following elements:
Linear features representing streets,
Group of roads,
Route structure,
Route data,
Route segment names,
Route Segment Width (optional), and
Number of Passes Requirements (optional)
NOTE: The collection of route groups, routes and segments is imported into a service group in MyGeotab for use by route completion. If configured, optional data can also be imported.
The shapefile import process converts each line in the shapefile into a polygon with rounded ends and a configured width (or default width of 10 meters) on each side of the line. These polygons are Zones in MyGeotab and are grouped into Routes. These routes are then grouped into route group(s) based on the route and group data entered in each line segment of the shapefile by the client.
NOTE: All other custom attributes in the client geospatial shapefile are ignored by the shapefile upload process.
Geotab document
Public Works Controller Integrations [PUBLIC]
Winter Solution Install Guide [PUBLIC]
IOX-WRKS [PUB]
MODULE 1: Geotab Public Works - Detailed Solution Overview [PUB]
MODULE 2: Field Services Overview [PUB]
MODULE 3: Geotab Public Works - Technical Overview [PUB]
Public works documentation