Note: Operations file containers are designed to keep you organized when tracking groups of Device in multiple locations. By breaking down tracking assignments into Operations, Devices can be independently displayed on the screen without clutter. In addition, once an Operation is create, all Device activities become a permanent record for future review and analysis.
In Application, an ‘Operation’ is a container used for a single tracking project. Operations connect specific Users, Devices, Data Sources, and Features so they can be assembled together into one operating unit. Your ability to create and access Operations depends on your permission levels.
Note: Devices and Data Sources can only be assigned to one Operation at a time. If your tracking Device is assigned to an Operation, other individuals (not assigned to the Operation) cannot see the Device or follow its activities.
Note: Once an Operation is created using the Operation Builder tool, it cannot be removed from Application unless officially archived.
You will need the following information before creating an Operation using the Operation Builder tool:
- Permission from your Administrator to edit Operations.
- A name for the Operation (required).
- A description of Operation objectives (optional).
- Planned dates for the Operation (optional).
- Supporting documents (such as a mission statement or plan/background/ orders/command contact list/and copies of warrants (if law enforcement) (optional).
- A list of Users who have permission to access the Operation.
- A list of the Devices and Data Sources to be deployed on the Operation.
- A list of Features and Feature Groups used to support Device tracking and deployment.
8.2 Creating an Operation
To create an Operation, start by opening Operation Builder and giving the Operation a Name. Then assign Users, Features, Attachments and Data Sources to the Operation. Start by:
- Opening the Menu > Views > Operations > +Add New Operation.
- In Operation Builder, enter the requested information. This must include a Name (required) for the Operation. How much more detail is entered depends on your security protocols.
Note: Use the Start Date/Time and End Date/Time with caution. In the future you will only be able to access Operational data that occurs within this date range.
- Enter optional Start/End dates for the Operation by clicking each text box to open Calendars.
Select a Start Date and a Start Time using the red slide bars next to Hour, Minute and Second.
Click NOW and then DONE, if the Operation starts now. Click DONE, if the Operation starts later.
- Set an End Date by clicking in the End Date/Time text box.
Select an End Date.
Select an End Time using the slide controls.
- Click NEXT.
8.3 Adding Users to an Operation
On the Users page, add the names of all personnel with permissions to access the Operation file you are building.
- Click the Pencil button in the upper-right corner to add names.
- Highlight,and then transfer(from the left column to the right) the names of all personnel with access the new Operation.
Click the arrow button under the left ‘SHOW ALL’ to make the transfers.
- ClickSAVEafter all names have been transferred.
- On thenextUsers page, verify the names on the access list.
Click the red (+) button again and re-enter information if changes are needed.
- Afterwards, clickNEXT.
Adding Users by User Groups
This feature is currently only available in E2, not Evolution.
Active Directory Users can now optionally be added to or removed from Cases by Active Directory Defined User Groups.
- When enabled, Operation / Case Builder will have an extra slide, Groups:
- Add and remove UserGroups to the Case / Operation using a familiar Modify Dialog:
- UserGroups are created and managed in Active Directory so AD integration is a prerequisite. By default, the UserGroups user interface is disabled and must be enabled via database configuration (dbo.Configuration: ConfigurationSection=”General”; ConfigurationName=”enableUserGroups” - “true” / “false”)
- UserGroups are added to a new Global Security Organisation Unit in AD that is located alongside the existing “Groups” and “Users” OUs.
- Note that the pre-existing “Groups” OU should not be confused with the new UserGroups.
- The default name for the new OU is “EvoUserGroups” but this can be configured in the database (dbo.Configuration: ConfigurationSection=”ActiveDirectory”, ConfigurationName=”userGroupOU”.
8.5 Adding Feature Groups to the Operation
Next, add the Feature Groups you want to add to the Operation. Once added, these map Feature groups can added or removed from your tracking map as needed.
- In the Features window of Operation Builder, click Feature Groups.
- Click theModifybutton in the upper-right corner.
- Highlight theFeature Groupsyou want to add to the Operation.
Click the right-pointing arrow under SHOW ALL to transfer the Groups to the Operation.
- Your transfersthen appear on thelist of Feature Groups now associated with your Operation.
8.6 Adding Ungrouped (Individual) Features
Ungrouped Features are individual geofences, boundaries or individual points of interest created by Users and displayed on the Base Map. (Ungrouped Features are more common than Feature Groups.)
- To add these Features to the Operation, navigate to Operation Builder.
Scroll down the menu on the left.
Click Features > Features (Ungrouped).
- In theFeatures(Ungrouped) window, click the red Modify icon in the upper-right corner to add these Features to the Operation.
Note: If you are just creating this Operation, specific Features may not have been created or added to your map. These Features can be added later.
- If you are not familiar with aparticularFeature, preview it before adding it to your Operation.
To preview an Existing Feature, click the drop-down arrow the text box on the left side.
- Highlightyour selection in the drop-down list. TheFeature will then appear on the right. Using map controls, zoom in or out of the map to get a perspective of the Feature’s size and location.
Click USE if you want the Feature added to your Operation.
Click CANCEL is you want another choice.
Note: If the Feature you selected is part of a ‘Grouped Feature’, it will not transfer when clicking ‘Use’. If nothing transfers, make another selection.
- Your selection(s) will appear under the right‘Included’ column.
Click SAVE after the transfer is completed.
- Verify theFeaturenames appear on the Features list for the Operation.
Afterwards, click NEXT at the bottom of the page to continue adding to your Operation,
or click FINISH to leave Operation Builder.
8.7 Adding Attachments to an Operation
To keep supporting documentation for your Operation in one place, add the documents to the Operation. The added attachments may include pictures of subjects, geographic intelligence, legal documentation, and historical files that might be needed as the operation matures. Take the following steps to add attachments to your Operation:
- Go into Operation Builder for the target Operation.
Click the ATTACHMENTS tab in the menu on the left.
Click the drop-down arrow to select a category filter for the attachment(s) you want to upload.
(In this example, an executive summary is being added to the file.)
- 2. Scroll down the filter list.
Left-click and highlight Operation.
Click the add (+) button.
Note: These file types are acceptable for uploading: gif, png, jpeg, pdf, csv, txt, doc, docx, ppt, pptx, xls, xlxs, mp4, avi, ogg, mp3, wav, ogb.
- 3. Selectthe type ofObject being uploading on the next attachment
Enter a Name for the Object (commonly called an attachment or item).
Upload the Object (attachment).
- On theAttachmentspage, look for the uploaded file.
Click the (+) button to add more attachments.
Click the Trash Can to remove unwanted documentation.
- ClickNEXTwhen uploading is complete to continue adding information to the Operation file,
or click FINISH to save your changes.