Third Party Integration FAQ
Everything you need to know about integrating to our GPS devices
Q. Please explain to me what do you mean third party integration?
Q. How do we go about integrating to your products?
Q. What kind of functionality can be achieved?
Q. What kind of interface is available for integrating our application to your products?
Q. What are the steps to initiating an integration?
Q. I have some specific questions.
Do you have a question not answered here? Ask Future Quest
1. Please explain to me what do you mean third party integration?
Third party integration basically means making our Fleet.NET wireless GPS family of devices work with another application. For example, let's say that you are a municipality and you already have extensive investments in city street maps with special utility layers, etc. You would like to track your public works vehicles, but would prefer to use your own maps and IT expertise. In this case you would be able to develop your own GPS tracking application and integrate it to our GPS devices. Or, perhaps you are a trucking company with a significant investment in a dispatch system, but you would like to add wireless dispatch to it with vehicle tracking. In this case, you would integrate to our CommVision portable data terminal, using our third party integration tools.
2. How do we go about integrating to your products?
The Fleet.NET family of devices use a wireless middleware layer called MidLink™ as their communications gateway. We have a full open API interface with excellent documentation that will allow your application to communicate with our devices, using MidLink™.
3. What kind of functionality can be achieved?
As you can see in the detailed information in this website, our selection of Fleet.NET devices provides a broad range of functionality. All of the features that you say may be used in our third party interface. This includes integrating job dispatch capability to your existing enterprise application, as well as full featured vehicle tracking with input monitoring, etc.
4. What kind of interface is available for integrating our application to your products?
The interface between your application and MidLink can either be an ActiveX or TCPIP interface. We have ActiveX DLL's available for VB6 and VB.NET environments, which makes the interface basically plug and play.
5. What are the steps to initiating an integration?
a. Contact our sales desk to arrange a detailed discussion on your integration requirements. At that time, we can give you an idea about pricing. Do not assume the pricing will be the same as is contained in our on-line quote tool.
b. Once you are satisfied with the hardware pricing and capabilities, we would have you execute an NDA.
c. Then, we will provide our API documentation and tools.
d. Support is provided during the integration period.
6. I have some specific questions.
We would be happy to answer any questions you may have. Send an email to:
If you have any further questions that have not been answered, please don't hesitate to contact Future Quest.
Watch a Brief Presentation on Third Party Integration
- Fleet.NET Vehicle Tracking System
- Introduction
- Internet Hosted Configuration
- Enterprise Configuration
- Overview
- Fleet.NET™ Features
- Fleet.NET™ Benefits
- Fleet.NET™ Options
- Choose Your Tracking Devices
- Cellular Phone Tracking
- Low Cost Vehicle Tracking
- Enhanced Vehicle Tracking
- Trailer & Asset Tracking
- Job Dispatch and Tracking
- Frequently Asked Questions
- Cell Phone Tracking FAQ
- Vehicle Tracking FAQ
- Trailer Tracking FAQ
- Map Operation FAQ
- Third Party Integration FAQ
- Third Party Integrations
- MidLink™ Wireless Middleware
- Downloads
- Brochures & Manuals
