System requirements

Web Browser

Supported browsers are:

Mozilla Firefox 21+

Google Chrome 29+

Opera 10+

Internet Explorer 8+

If you use a browser not mentioned above, Vertex IFMS may function incorrectly.

Click here to check if you are using a good browser.

Computer Capability

Computer capability affects browser operation. The key points of high performance are the CPU (Central Processing Unit) and RAM capacity. Multi-core processors do not affect browser operation in most cases. The exception is Google Chrome that can use more than one core in its operation.

Considering all above mentioned, the minimum requirements are:

CPU at 1.6 GHz clock rate;

512 MB of RAM.

and recommended requirements:

CPU at 2.4 GHz clock rate

(if Google Chrome is used as web browser, a processor with two and more cores is recommended);

2 GB of RAM.

Monitor size and screen resolution should be also considered. The bigger the monitor is, the more data is queried from server and processed by CPU. It is especially true for the maps and when the Internet connection is slow. The solution for big monitors is to not use browser in full-screen mode.

Antivirus software can slow down computer performance as well as gathering actual data from the vehicles. If Vertex IFMS is getting slower, you can add it to the list of exceptions or simply disable antivirus monitoring during Vertex IFMS session. You can also create a rule which allows Vertex IFMS to develop any activity.

Internet Connection

Vertex IFMS requires 1 Mbit Internet connection channel for one computer. If more than one operator will work simultaneously, do some tests and choose the most appropriate speed.

Furthermore, when working with Vertex IFMS, your IP address should not be changed within a session.

Optimization Measures

Here are some tips, which will help you to improve Vertex IFMS performance in cases when more than a hundred units are connected.

1. Web Browser

Web browser is very important. See the list of supported browsers above. The most efficient is Google Chrome. It is followed by Mozilla Firefox and Opera. The slowest, according to our tests, is Internet Explorer.

Vertex IFMS efficiency strongly depends on browser event system. Each browser has its individual event model. As the tracking system is rather dynamic and tracks change with up to 2-second delay, some browsers (like Internet Explorer) cannot process such a large quantity of events. The solution here is to use a more powerful computer.

2. Graphics & Tooltips

Graphic elements displayed on the map and in lists are resource-consuming. If you notice that your browser is getting slower, try to disable the mapping of the following elements: units, geofences, tracks, as well as names, direction arrows, and 'trails' for units (these elements are disabled with the three corresponding buttons in the bottom panel. Limit the number of units displayed in the Monitoring panel. Limit the number of other objects displayed on other panels that are frequently used (apply the filter for doing that). Enable only those elements that are necessary for your work at the moment.

If there are a lot of geofences or geofences composed of multiple points, then your browser could be severely overloaded. In such cases, disable the display of unused geofences.

3. Queries to Server

When Vertex IFMS starts, not all data is loaded at once. It is made to speed up the loading and operation. That is why some action that is done for the first time may take more time than for future work. Resource-consuming reports (such as reports on groups or reports with grouping and detailization) should be avoided for a long interval. Enclosed rows of detailization stay hidden until you expand them, and if there is a hundred or more enclosed rows, the browser may hang.

Limitations

Limits for logins and sessions:

No more than 10 unsuccessful logins from one IP address in a minute;

No more than 120 successful logins from one IP address in a minute;

No more than 100 active sessions of one user from one IP address.

If these limits are met, IP address will be temporarily blocked. It can cause difficulty to log in to the system.

Limits for reports:

2 minutes are allocated for online execution of a report;

When the timeout is exceeded, report execution will be aborted. That means the report will not be generated. In this case, diminish time interval or number of analyzed objects.

Other limitations:

No more than 3 heavy requests (e.g., report execution with a long interval) can be processed simultaneously in a session.