As competition within the transportation and logistics sector heats up, telematics solution providers (TSPs), electronic logging device providers (ELDs) and commercial fleets are increasingly deploying commercial-grade tools to keep drivers safer and help them operate more efficiently on the road. Commercial navigation technology like CoPilot not only enhances safety and efficiency — it can help fleets avoid liability for bridge strikes and ensure compliance with posted roadway restrictions.
We recently launched a new CoPilot integration option for TSPs, ELDs and commercial fleets: a cloud-based CoPilot standalone app. It’s a fast and easy integration method that doesn’t require a significant investment of development resources or a lengthy deployment. It delivers CoPilot (plus map and software updates) via app stores and allows full dispatch integration. The cloud-based option is one of three CoPilot integration methods; the other two are CoPilot integration via CPIK Libraries or SDK App.
But how do you figure out which CoPilot integration option is right for you? That depends on your priorities, what mobile and server-side development resources you have available, and how fast you want to roll out your commercial navigation capabilities. Here’s a quick overview of the requirements and capabilities for each integration option:
|
Cloud-Based |
CPIK Libraries |
SDK App |
|
|
Mobile development work required: |
Minimal |
Extensive |
Extensive |
|
Server side development work required: |
Moderate |
Moderate |
Moderate |
|
Trimble MAPS team support needed: |
Yes |
Yes |
Yes |
|
Control and customization level: |
Some customizations within a standard foundation |
Highest level of customization |
Highly customizable |
|
Speed to release: |
Fast rollout |
Lengthier rollout |
Lengthier rollout |
The differences are based on how CoPilot is deployed. For the cloud-based option, CoPilot runs as a separate application. It can operate independently, but TSPs, ELDs and commercial fleets can expand its functionality by automating driver logins and using APIs to manage licenses, settings and routes. With this approach, fleets can send trip information to the driver’s device.
The CPIKLibraries method works by plugging a CoPilot API library into the partner application, which makes CoPilot a part of the application. With this option, users interface with CoPilot via the partner application; it isn’t available separately. CPIKLibraries offers the broadest level of customization, and partners can opt for a user experience that combines the interfaces of the partner app and CoPilot.
The SDK App option keeps the partner app and CoPilot separate, but CoPilot is controlled remotely by the partner. That means the partner app sends instructions, configurations and destinations to drivers via CoPilot and receives trip events and other data from the driver’s device. The partner can control app switching remotely to deliver a completely seamless user experience for drivers.
The developer pages for the cloud-based CoPilot standalone app, CoPilot CPIK Libraries and CoPilot SDK App have more detailed technical information, but here’s the bottom line: if you need a highly customized version of the CoPilot interface and have the time and developer assets to implement and maintain an SDK version, the CPIK Libraries or SDK App methods are probably the best choice.
But if you’re looking for a solution that gets commercial navigation capabilities to drivers more quickly and with minimal development work, take a look at the cloud-based standalone app. No matter which method you use to integrate, CoPilot delivers truck-specific navigation, improves last-mile performance and compliance, and provides post-trip insights that help commercial fleets operate more safely and efficiently. All you need to do is figure out which integration method works best for you.