Corp Ten International Proprietary
Last Reviewed: 2016-09-23
EVOLUTION ADMINISTRATORS GUIDE
Version 1.4
May 9, 2016
Corp Ten International
100 West Road, Suite 300
Towson, Maryland 21
Ph. (800) - 411-2675
Contents
Command and Control Capabilities 5
SYSTEM SOFTWARE AND COMPUTER REQUIREMENTS 6
THE ADMINISTRATIVE DASHBOARD 7
Configuring the Home Button 19
Adding the new Role to a User 26
Adding Permissions to Users 28
Creating Specific AFW Type Permissions for Users 34
Adding a Newly Created Role 39
Giving Additional Permissions to Users 40
Roles and Permission Terminologies 46
Viewing Imported Data in Advanced History 55
Scheduling Data Downloads on the Calendar 60
(This page has been left blank)
© Copyright 2016 Corp Ten International
Your use of this information is subject to the terms of your license agreement with Corp Ten International. Unauthorized access, use, or dissemination of this information is prohibited.
Corp Ten International makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Corp Ten International shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Corp Ten International. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for Corp Ten International products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Corp Ten International shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft, Windows®, and Internet Explorer® are registered trademarks of Microsoft Corporation.
Mozilla and Firefox are registered trademarks of the Mozilla Foundation.
OpenStreetMap is open data, licensed under the Open Data Commons Database License (ODbl).
Esri is a registered trademark of the Environmental Systems Research Institute Inc.
PRODUCT ADVISORY
The EVOLUTION tracking product is designed exclusively for national security organizations, government agencies and law enforcement groups. EVOLUTION is not intended to be a ‘consumer product’ and is not designed for consumer or household use. The product is designed for use by trained professionals, skilled in their trade and aware of the risks of such profession, including the risks inherent in the use of this product.
Note: All screen shots in this document are notational and may not reflect the latest configuration.
Note: Some sections of this document are still under development and/or may need updating to reflect recent product changes.
EVOLUTION OVERVIEW
EVOLUTION is a web-based tracking and analysis application that is part of an advanced intelligence system for tracking mobile Devices worldwide. The application is designed to work with almost any tracking unit regardless of manufacturer, type, capabilities or location. EVOLUTION can operate as a standalone system, or expanded to work with other applications using its plugin architectural framework.
Product Description
EVOLUTION’s tracking is based on Global Positioning Systems (GPS). GPS satellites transmit signals used by tracking Devices to calculate their locations. Once a Device identifies its own position, it periodically transmits that location back over satellite, radio, or cellular systems to a central UniTrac server. EVOLUTION is the new, modern user interface for UniTrac based server systems. UniTrac collects the reporting data and EVOLUTION displays the data locations as icons on maps.
Command and Control Capabilities
EVOLUTION also gives Users the ability to remotely communicate with and control devices using two-way over-the-air (OTA) command and control (C2) tools. In addition EVOLUTION can receive device Panic Alerts. This device option is used to notify Users and Operators of emergency or dangerous situations for personnel in the field. Some Devices with advance capabilities allow Users to respond directly to alarm Owners when in Panic Mode.
Other Capabilities
EVOLUTION can:
- Continuously archive device communications for auditing and playback.
- Re-create historical tracking records to provide advanced intelligence data.
- Import tracking data from outside data sources.
- Provide on-screen map measurement tools.
- Display multiple types of maps to identify points of interest for advanced deployment planning.
- Present 24 hour monitoring of geofences and boundaries with UI, text and email breach alerts.
- Allow multiple maps on-screen at one time to multiply Operation monitoring capacities.
- Cluster individual devices onto one map for easy monitoring.
- Import media events such as pictures and audio files sent from devices.
- Can go live to a URL address for additional monitoring capabilities.
- Provide administrators tools for auditing all activities of Users and the application.
- Provide a calendar tool for scheduling automatic data downloads from outside sources..
- Present multiple map overlays for customized on-screen mapping.
- Support map printing with multiple security identifications.
SYSTEM SOFTWARE AND COMPUTER REQUIREMENTS
Server Requirements
The following are the recommended for Evolution server hardware:
• Intel Xeon or equivalent processor, 2.4 GHz or greater, four cores or greater.
• 8GB RAM or greater
• 100Mb or greater internal network connection
• 1Mbps or greater available bandwidth to external network
• 1GB available disk space for Evolution application files
• 160GB or greater available disk space for Evolution database files.
• 10K RPM or faster enterprise-class internal hard disks, configured as RAID1 or RAID1+0 -or- an enterprise-class SAN/NAS solution offering a minimum 100 IOPS per operating environment/initiator recommended
Software Requirements
The following are the required software specifications for an Evolution server:
• Windows Server 2008 R2 or later, x64 recommended
• Microsoft SQL Server 2008 R2 or later, x64 recommended.
• Internet Information Services 7.5 or later
• Microsoft .NET v4.5
• Microsoft ASP.Net MVC 2.0
- Evolution cannot be installed on a domain controller.
- SQL Server must be configured for mixed-mode authentication.
Computer Requirements:
- 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor
- 2 GB RAM
- DirectX 9 graphics processor with Windows Display Driver Model (WDDM) 1.0 or higher
- Internet access to Internet Explorer v10+, Chrome v45+ or Firefox v41+
THE ADMINISTRATIVE DASHBOARD
Overview
The Administrative Dashboard contains tools to help Administrators set up and oversee many aspects of the application. It is where defaults can be added when first setting up the application, or when situations change that require default modifications. The Dashboard is also the home for an Audit Log that allows you to see every activity in the program as it is happening. The Log can also be an investigative tool to recreate past histories in the application.
Here is also where Users are given permission to see or not see parts of the application depending on security protocols. It is under Roles that individual types of User jobs are associated with certain permissions.
To see the Dashboard:
- Open the Menu > Administration > Dashboard.
- The menu on the left provides access to the following tools:
- AUDIT LOG --- An automatic tracking tool for every action taken in EVOLUTION. The tool provides detection of and response to unauthorized information processing or use.
- ROLES --- Gives Administrators the ability to create and assign Users various permissions ‘in bulk’ under one Role as related to their jobs or functions.
- USER --- Provides Administrators with a list all Users with access to EVOLUTION. Administrators can modify or change the access permissions of each User from this location.
- MAP CONFIGURATION --- Allows Administrators to select default map settings for the application, choose direction providers and geocoder suppliers, and set up URLs to those providers.
- CONFIGURE HOME BUTTON --- Allows Administrators to pre-set and save a certain point on the base map as a ‘home’ location. By saving the location, the map will always move to this area when the application is opened.
Audit Log
The Audit Log tracks and records all information processing and activities in EVOLUTION 24 hours a day.
Use the log to follow immediate and historical activities.
To see the log:
1. Open Menu > Administration > Dashboard > Audit Log.
2. Scan the log. If anything appears abnormal, left-click to highlight that listing.
3. Click the drop-down node on the left to open the history log.
4. Review the log as needed.
Roles
In the Roles section of the Dashboard, Administrators can create multi-permissioned User Roles and give specific permissions to a group or an individual basis. Here you can create Users roles that reflect the types of job individuals have while limiting access to other parts of the software.
The following is an example of how to create a new Role. The role will be called an ‘AFW Standard User’ role. It is for a new User that needs to have the same access in Evolution that they had when using the AutoFind Web tracking service.
Note: In Evolution each individual is classified by default as a ‘USER’ and are provided basic ‘User’ permissions. As User Roles expand the basic USER can be given added permissions.
Take the following steps to create the new Role.
1. Open the Evolution Menu > Administration > Dashboard >Roles.
2. In the Roles list, right-click any listing to open a shortcut menu.
Click Add New Role.
3. In the Role Permissions Editor, enter a Name and Description for the new role (which we call an AFW Standard User)
Click SAVE.
4. After clicking SAVE, the Permissions tab becomes visible on the left.
Click NEXT or click the PERMISSIONS tab to move to the next step.
5. Begin by assigning the new User role some basic Administrative privileges to match future responsibilities.
Click Administration.
Note: There are over 75 Permissions to choose from in the Editor. Use the chart in the next section for definitions and explanations for each permission. Once you have selected which permissions should be attached to a particular Role, assign that Role to others to eliminate having to go through the permissions process over and over again.
5. On the Administration page, click Edit.
6. In the Edit pane, select Features, Reports, Rules, Tree, Device Properties, and Workspaces.
Scroll down.
Skip over Read.
7. Click Other and scroll down.
9. Next, check give permissions to View Devices, View Permissions, View Workspaces, Send Command and Control, View Features, View Reports, View Rules and View Tree.
Click FINISH.
A notice appears verifying these new User Permissions have been saved.
10. Next in the Role Permissions Editor:
Skip Inventory (for future development)
Skip Reports (no changes needed)
Skip User Management (for future development)
Skip Case Management (no changes needed)
Skip User Management (a placeholder)
Skip UniTrac (a placeholder)
11. Click Command and Control.
12. Click Other.
13. Check the Select All box on the right to give the new Role full Command and Control capabilities.
Click FINISH.
(Skip Data Destruction)
14. You have now completed creating the new Role.
Click the X in the upper right-hand corner to close the Editor.
15. Take the following steps to add the newly created Role to a User or multiple Users.
Click USERS in the Dashboard menu on the left.
16. In the Users List, find the User you want to give the new role.
Right-click on the User listing to open a shortcut menu.
Click Modify User.
17. In the Roles Editor, verify ‘User Role’ is checked. (This is a default setting that is required)
Important: User Role must always remain checked. This setting provides recognition of a User by the Evolution application.
18. Check the newly created Role (AFW Standard User).
Click FINISH.
19. Repeat steps 15 -18 for each User you want to have the new permissions. These steps will save a lot of time when giving multiple permissions to a large group of Users.
End of Segment.
Users
Use this section of the Administrative Dashboard to Add, Modify or Delete User permissions.
- To add additional permissions, open the Menu > Administration > Dashboard > Users.
- User Permissions can be modified by right-clicking on a Username, then selecting Modify.
- If you want to add or delete permissions to someone who is a basic User, click PERMISSIONS.
- In this example we will give a standard User permission to read support documentation connected with the Cases they track on the map.
Click Case Management in the Permissions list.
- Click Read in the Roles Editor, then select Associated documents.
- Scroll down and click FINISH. The User now has permission to read the documentation, but not permission to alter it in any way.
Map Configuration
To change the default settings for Base Maps and Map Services, open the Menu > Administration > Dashboard > Map Configuration.
1. Under the General tab, select the map providers and map service providers you want using the drop-down arrows in each text box.
2. Click the URLS and TOKENS tab, then use the drop-down arrow to select your map Supplier
and change the URLS and TOKENS listed.
Click NEXT.
3. Next, select the map of choice to be your Base Layer choices for the application.
4. Your selections will appear as one of the choices for Base Layers on the map.
Configuring the Home Button
This Administrative option allows you to create a default ‘Home’ area on the map that is returned to each time the application is opened. The option allows you to always open in a particular hemisphere, continent, country, state, region or city or even a neighborhood. To set the default location:
- Open Menu > Administration >Dashboard > Configure Home Button.
- Click the ‘world’ icon in the map tool in the upper left corner.
- Using the maps tools and your mouse, reposition the map over the area you want
identified as your ‘Home’ area.
- Click SAVE at the bottom of the screen.
- To see if the map position saved, zoom out of the map area as far as possible.
- Click the Load button, and the map should zoom to your new ‘Home’ setting.
Setting Device Opacity
Under Development…
ROLES AND PERMISSIONS
Creating New User Roles
The following steps are used by Super-Administrators and Administrators to give individuals and certain groups permission to access parts of the Evolution application. Permissions can vary from simply tracking Devices on the map, to creating broad based Case Files. This can mean creating a digital User Role that will give new Users specific permissions to match their job responsibilities.
In the following example we will be create what is called an ‘AFW Standard User’ role for someone that wants to have the same accesses in Evolution that they had when using the AutoFind Web tracking service. A description of the Roles, Permissions and Terminologies can be found in the next section of this document.
Note: In Evolution each individual is classified by default as a ‘USER’ and are provided basic ‘User’ permissions. As User Roles expand the basic USER can be given added permissions.
Take the following steps to create a new Role in Evolution.
1. Open the Menu > Administration > Dashboard > Roles.
2. Right-click on the target Users listing to open a shortcut menu.
Click Add New Role.
3. In the Role Permissions Editor, enter a Name and Description for the new role (which will be called AFW Standard User)
Click SAVE.
4. After clicking SAVE, the Permissions tab becomes visible on the left.
Click NEXT or click the PERMISSIONS tab to move to the next step.
5. Next, to assign the new role some basic Administrative privileges to match future responsibilities.
Click Administration.
5. On the Administration page, click Edit.
6. In the Edit window, check Features, Reports, Rules, Tree, Device Properties, and Workspaces.
Scroll down and skip over Read.
7. Click Other and scroll down.
9. Next, check AFW type permissions like View Devices, View Permissions, View Workspaces, Send Command and Control, View Features, View Reports, View Rules and View Tree.
Click FINISH.
A notice verifies the new User Permissions have been saved.
10. Next in the Role Permissions Editor:
Skip Inventory (for future development)
Skip Reports (no changes needed)
Skip User Management (for future development)
Skip Case Management (no changes needed)
Skip User Management (a placeholder)
Skip UniTrac (a placeholder)
11. Click Command and Control.
12. Click Other.
13. Check the Select All box on the right to give the new Role full Command and Control capabilities.
Click FINISH.
(Skip Data Destruction)
14. You have now completed the procedure for creating the new Role.
Click the X in the upper right-hand corner to close the Role Permissions Editor.
Adding the new Role to a User
The next step involves adding the Role to the User.
15. Open the Menu > Administration > Dashboard > Users.
16. In the Users list, find the User you want to give the new role.
Right-click to highlight the User name.
Click Modify User.
17. In the Roles Editor, verify ‘User Role’ is checked. (This is a default setting that is required)
Important: User Role must always remain checked. This setting provides recognition of the User by the Evolution application.
18. Select the newly created Role (AFW Standard User).
Click FINISH.
19. Repeat steps 15 -18 for each User you want to have the new permissions. Using these steps will save a lot of time when giving multiple permissions to a large group of Users.
End.
Adding Permissions to Users
The following is for Super-Administrators or Administrators to update or add access permissions to individual Users of Evolution. This section explains how to give permissions to view, edit and modify various functionalities in Evolution.
Note: In Evolution each individual is classified by default as a ‘USER’ and are provided basic ‘User’ permissions. As a basic User role expands Users can be given additional permissions.
Take the following steps to add (or delete) Users permissions without having to create a new Role.
This process works best when changing only a few permission listings at a time. For large numbers of permission changes, consider making those changes by creating a new Role or several Roles with the proper permissions.
1. Open the Menu > Administration > Dashboard > Users.
2. In the Users list, select the User you want to give the added permissions.
Right-click on the User listing.
Click Modify User in the options menu.
3. In the User Roles Editor, verify that User Role is checked. This is a default setting and it should not be changed. If it is not checked, then check it.
Click NEXT.
Important: User Role must remain checked. This default setting provides recognition of a User by the software.
4. Click Administration to give the User more Administrative privileges. (There are 37 privileges types listed under Administration.)
5. On the Administration page, check Edit to give the User permissions to Edit certain areas in application.
6. In the Edit window notice that Features and Workspaces have already been checked by default as part of the original User Role permissions.
Now check a few basic Administrative permissions, such as the ability to edit or update Reports, Rules, and Device Properties.
Afterwards, skip Read permissions and scroll down to Other.
7. Under Other you will see View permissions, View workspaces and View features have already been checked. Here you may give the User the rights to View Devices on the map, View device reports, and View rules connected to Devices.
8. After checking additions in Other, scroll up and click SAVE CHANGES.
A notice verifies your User Permissions have been saved.
10. Next in the Roles Editor:
Skip Inventory (this is a placeholder for future development)
Skip Reports (no changes needed unless you want the User to see the locations of Devices)
Skip User Management (a placeholder)
Skip Case Management (no changes recommended)
Skip UniTrac (a placeholder)
11. Click Command and Control.
12. Click Other.
13. Check the Select All box to the right of Other to give the User full Command and Control capabilities over Devices and their functionality.
Click FINISH.
14. Looked for the Saved verification notice.
15. Click Device Data Destruction on the Roles Editor page.
16. Do not add or remove anything under Data Destruction.
Just click FINISH.
Creating Specific AFW Type Permissions for Users
The following procedure shows how to create a Role in Evolution to give Users permissions that match those of a standard AutoFind Web (AFW) user. The procedure allows Users familiar with AFW to see the same set of corresponding functions in Evolution as when using AFW despite that many of the terminologies may be new and different.
Note: In Evolution each individual is classified by default as a ‘USER’ and are provided basic ‘User’ permissions. As User roles expand the basic USER can be given added permissions. Or the User can be provided with an entirely new Role that has the needed permissions attached. That is the process we are using here.
Take the following steps to create a standard AFW Type role in Evolution.
1. Open the Evolution Menu > Administration > Dashboard > Roles.
2. In the Roles list, right-click to open the options menu.
Click Add New Role.
3. Enter a Name and Description for the new role in the Permissions Editor.
Click SAVE.
4. After clicking SAVE, the Permissions tab will become visible on the left.
Click Next or click the Permissions tab to the next step.
5. Next, assign the User some basic Administrative privileges to match previous AFW privileges.
Click Administration.
5. On the Administration page, click Edit.
6. In the next window, select Features, Reports, Rules, Tree, Device Properties, and Workspaces.
Scroll down and skip over Read.
7. Click Other and scroll down.
9. Next, select permissions for View Devices, View Permissions, View Workspaces, Send Command and Control, View Features, View Reports, View Rules and View Tree.
Click FINISH.
A notice appears verifying these new User Permissions have been saved.
10. In the Role Permissions Editor:
Skip Inventory (for future development)
Skip Reports (no changes needed)
Skip User Management (for future development)
Skip Case Management (no changes needed)
Skip User Management (a placeholder)
Skip UniTrac (a placeholder)
11. Click Command and Control.
12. Click Other.
13. Check the Select All box on the right to give the new Role full Command and Control capabilities.
Click FINISH.
(Skip Data Destruction)
14. You have now completed creating the new AFW Role.
Click X in the upper right corner to close the Role Permissions Editor.
--------------
Adding a Newly Created Role
15. Open the Menu > Administration > Dashboard > Users.
16. In the Users List, find the User you want to give the new role.
Left-click to highlight the Username, then right-click to open the shortcut menu.
Click Modify User.
17. In the Roles Editor, verify User Role is checked. (This is a default setting an is required)
Important: User Role must always remain selected. This setting provides
recognition of a User by the application.
Check the newly created role (AFW Standard User).
Click FINISH.
18. Repeat these steps for each user you want to give the new role.
Giving Additional Permissions to Users
The following is a step-by step guide for Super-Administrators wanting to provide Users with new or advanced access and permissions in EVOLUTION.
At the end of the update is a list of Roles and Permissions along with their definitions. This information may be useful when learning many new terminologies found in EVOLUTION.
Note: In EVOLUTION each individual is always classified by default as a ‘USER’ and are provided basic ‘User’ permissions. As User roles expand Users can be given additional permissions.
Take the following steps to set up EVOLUTION with new permissions.
1. Open the Menu > Administration > Dashboard.
2. Click USERS tab in the Menu on the left.
In the Users list, select a User you want to give the added permissions.
Right-click the User listing, to open a shortcut menu.
Click Modify User.
3. In the Roles Editor, verify that User Role is checked. This is a default setting and it should not be changed. If it is not checked, then check it.
Click NEXT.
Important: User Role must remain checked. This default setting provides recognition of a User by EVOLUTION.
4. Next, give the User some additional basic Administrative privileges as requested by current Users.
Click Administration.
5. On the Administration page, click Edit to provide the new Edit permissions.
6. In the Edit window notice that Features and Workspaces have already been checked by default from previous settings. Add to the list by checking Reports, Rules, Tree and Device Properties.
7. Skip over adding Read permissions and scroll down.
8. Click Other, and scroll down.
9. Under Other, notice View Permissions, View Workspaces and View Features have already been checked by default.
Check permissions for View Devices, Send Command and Control, View Reports, View Rules and View Tree.
(See next page for graphic)
Scroll to the top of the page and click SAVE CHANGES.
A notice will appear at the top verifying your User Permissions have been saved.
10. Next in the Roles Editor is Inventory.
Skip Inventory (a placeholder for future development)
Skip Reports (no changes needed)
Skip User Management (a placeholder for future development)
Skip Case Management (no changes needed)
Skip UniTrac (a placeholder)
11. Click Command and Control.
12. Click Other.
13. Check the Select All box to the right of Other to give your User full Command and Control capabilities.
Click FINISH.
14. Looked for the Saved verification notice.
14. Click Device Data Destruction on the Roles Editor page.
15. Do not add or remove anything under Data Destruction.
Just click FINISH.
16. You have now completed the modification of Evolution to give a User
additional permissions to operate in the application.
Roles and Permission Terminologies
(Updated 05-09-2016)
ADMINISTRATION:
|
|
User Role |
This default setting is for all Users of Evolution and provides basic application recognition and permissions to everyone. |
Tech User |
For Users that provide technical support. Each User can create, update and delete Cases and see all Devices listed in UniTrac. |
Super-Administrator |
Can perform all tasks in the Administrative suite including assigning roles and permissions, managing configuration settings and resetting User’s passwords. |
Case Administrator |
Creates, updates and deletes Cases. |
|
|
Permission to Edit: |
|
Case |
Edit primary mission files that store data on devices, planning, contacts, subject names, deployments, and other support documentation. Only an Administrator can give access to these files. |
Deployments |
Plans and/or actions that articulate the assignments, activities and disbursement of tracking devices, assets and manpower to accomplish a mission or operation. |
Features |
Digitally drawn objects on a map used to set boundaries and identify intelligence points-of-interest. Features are generally Geofences or User created objects. |
Reports |
Periodic responses sent from a Device to Evolution to identify its location and activity. |
Rules |
Actions Evolution takes in response to reports from a Device as it relates to a Feature. As example: A Rule is created to notify Evolution when a Device enters or leaves a newly created geofence or boundary. |
Subjects |
Actors or targets associated with a Case (mission or operation). |
Tree |
A directory of Objects and Devices a User has permission to view. |
Identifiers |
The warrant numbers issued by courts that may be associated with a Device being used on a Case. (Primarily for Law Enforcement) |
Application Configuration Settings |
Internal settings used by the application to operate and function properly. |
Device Properties |
Standard and optional internal settings a Device uses to operate and function. |
Permissions |
Access rights to users or groups of users. These rights control the ability of the Users to view or make changes to the contents of a file. |
Roles |
The assigned position of an individual in EVO such as a User, Administrator or Super-Administrator. For example: A Super-Administrator generally has unlimited access to all aspects of an application. |
Scheduled downloads |
Automatic downloads from Devices scheduled by an Administrator on the Evolution Calendar. This calendar is located in the Menu under Tools. |
Teams |
(Future feature – Not Yet Released)
|
Users |
Individuals who have access to and can operate within the Evolution application. |
Workspace |
The working areas of a computer screen. Users may create and edit as many workspaces as needed to support their Cases. |
Permission to Read: |
|
Application Audit Logs |
View audit logs that provide a digital trail on the activities of a Device |
Application Configures Settings |
Read, investigate and troubleshoot configuration settings |
Other Permissions: |
|
Use Secured application diagnostic tools |
Check or debug the application |
Import external data files |
Import generic and other types of data files |
View deployments |
View deployment of Device activities in a Case file |
View devices |
View Device reports and Device properties |
View permissions |
View permissions given to other Users to read or access certain files |
View Roles |
View Roles and Permissions granted to others |
View scheduled downloads |
See the download calendar located under Tools in the Menu |
View teams |
Future Feature – Still Under Development - Not Released |
View Users |
Can see the list of individuals granted access to Evolution |
View Workspaces |
Can view their own workspaces and those of others on the same Case |
View Case |
Can see but not alter or update Case files (that required edit permission). |
View imported data |
Can view data after it is imported into Evolution |
Send command and control messages to devices |
Users can poll, change reporting times, check inputs/outputs, check battery status and even silence a device depending on its capabilities |
View features |
Can see all Features (or boundaries and geofences) assigned to a Case on the map |
View reports |
All Device reports can be seen by this User |
View rules |
Can view Rules attached to each Feature |
View subjects |
Can view the names of all subjects connected to an Case |
View tree |
Can see all Devices and Case assigned to them by an Administrator |
View warranted identifiers |
Can see the authorized numbers of a warrant as listed in the Case file of a Device |
REPORTS:
|
|
View location coordinates of device reports |
See the location of a Device each time it reports |
CASE MANAGEMENT:
|
|
Permission to Edit: |
|
Associated deployments |
Add, remove or edit deployments in a Case file |
Associated documents |
Add, remove or edit documents in a Case file |
Associated subjects |
Add, remove or edit subjects in a Case file |
Associated teams |
(Future feature –Not Released) |
Associated data sources |
Add or remove device and generic data sources from use |
Associated devices |
Add or remove devices from an Operation |
Associated features |
Can add, remove or edit a feature attached to a device |
Associated summaries |
Can modify the summary page in Case Builder |
Associated users |
May add, remove or modify Users information on an Operation |
|
|
Permission to Read: |
|
Associated deployments |
Read deployment information in a Case file |
Associated documents |
View supporting documents in a Case file |
Associated subjects |
View Subjects information in a Case file |
Associated teams |
Read team correspondence and communications |
Associated data sources |
Read source data (such as spreadsheets) in a Case file |
Associated devices |
View device reports and properties |
Associated features |
View features supporting devices on the map |
Associated summaries |
Read Case and Case Builder summaries |
Associated users |
View lists of Users with permissions to see a Case file |
|
|
COMMAND AND CONTROL : |
|
|
|
Disable Device |
Allows users to perform commands to disable the device |
Get Configurations |
Depending on device capabilities, Users can activate specialized and advanced device functionality |
Enable/Disable Live Tracking |
Enables or disables live tracking on the device |
Record Media |
Sends commands that start video or voice recordings or take photos |
Send Texts |
Allows the use of SMS messaging panels to send SMS to the device. |
Poll |
Provides access to Device Control Panels to Poll devices as needed |
Set I/O |
User can select a variety of device inputs and outputs |
Reset Device |
Users can resent the device to factory defaults |
Download Logs |
Imports data logs from various sources |
Get Status |
Devices can be queried for status/system information |
Set Communication Modes |
Enables communications modes, such a GPS or GSM settings |
Configure Device Notifications |
Sets device based notifications and event triggers |
Set Geofences |
Create various size and shaped Geofences and boundaries |
Set primary rates |
User can access Device Control Panels to set primary situational reporting rates, depending on device capabilities |
Set Sleep |
User can set specific sleep times or stun times if the device capability is available |
IMPORTING BULK DATA FILES
Bulk Data Requirements
To upload device data into the application, you must have the following Administrative or User permissions.
1. Edit scheduled downloads
2. Import external data files
3. View scheduled downloads
4. View imported data
5. View other data source identifiers
6. View associated data sources
7. Read associated data sources
Using the Data Import Tool
The Data Import Tool imports Generic Device reports (GDR) and QML data formats. To import data:
1. Open the Menu > Plugins > Data Importer > Generic.
2. Click SELECT FILE to search for the file you want imported.
Using the drop-down arrow, select the target Cases name with which the file is to be associated.
Click UPLOAD.
Note: If the imported file data was produced by a Device previously provisioned in Evolution, but not assigned to an active Operation, you cannot import its data.
If the Device has not been provisioned, provisioning will create the Device and assigned it to the selected Operation.
3. A notice appears stating the data is uploading. Underneath a second notice will state the File has been successfully submitted.
4. Click the Notification Center icon on the Toolbar.
5. Click the Refresh button in the Notification Center at the bottom of the reports grid.
6. The uploaded .GDR file will now appear twice in the Subject column. The second report indicates the file has been submitted for Validation. The top report indicates the results of the upload are available for review.
8. Right-click on the Validation Message to highlight it.
Click Import or Discard Uploaded Data bar on the right to uploaded file.
9. On the Upload Response page you will see that 3 valid data file rows uploaded. Scroll down the page to locate the Import button.
10. Scroll down the page and click IMPORT.
A verification Notice will appear.
11. Refresh the Notification window.
12. A third message will verify the Import has been completed and accepted.
13. Right-click the report to highlight it and reveal the actual report on the right.
14. Open Menu > View > Tree.
15. Scroll down the Tree to find your imported file under the Operation’s Data Sources.
16. Right-click the file to open a context menu to either open the file in Advanced History or Import another file.
End of segment.
Viewing Imported Data in Advanced History
One way to view the imported data is to use the Advanced History Filter tool.
1. Open the Menu > Views > Reports > Advanced History Filter.
Select your Target Case or Operation using the drop-down arrow on the right in the text box.
Click the drop-down in the Target Devices text box and select the uploaded file.
2. Enter the Dates and Times that match those in the imported file.
Scroll down to Start Date/Time.
Click in the empty text box to open a calendar.
3. Click the highlighted date that appears when the calendar opens. (This search start date is what was entered when the file.)
Click DONE.
(See next page)
4. Click in the text box for End Date/Time to open its Calendar.
5. Click the highlighted date on the calendar.
Click DONE.
Note: This example is a small file that presents three generic device reports that were recorded in less than 2 seconds on the same day.
6. Click EXECUTE.
7. Click YES on the action notice.
8. Give the Report a Name as it relates to your Operation.
Click SAVE.
9. Using the drop-down arrow, Select the map where you want the data displayed. (Map 1 is the base or main map on the screen)
10. Afterwards two notices appear as the data is moving to the Advanced History Map.
11. On the Advanced History dashboard you will see the three reports listed at the top. The Device icon is located over the English Channel. (This is a rapid reporting device on a ship in the channel.)
12. On the Timeline below, display the data by manipulating the timeline.
Here you can see the three reports were generated by the device about a second apart.
End of section.
Exporting Bulk Data
1. To Export data, click the Quick Actions Icon on the toolbar.
Scroll down and click Export Data File.
2. Select how much of the file you want to export and what type of file you will be exporting.
(Either CSV or Excel).
Click FINISH.
3. To view the exported file, click Open (or Save).
3. The exported file will open as seen below.
Scheduling Data Downloads on the Calendar
To automatically download position reports stored in a device’s memory, use this procedure to set up an automatic download calendar. This procedure allows Administrators to update data on a regularly scheduled basis without User interaction.
1. Open the Device grid and identify your target device. Left-click the target device listing to highlight it then right-click to open a context menu.
2. Click Control Panel in the context menu.
3. Click Download… in the Control Panel.
4. Click Schedule Download.
5. To enter a Recurring download schedule, click the Start Date/Time drop-down arrow in the text box.
Use the calendar and the clock to schedule the first download.
Enter the number of times and information on how often you want the download to reoccur.
Schedule an End Date/Time to end the downloads.
Click SET.
6. A notice verifies the scheduling has been set.
7. To verify the schedule, open Menu > Tools > Calendar to see if the download is scheduled on the calendar.
Corp Ten International Proprietary
/
Comments
0 comments
Article is closed for comments.