Vision FAQs

Please refer to the Quick Start Guide.

Download PDF

Click on the link "forgot your password?" and enter a valid email address. A link will be sent to this email address with instructions on how to change your password.

When a unit is removed from a project it will remain in the project, Unit menu indefinitely but will be greyed out and shown to be in an Archived state.

All events posted to the project will remain in the project Event Menu even when the unit is Archived.

Event data cannot be deleted permanently, it can only be archived.

Download PDF

Please refer to Chapter 7.4.2 of the THOR Operator Manual, page 163, for more information.

The first time you must log in to Vision’s web interface at https://vision.instantel.com with the username and one-time password that you received from Instantel. Upon logging in, you must create a Company and set up the Web Service User Name and the Web Service Password.

The default Vision settings are always used unless overridden by individual projects that configured their project-specific settings. When you create a new project, you can choose whether that project will use the existing user name and password, or use a project-specific user name and password.

1. Click the Preferences tab.
2. Fill in the mandatory fields.
   1. Once you have created a Web Service User Name and the Web Service Password on the Vision web interface, they can be entered in THOR. Once THOR has established a connection it can upload data to your Vision account.
3. Click Test Connection to verify the web service link and click Apply to register the changes.

When you configure a project for Vision, you must choose whether the project will use the default Web Service user name and password set up in Preferences or a Project Specific user name and password. You can also decide that the project will not send any event data to Vision.

1. Click the Projects & Events tab
2. Click the Manage Projects button
3. Select a Project
4. Click the Edit Project button
5. In the Vision Settings field, select one of the following options:
   1. Disabled - Events will not be sent to Vision.
   2. Use Application Preferences Credentials - ACH sessions will send data to Vision using the default Web Service User Name and Web Service Password as defined on the Preferences page. 
   3. Use Project Specific Credentials—ACH sessions will send data to Vision using a Web Service User Name and Web Service Password specific to this project. When selected the two new fields must be filled in:
   4. Web Service User Name, type the project-specific user name and
   5. Web Service Password, type the project-specific password.

Send Data to Vision Using ACH

Before event data can be uploaded to Vision, ensure:

• You have a valid Vision license
• You have set up your Vision Web Service User Name and Web Service Password.
• You set up the unit to properly communicate with THOR.
• Auto Call Home is running 
• The ACH filter is set up to send events to Vision 

Set up ACH Filter to Send Events to Vision

1. Click the Auto Call Home tab.
2. In the Filter section, select a filter.
3. Click the Edit button.
4. Enable the Checkbox Send Events to Vision.
5. Click OK to validate.

Please refer to the attached pdf  "How to transfer event data from Blastware to Vision.pdf" for more information.

Download PDF

Some users manually collect event data from field installations and require a means of pushing these events to the Vision Server. It is possible to batch process up to approximately 500 events at a time using the Blastware Auto Call Home program following the steps below. Please note that Blastware PDF formatting looks different from the THOR or Vision PDF formatting done through ACH.

Step 1: Download and configure the Forwarding Agent. The Forwarding Agent download is available in the drop-down menu on the top right of the webpage.

Install the forwarding agent and run the software. Enter Group alias (Webservice username) and Group Password (Webservice Password).

Step 2: Setup the Auto Call Home reports as shown below and make sure you select the right measurement units and the right compliance is selected at the bottom.

Step 3: Open the Processing window in Auto Call Home located under the Test tab

Step 4: Select the Events from the file location you have manually saved the events on your system and click on the File Convert button (Note you can process up to 500 events using this tool, if you have large files you may have to process in smaller batches for the tool to work)

Step 5: You can view the files being created and processed to Vision from the Target directory selected in the Reports Options/Forwarding Agent. Once processed they will be moved to a Sent folder in the same directory.

Please refer to the attached pdf  "Instructions for Batch printing of Events.pdf" for more information.

Download PDF

These steps can be followed to download events as a PDF file using a date range filter with up to 1000 events at a time.

1. Login into Vision.
2. Select the Project you want to print the events from.
3. Click on the Custom Reports and create a custom report.
4. Name the report and description and save it.
5. Click on “View Project Event” on the Left Tab and select the date range for printing events.
6. At the bottom, select the report named in the 4th step and click on the print button.
7. Check the download even option and click on the Print button.
8. The download containing the events in the selected date range will start automatically, you can cancel the print dialogue box if you do not want to print the report.

Vision supports direct connection from remote units, thus removing the necessity to call into a host server in the office. This reduces the support and infrastructure costs associated with remote access applications.

An example of the modifications to a modem configuration is found below, the modifications to send to Vision are:

Destination Port: 8070
Destination Address: vision.instantel.com

Note 1. If you use THOR to control the unit with an active connection over TCP in the UNIT tab, Auto Call Home will not divert any data directly to Vision.

Note 2. To achieve Vision forwarding while using THOR, you must program THOR to forward it through THOR to Vision.