Frequently Asked Questions

CONNECTIVITY

Through our hosting partner, Rackspace (www.Rackspace.com), FieldPro is hosted in a secure, fault-tolerant, Tier 1 hosting center with a 100% guaranteed Network and HVAC/Power uptime. In the event that your internet communications are interrupted, operations can be conducted using the FieldFX client in offline mode. Once communications is re-established FieldFX will synchronize the data collected while offline.

FieldFX is well-suited for use over slow internet connection. Our product implements highly-optimized compression algorithms that compress data at the server before it is sent to the end user. Our approach reduces the amount of data transmitted between the server and the end-user on average by more than 10 times. In most situations a 100 Kilobytes of data would be reduced to 10Kilobytes of data for transmission and then uncompressed once on the end-user's computer.

What does this mean to your users… the system runs faster, pages take less time to load and data synchronizations from the field to the office are 10 times faster than normal. If you have remote field operations in low-bandwidth areas such as offshore, rural areas or under-developed countries, FieldFX has you covered.

Due to the occasionally-connected architecture, FieldFX is ideally suited for this type of application. Your techs can synchronize their computer prior to leaving the office and have all of the data required to accurately perform and capture all of the job-related details while they are out of communications range. Once a data link is reestablished, FieldFX seamlessly synchronizes the techs data into the server and any data created on the server since the last sync will come down to the tech's instance of FieldFX.

COST

The FieldFX Software-as-a-Service subscription license is paid monthly and starts with a minimum package of 15 users.  A user is defined as a field or office employee that logs into either the Console or Mobile Application.  The Agreement is a 12 month term that renews annually.  Please contact Sales at 713-552-9250 or email  Sales@liquidframeworks.com for more information.

A user is anyone with an activated login account to FieldFX. You may delete/create users at any time - only the total number of activated users are counted for billing purposes. In other words, you may inactivate a series of users. Inactivated users incur no charge; however, the historical data related to an inactivated user remains available. We bill on the first day of the month for the respective month's service.

There is no additional cost for Maintenance and Support in the FieldPro Cloud.  The cost for Maintenance and Support is included with your monthly subscription.

Nothing.  The FieldFX Cloud environment is monitored, managed, maintained and upgraded by LiquidFrameworks.  You never incurr time or money for an upgrade to take place.  We handle all of that for you automatically and the cost is included with your monthly subscription.

DATA OWNERSHIP

We provide access to your data to you and your authorized user base exclusively.

Your data is not combined, aggregated, mined, or sold to third-parties by LiquidFrameworks.

SECURITY

FieldFX uses 128-bit RSA file-based encryption for the locally stored data. If one of your computers is stolen or lost, the local data on the device is unreadable by anyone without the FieldFX login username and password.

FieldFX uses a secure, role-based login mechanism that ensures only valid users log into the system, whether the unit is connected to the office or is running disconnected in the field.

Your administrator can easily disable users at any time with a single click. At that point, the inactivated user will no longer have access to any part of the system, regardless of their security roles.

Synchronization data is transmitted via 128-bit Secure Socket Layer transmission over password protected web services. This data is undecipherable and not-readable. Each time the FieldFX client communicates with the server-based web service, encrypted security credentials are sent to the service layer and validated against our security model.