Mindflow GPS Tracking Solution caters for large and small.

We can provide your business a tracking solution built on open standards.

• NO a Protocols and No Proprietary Messaging Format.
• NO Vendor lock in.
• Custom Features development and integration as required/defined by you.
• Network Efficient - Very Low Bandwidth, meaning Lower GPRS costs.
• Small footprint - will run on existing mobile phones.
• Service Hosting by us is default
  • Self Hosted Service can be arranged.
• Call Us to discuss why these points are so important for your GPS Tracking Solution.

We have the skills and capability to integrate into your existing infrastructure, be it Windows, Unix or Linux.

GPS Tracking Implementation  Mindflow offers a new GPS World Tracking Service in Australia for Companies and Individuals. To take advantage of this you need:  Mobile Phone PDA or Mobile Device Bluetooth or Inbuilt GPS Java enabled (contact us if you need help answering this) Phone Connection (Even Prepaid accounts Work!) Sign up to our Service... Use our Contact Us page or Call us for account enquiries. Access to a PC with Internet to look-up the dynamic maps and reports. Coporate Enterprise GPS Tracking Enquire about our custom GPS Tracking. We implement GPS Tracking to work within your Company requirements and existing systems.

GPS Tracking Solutions:

• Custom GPS tracking built on solid open standards solution.
• Custom integration into your existing infrastructure.
• No Proprietary code meaning you are not locked in with us.

Some of the features of our offering:

• Targeted Event Generation: Many devices on the market are designed simply to transmit copious amount of GPS data to a back-end server hoping that the server can make sense of the data that it is receiving. The problem with this approach is that it tends to result in higher data transmission costs for information which will never be used. A protocol used for mobile applications need to be able to provide the flexibility to generate only the events that are pertinent to the specific application.

• Network Efficient: Mobile devices typically have limited network connectivity, and in some cases data communication can be quite expensive (e.g. satellite). Because of this the protocol needs to be efficient in it's dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.

• Transport Media: Different mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.

• Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.

• Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.

• Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.

• Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to encapsulate the specific needs of the device.

• Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should easily support devices such as PDA's, mobile phones, GPS monitoring devices, and other OEM micro-devices.

• Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.

For further information contact us by Telephone, thank you.