View Attachment A — Oakland City Council, July 19, 2022 (part 3 of 3)

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Toolbar
At the top of the Edit Queries panel is the toolbar that contains the following controls:

New Saved Query
Adds a saved query to the Saved Query tree. The new saved query node is added to the same level as the currently selected node. If the selected node is the query group, or if nothing is selected, then the new node will be added as a level 1 node.

New saved queries can only be added when the Tree View is in use.

Cut Selected Saved Query
Cuts the selected saved query node and all of its children nodes; all of the nodes remain in place until pasted. The image of the cut nodes changes so that there is a visual way of determining the affected saved queries.

The cut button is only enabled when the Tree View is in use.

Copy Selected Saved Query
Copies the selected saved query node and all of its children nodes. When the saved query node is copied to the new location, the Query ID is changed to ensure that it is unique.

The copy button is only enabled when the Tree View is in use.

Paste
Paste the cut or copied nodes to the new location. The new location is determined based on the selected node in the tree. The list below outlines the checks that are preformed during the paste operation.

Query Group Selected
The cut or copied saved queries are pasted as a level 1 saved query and are placed at the top of an existing level 1 saved queries.

Level 1 Selected
Pastes the cut or copied saved query node as a level 2 with the selected node being the parent. The children of the pasted node are also cut or copied. Before the paste operation, there is a check to ensure the saved query node to cut or copy has no more than two levels otherwise there is an error message that prevents the operation.

Level 2 Selected
Pastes the cut or copied saved query node as a level 3 with the selected node being the parent. There is a check to ensure that the cut or copied saved query node has no children otherwise there is an error that prevents the paste operation.

Level 3 Selected
Pastes the cut or copied saved query node as a level 3 and has the same parent as the selected node. It is placed below the selected level 3 saved query node.

After the paste operation, the cut or copied node is expanded if it has children nodes and is selected. Also, the paste clipboard is cleared.

The paste button is only enabled when the Tree View is in use and there is a saved query node on the clipboard.

Remove Saved Query
Removes the selected saved query and its children nodes.

The button is enabled when there is a selected saved query node and when the Tree View is in use.

Move Up
Moves the selected saved query node up in the tree view; the movement is limited to the same level of the saved query.

The button is only enabled when the Tree View is in use, there is a selected saved query node and that node can be moved up.

Move Down
Moves the selected saved query node down in the tree view; the movement is limited to the same level of the saved query.

The button is only enabled when the Tree View is in use, there is a selected saved query node and that node can be moved down.

Page 31 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Move Left
Moves the selected saved query node up a level and also moves the node's children.

The button is only enabled when the Tree View is in use, there is a selected saved query node and that node is a level 2 or 3.

Move Right
Moves the selected saved query node down a level and also moves the node's children. One of the requirements of a level 3 saved query is that it has an attribute query. Consequently, when the saved query is changed to level 3, the saved query is required to have an attribute query.

The button is only enabled when the Tree View is in use, there is a selected saved query node and that node is level 1 or

2. When the selected saved query node has children, there is a check to ensure that the children will not become an unsupported level.

Find and Replace
Opens the Find and Replace dialog
that is used to search and edit saved queries.

Transfer Attribute Queries
Opens the Transfer Attribute Queries dialog that allows the attribute query to be copied from one format to another.

Verify Query
Opens the Verify Saved Queries dialog that tests the attribute query syntax.

Saved Query Details
When a saved query node is selected in the tree on the left side of the Query Editor panel, the details of the saved query are displayed on the right side. These details may be edited and are only saved to the tree when the Apply button is selected.

Outlined below are the parameters that can be edited for a saved query.

Name
Name of the saved query that is limited to 100 characters. A name is required but it does not have to be unique.

Query Grouping
The list contains all of the query groupings.

Query ID
The query ID uniquely identifies the saved query and is created when the saved query is first generated. The query ID cannot be edited.

Item has attribute query
When this checkbox is checked, the saved query has an attribute query. When there is no check, the saved query is only a folder and tabs at the bottom of the dialog that contain the attribute query are disabled.

The checkbox is disabled and checked when the details of a level 3 saved query are displayed. This is the case because all level 3 saved queries must have an attribute query.

When the checkbox is unchecked, the attribute queries for all of the formats are cleared and the controls are disabled.

When the checkbox is selected again, the queries remain empty.

Attribute Query
The Omega query database currently supports four formats of saved queries; personal Geodatabase, ArcSDE, Shapefile and File Geodatabase. Each of these formats has a tab where the attribute query can be viewed and edited. The active tab has its text in blue.

Each tab has an icon before the name of the format. This icon represents the status of the attribute query for that format. Outlined below are the different status and icon:

Valid query

Page 32 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Attribute query has been tested; it was both successful and selected at least one feature.

Valid query with warnings
Attribute query has been tested and it did not selected any records or the attribute query has not been tested; this occurs when there is no reference data for the format.

Invalid query
There is an error with the attribute query.

No attribute query
No attribute query has been provided for the format.

There are a number of tools available for creating the attribute query. These tools are accessed with buttons located on the attribute query tab. The tools are outlined below:

Error Info
When the Error Info button is selected, a message box is displayed that contains information on why the saved query had an error or warning.

The error information is created when the saved query is imported into the Omega query database or the last time the saved query was applied to the tree.

Clear
Clears the attribute query for the format.

Restore
Restores the attribute query to its state the last time the query was applied to the saved query node.

Verify
The Verify button checks the attribute query syntax and updates the icon on the tab that represents the status. The error information, accessed with the Error Info button, is not updated.

The Verify button is only enabled when the feature class for the format is referenced .

Build
The Build button opens the Query Builder dialog. The button is only enabled when the feature class for the format is referenced.

Apply Edits
The edits to the saved query are only persisted to the saved query node when the Apply button is selected. When the Apply button is selected, there are the following checks:
l Ensure that a name has been provided for the saved query. The name does not have to be unique. Invalid characters, which include single quotes and <> symbols, are replaced with an underscore. l The attribute query for all of the supported formats are tested. If there is a query that has an error with the attribute query, a message box is displayed and the saved query is not persisted to the saved query node.

An attribute query can only have an error when there is reference data. If the reference data is not set for a supported format, that format will receive a warning.

If the edit to the saved query passes the validation process, the updates outlined below are made. l The saved query node is updated with the new name.
l The saved query node icon is updated based on the status of the attribute query. l The error information for the saved query is updated. l The icons on the attribute query tabs are to reflect the status of the attribute queries.

Note: The edits to the saved query are not saved to the Omega query database until the Save button is selected.

Page 33 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Columns
The Saved Query Viewer that is used by Omega desktop applications allows saved queries to be displayed in either a tree view or a column view. Each view has similar functionality but organizes queries in a different fashion. The Columns panel is used to support the organization of the saved queries.

Query Viewer Columns
To enable the column view check the Support Column View checkbox.

The next step is to the specify the level 1 saved queries whose children are to be displayed in the columns by selecting the browse button that opens the Level 1 Saved Query dialog.

The Level 1 Saved Query dialog contains all of the level one saved queries within the current Query Group. The list excludes the saved query that has been specified for the other column.

Level 3 Saved Queries
Only the children, which are level 2 saved queries, of the level 1 saved query are displayed in the columns. If there are also level 3 saved queries, these saved queries will not be visible in the columns and there is a warning displayed with the Saved Query Viewer.

Missing Reference
When the level 1 saved query that has been assigned to a column is missing there is a red exclamation mark next to the text box that contains the name of the saved query.

The missing reference can occur when the saved query is deleted or changed from a level 1 saved query. In both cases, there is a warning message after the operation.

Exclude Saved Queries: Projection Analysis
The School Planner Projection Analysis routine has specific requirements on which saved queries are to be displayed to the user. Typically, the routine requires that those saved queries that specify grade are not to be displayed.

Level 1 saved queries and their children can be excluded. Use the Add button to open the Level 1 Saved Query dialog to add the saved queries to exclude.

Field Qualifiers
Field qualifiers are used to delimit the beginning and ending of a field name in an SQL query. Field qualifiers are typically used when the field name contains spaces. Each feature class format has different field qualifiers.

Use of Field Qualifiers
The field qualifiers are used in the construction of the SQL query with the following operations:

Importing from MS Access table
The field identified as the code field uses the field qualifiers when the SQL query is automatically generated, provided that the option to use the qualifiers was selected.

Query Builder dialog
The list of the fields includes the field name and the field qualifiers when the option to use the field qualifiers is selected.

Field Qualifiers Dialog
The field qualifiers are specific to each Query Group. The field qualifiers can by edited using the Field Qualifiers dialog.

This dialog can be opened from the following locations within the Omega Query Editor:
l Reference Data panel
l Query Builder dialog

Page 34 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
The Omega Query Editor contains default values for the field qualifiers. These default values are outlined in the following table:

Field qualifiers are limited to a single character. When edits are made to the field qualifiers, there is a check to ensure that a value is provided.

When reference is made to a new feature class, the Omega Query Editor checks with the workspace of that feature class and updates the field qualifiers values. The option to use the field qualifiers is not altered.

Import Query Group
Query Groups can be imported from an existing MS Access table instead of being entered manually. The parameters for the import process are collected through the use of a wizard. This wizard is accessed from the Query Groups panel .

The table requires the following fields:

Code
The code field contains the value that is to be searched for in the attribute query. This field can either be numeric or text. The code field is required.

Description
The description field is the text that describes the code and it is used as the name of the saved query. This field must be text or numeric and it is required.

Grouping
The grouping field is used to identify the query groupings.

Query Level
A numeric field contains the level of the saved query. The valid range of values is 1 through 3.

Order By
This field identifies the order in which the records should be sorted when imported into the Omega query database.

Import Query Group

1. Query Group destination
Select the destination of the Saved Queries that are to be imported from a table in MS Access. There are two options:

New query group
When creating a new query group, provide a name. This name is limited to 100 characters and must not contain any invalid characters which include the single quote and brackets ("<", ">").

During the import process there is a check to ensure that the name of the query group is not already in use within the Omega query database. When the new name is not unique, a unique name is automatically generated.

Append to existing query group
Select the query group in the Omega query database to append the new save queries to. The new saved queries are appended to the end of the existing saved queries. If query groupings are identified, these are in addition to an query groupings that already exist. The reference data that is identified overwrites any reference data that the query group may already have.

To move onto the next step in the wizard, select the Next button.

Import Query Group
Format Left Qualifier Right Qualifier
Personal GDB [ ]
ArcSDE ' '
Shapefile " "
File GDB " "

Page 35 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A

2. Source Database
Use the browse button to navigate to the MS Access database (*.MDB) that contains the source data being imported.

When the database is selected, select the Open button which then populates the list of tables to import.

It is not necessary for the MS Access database to be a personal Geodatabase. Any tables that begin with the "GDB_" prefix will be automatically excluded from the list of tables, as they are proprietary to the Personal Geodatabase data model.

Select the table that contains the information to import and select the Next button to continue with the wizard.

Import Query Group

3. Code and Description
Select the field that contains the code values and the description values that are to be used to generate the saved queries. These are required fields.

Code field
The code field contains the value that is to be searched for in the attribute query. The list of code field contains both numeric and text fields. If there is a field in the table named "Code", then this field is automatically selected otherwise the first field is selected.

The field type of the code field will determine what fields are available from the reference data feature class. When the code field is numeric, only numeric fields will be able to be selected as the query field.

Description field
The description field is the text that describes the code and it is used as the name of the saved query. The list of the description fields contains both numeric and text fields. If there is a field in the table named "Description", then this field is automatically selected otherwise the first field is selected.

Note: memo fields are excluded from the list of fields.

The import operation supports forcing the code or description values to upper case. This is done be selected the appropriate checkbox. For more complex calculations, use the tools in MS Access or ArcMap to make the updates before starting the wizard.

To move onto the next step, select the Next
button.

Import Query Group

4. Order By and Query Level (Optional)
Order By
The selection of the Order By field allows for the sorting of the saved queries when they are imported into the Omega query database. The Order By list is populated with all of the text and numeric fields that are found in the source table along with the " < None >" item that is selected by default.

When the Order By field is not used, the saved queries are imported based on how the records are stored in the table and there is no guarantee of the ordering of the saved queries. When an Order By field is identified, the saved queries are imported in ascending order (A to Z or 1 to 9).

Query Level
The Omega query database supports three levels of saves queries. The level of the saved query may be specified by selecting the Query Level field. The Query Level list is populated with all of the numeric fields that are found in the source table along with the "< None >" item that is selected by default.

When a field is selected in the list, there is a check to ensure that all of the values in the field are with the range of 1 through 3. When an invalid value is found in the field, a message box is displayed, the field is removed from the Query Level list and the "< None >" item is selected.

During the import process, there are the following additional checks:

Page 36 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
l The first saved query is given the query level of 1, no matter the value specified. l In order for a saved query to be level 3, the previous saved query must also be a level 3 or level 2. When this condition is not satisfied, the saved query is given the same level as the previous saved query.

When no Query Level field is specified, all saved queries are set to level 1.

To move onto the next step select the Next button.

Import Query Group

5. Query Grouping (Optional)
Query grouping is used in the construction of the SQL query when joining multiple saved queries. Those saved queries that have the same query grouping are joined together with the "OR" connector while different query groupings are joined with the "AND" connector. Typically, the saved queries that share the same query grouping query the same field in the feature class.

If the table being imported contains query grouping information, select the field from the list of numeric and text fields.

By default the "< None >" list item is selected; no query grouping information in the table being imported.

Grouping Name
When a query grouping field is identified, the wizard populates a grid with a list of the unique values found in the table for the query grouping field. A default name of the grouping is also provided in the grid. These names can be edited by typing directly into the cell that contains the name. The name is restricted to a maximum of 50 characters and it must be unique.

When the number of unique values found in the query grouping field is greater then the maximum number supported for a query group, which is 50, then there is a warning message at the bottom of the grid and the field will not be able to be used as the query grouping field.

If appending to existing query groupings, then there is a check during the import process to ensure that the query groupings names are unique among the existing names. When an imported query group name is not unique, the import operation automatically re-assigns a new unique name.

To move onto the next step in the wizard, select the Next button. Before moving onto the next step, the following is done when a query grouping field is identified:
l Checks to ensure that the query grouping names are unique. When a name is not unique there is a warning message.
l Replaces any invalid characters (including single quote and brackets <>) with an underscore.

Import Query Group
6 - 9: Reference Data
There are four steps in the wizard where the reference data is set and field mapping is done. Each of these steps is the same except there is a single step for each of the formats of the attribute query.

Reference Data
Reference data aids in the validation of the attribute queries during the import process and is used in the field mapping.

Use the browse button to select the point feature class.

Reference data is not required. When there is no reference data the query field must be manually entered.

When appending to an existing query group, the reference data selected will override the existing reference data; even

Page 37 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
for those formats where no reference data was selected.

Field Mapping
The grid at the bottom of the step contains a list of the query groupings along with the query field. The query field is used in the construction of the attribute query.

When no reference data has been set, the name of the query field must be manually entered. This is done by clicking in the query field cell and typing in the field name. When manually entering the field name the name is limited to 150 characters.

When the reference data has been set, the query field will contain a drop down list of the fields found in the feature class. If the field identified as the "Code" field is text, then the list of query fields is limited to those text fields found in the feature class. Conversely, the same is true when the "Code" field is numeric; only numeric fields are displayed in the list.

To move onto the next step, click the Next button. Before moving on, there is a check to ensure that a query field has been provided for each query grouping.

Import Query Group

10. Field Qualifiers
Field qualifiers are used to delimit the beginning and ending of a field name in a SQL query. Each feature class format has different field qualifiers.

To use field qualifiers for a specific feature class format, select the checkbox. Field qualifiers are limited to a single character. When edits are made to the field qualifiers to use, there is a check to ensure that a value is provided.

When reference is made to a feature class, the wizard checks the workspaces of that feature class and updates the field qualifiers values.

To move onto the next step, select the Next
button.

Import Query Group

11. Summary
The final step in importing a query group from an existing MS Access table is a summary of the information collected by the wizard.

Review the information to ensure that it is accurate and use the Back button to make any changes otherwise press the Run button to perform the import operation.

Import Query Group
Import Processing
After the parameters have been collected from the wizard dialogs, the Omega Query Editor will import the MS Access table as a new query group.

Saved Query Name Validation
During the import process the names of the saved queries are checked for the following:
l Ensure that a name is provided. When no name is provided, then the default name of "Required" is entered.

Page 38 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
l Invalid characters, include single quotes and brackets ("<", ">"), are replaced when an underscore.

Saved Queries Editor
NOTE: The Saved Queries Editor is no longer added to the Omega Data Manager toolbar by default as this tool has been replaced with the Omega Query Editor. The Saved Queries Editor is no longer being enhanced and will be removed from the installation at a future release.

The Saved Queries are shown in a tree format in the OmegaGIS routines. These queries are stored in the saved query database. This editor provides a way to create, import, and/or edit the saved queries. It is accessed from the Omega Data Manager toolbar in ArcCatalog.

When you open the Saved Queries Editor you will be prompted to do one of the following:

1. Create new saved queries
Start with a blank query tree and build the saved queries in the editor.

2. Import saved queries
Import saved queries from either an existing query.ini file or from an Excel template. The Utilities dialog will be opened.

3. Open existing saved queries
You will be prompted to open an existing saved query database. Then any changes can be made to the query tree using the editor.

Toolbar
The toolbar provides the following options:

Add: Select from one of the drop-down options.

Group: Adds a new query group to the tree.

On same level: Adds a new query on the same level as the selected query.

Down one level: Adds a new query under the selected query.

Edit Query: Opens the Edit Query dialog, where queries for shapefiles, personal geodatabases, and ArcSDE geodatabases can be created and verified.

Delete: Deletes the selected query.

Find: Enter the value to find in the text box.

Utilities: Opens the Utilities
dialog.

Save: Save the changes to the saved query database.

Select Database: Open an existing saved query database.

Open Help: Opens help for using this editor.

Right-Click Menu
Right-clicking on one of the queries gives the following options:

Rename: Rename the selected query.

Edit: Opens the Edit Query dialog, where queries for shapefiles, personal geodatabases, and SDE geodatabases can be created and verified.

Add: Select from one of the sub-options.

Page 39 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
New Query Group: Adds a new query group to the tree.

New query on same level: Adds a new query on the same level as the selected query.

New query down one level: Adds a new query under the selected query.

Move: Select from one of the sub-options.

Up: Move a query up in the tree.

Down: Move a query down in the tree.

Query Type: Select either Primary or Secondary. By default, all queries are Primary.

Delete: Delete the selected query.

Utilities
The Utilities dialog has 3 tabs:

Password
If you would like the saved query database to be password protected, select the option here and enter the password.

This password is needed anytime the saved query database is opened in this editor. A password is not required to use the saved query database in OmegaGIS.

Verify Queries
All queries in a query group can be verified here. Select the query group and the type of queries to verify. Then select an appropriate data layer. Any problem queries found will be written to a log file.

Convert Data
The saved query database can be created one of the following ways:

1. Import from a Query.ini file. The Query.ini file was used in previous version of Omega products. This can be imported into the Excel template or the Access database. From the Query.ini file, queries for both Shapefiles and Personal Geodatabases are created. From the SDE_Query.ini file, only queries for ArcSDE are created.

To import into the Access database, the old Query.ini file must be formatted to define the query tree levels.

These are defined by adding a pound sign (#) to the beginning of each query name. The number of pound signs designates which tree level the query belongs on. The query tree can only go 4 levels deep. See Figure 1 for an example.

Using the example in Figure 1, ‘RMS’ is the name of the query group, which will be on the first level. The query group cannot have an associated query. On the second level under ‘RMS’ is the ‘Part I Crimes’ category. On the third level under ‘Part I Crimes’ are the 8 types of Part I crimes. The first one is ‘Homicide’ and it is further broken out into sub types ‘Murder’, ‘Manslaughter - Vehicle’, etc. These sub types are on the fourth level.

To import into the Excel template, only a valid Query.ini file is needed. If the Query.ini file has not been formatted with the pound signs, it will import all queries onto the second level. You can drag and drop the queries onto the appropriate levels. See #2 for more information.

Figure 1. Importing Query.ini

Page 40 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A

2. Create in the Excel template and then import into the Access database. The Excel template provides an easy way to create and edit the query tree. (See Figure 2) However, the queries created in Excel cannot exceed 255 characters. If a query is longer than 255 characters, it will be cutoff when it is imported into the Access database.

Be sure to verify all queries after importing to check for any errors in the imported queries. See the Query Help worksheet in the Excel template for more information about creating queries using the Excel template.

Figure 2. Excel template

Page 41 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A

3. Using this Saved Queries Editor to create or edit the query tree. The query tree can be created using the toolbar or by right clicking on any item in the query tree. Queries can be entered for Shapefiles, Personal Geodatabases, and/or ArcSDE layers, since these feature types require different query syntax. The icons on the right hand side signify which type of queries are defined.

About Demographic Data Loader
The Demographic Data Loader is used to compile source census information used by both the Demographic Viewer and the Crime Rate Generator routines. The tool creates a Personal Geodatabase (.MDB), containing the census files downloaded from the ESRI website. For information on downloading census data from the ESRI website, read about Accessing Demographic Data.

To access the Demographic Data Loader, open ArcCatalog, click on the Tools menu, and select Extensions. Ensure the Omega Data Manager extension is checked. Select 'Customize' from the Tools menu; and from the Toolbars tab, choose the "OmegaGIS Data Manager".

The Omega Data Manager extension is protected from unauthorized use. At least one Omega Desktop product, such as the Omega Import Wizard, CrimeView, FireView or School Planner, must be licensed for the Omega Data Manager to be enabled.

Page 42 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Data Description
The Demographic Data Loader assembles census layers by joining a shapefile to a .dbf flat file. For each census boundary type (tract, block group or block), both a shapefile and flat file must exist. The shapefile contains the geographic extent for each boundary polygon in the layer. The .dbf flat file consists of the population statistics compiled by the U.S. Bureau of the Census. The files can be identified by their extensions; .shp for the shapefile, and .dbf for the flat file.

The two files are joined on a common field called STFID. If this field is missing from either file, the tables cannot join correctly. The STFID field contains values that uniquely identify each polygon in the shapefile and each record in the flat file. The shapefile consists of a record for each of the polygons making up the boundary layer. The .dbf flat file must have the associated statistical population data for each of the polygons to join correctly. In many cases, this file includes additional records that do not match any of the STFID values in the shapefile. These extra records however, have no effect on the outcome of the join, they are discarded if a corresponding polygon in the shapefile is not found.

At this point in time both the Demographic Viewer and the Crime Rate Generator tools work exclusively with the census data provided by ESRI. If the Demographic Data Loader is not used to assemble this data, it is important to read through all of the information provided about the data format of the resultant census files, in order to mimic their format so that these tools can be used successfully.

Data Dictionary
Detailed information is available from both the ESRI website and the U.S. Bureau of the Census about the files used in creating geographic census information. Browse the following sites for information on the spatial reference, distance units, data accuracy and the currency of the compiled information.

ESRI: http://www.esri.com/data/download/census2000_tigerline/index.html Census Bureau: http://www.census.gov/main/www/cen2000.html Demographic Data Loader Wizard
The Demographic Data Loader consists of a wizard made up of three dialogs. When all of the information required by the first wizard dialog is entered, the Next button becomes available, and the user may move on to the next dialog.

Creating the Personal Geodatabase
Selecting the Census Data
Summarizing the Results
Creating the Personal Geodatabase
The first dialog provides an option to either create a new personal geodatabase, or use an existing personal geodatabase.

If the existing personal geodatabase is selected, any feature classes already existing in the database are deleted.

Page 43 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Note that at this time, only personal geodatabases may be created or updated. The File Geodatabase format introduced at ArcGIS 9.2 is not an option. If creating a new database, only a personal geodatabase will be produced. If selecting the 'existing personal geodatabase' option, a warning will occur if a file geodatabase is selected.

Selecting the Census Data
Moving on to the next dialog, if the census files are all located in the same folder, and the original names have been retained, all of the text boxes on this dialog may be updated automatically simply by choosing the folder in which the data resides. Alternatively, these file names can be browsed manually.

Generally, three file names are available representing the three census boundary types; tracts, block groups and blocks.

The boundary files can be recognized by the file extension as well as the abbreviated names contained within the file name. For instance, *trt*, identifies census tracts, *grp*, is short for block groups, and *blk*, stands for blocks. Ensure that the correct file is placed the appropriate text box. If the incorrect files are entered, a warning will be issued on the last dialog.

Page 44 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
As a reminder, census data is accessed through the ESRI website. A detailed account of this procedure can be viewed within the Accessing Demographic Data section of the Demographic Viewer help.

Summarizing the Results
The final dialog provides a summary of the success or failure of the new census layers. For each file, census tracts, census block groups and census blocks a message states whether the process succeeded or failed. If the process succeeded, the number of polygons created is identified. If for any reason during the processing an error occurs, a warning is issued. A warning can be identified by a red exclamation beside the summary information.

Page 45 of 45 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh5896.htm Attachment A
Getting Help
Analysis using Geographic Information Systems (GIS) can be a complex process. The Omega Desktop suite of tools, created by The Omega Group, is designed to simplify this process but questions and issues can arise. There are a number of ways to get assistance.

Training
Product Documentation
Omega Customer Support
Training
Training is an essential component in maximizing an investment in technology. There are several training options outlined below:

Omega Training
The Omega Group provides training when the Omega Desktop project is installed at the client's site. The training focuses on using the routines included with Omega Desktop.

Omega Remote Training Modules
The Omega Group offers remote follow up training to existing clients through GoToMyPC software. The remote access software allows clients to dial directly in to the Omega Project Manager's computer and work with their own application. A few topics covered by the modules include 'CrimeView', 'Administrating a Application' and 'Geocoding'. Refer to The Omega Group's web site for further information.

Omega User Training Conference
The Omega Group has an annual training conference where the user can attend workshops and labs that focus on how to use Omega products. Refer to the Omega Group's web site for the date of the next training conference.

ESRI Instructor Led Courses

Page 1 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
An understanding of ArcGIS is necessary to use OmegaGIS efficiently. ESRI provides instructor led training courses in ArcGIS. Information on the different courses available can be found on the ESRI web site.

ESRI Virtual Campus
The ESRI Virtual Campus includes a series of self-pace courses that are offered through the internet. There are a wide range of courses, many of which are free. Information on the ESRI Virtual campus may be found at the ESRI web site.

Product Documentation
Omega's product documentation is a great place to find detailed information on each of the routines and tools provided with Omega Desktop. There are two important components to the documentation; the descriptions of each routine and tool, and the troubleshooting information available when a problem is encountered using Omega Desktop.

Descriptions of each Omega Desktop routine and tool are provided in the Help associated with the software. Clicking on any of the Omega Desktop Dialog Help buttons opens the Help directly associated with the routine or tool in question.

Within the Help documentation is a section called Troubleshooting. This section describes in detail the most common errors that may be encountered while using Omega Desktop software. Errors are identified by a unique number and the description that is issued during the use of the routine or tool. The Cause and Solution sections addressed for each Error are extremely informative, and should always be the first resource for problem solving when using Omega Desktop software.

Omega Customer Support
For those organizations that have a current support agreement with The Omega Group, customer support

Page 2 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
is another way to get assistance.

Phone: (858) 450-2590
Toll Free: (800) 228-1059
Fax: (858) 450-0239
Email: [email protected]
Web: www.TheOmegaGroup.com
When contacting Omega customer support, have the following information available:
l Your organization.
l The Omega Product. For example CrimeView.
l Software information:
¡ Operating System.
¡ ArcGIS version and service pack. This information is available from the Desktop Administrator. From the Windows Start button, select All Programs -> ArcGIS -> Desktop Administrator. The ArcGIS configuration information is displayed on the right side of the dialog. ArcMap and ArcCatalog must be closed before Desktop Administrator opens.

Page 3 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
¡ Omega Desktop version, service pack and build. The Omega Desktop Administrator applications contains this information.

NOTE:

The Omega Group can offer our highest level of support to those clients who maintain their own GoToMyPC accounts. This remote access software will allow our support staff to directly troubleshoot an application. For more information on GoToMyPC visit The Omega Group web site.
6000 to 2025: Demographic Viewer
This section contains error messages relating to the Demographic Viewer.

Error 6006 Loading the Demographic Viewer Dialog
Description
"Census geodatabase cannot be opened."
Cause
The census geodatabase houses the data layers that are used with the Demographic Viewer. On opening the Demographic Viewer, the table of contents is searched for census layers. The census layer found in this case has an invalid data source. The data source may have become corrupt, may now be missing or may be of the wrong data type.

Solution
Find one of the census layers in the table of contents. Ensure that the census layer data source is contained within a Personal Geodatabase (.MDB) and that the feature class is not corrupt. If all else fails, recreate the census feature classes within a new personal geodatabase using the OmegaGIS Demographic Data Loader available as an extension to ArcCatalog.

Page 4 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 6011 Loading the Demographic Viewer Dialog
Description
"Census data not found in the active data frame. Data must be registered as a census layer. Use the OmegaGIS Metadata Editor to ensure that census layers in the data frame are registered as 'Census_Block', 'Census_Blockgroup' or 'Census_Tract'"
Cause
In order to open the Demographic Viewer, at least one census layer must be contained in the table of contents. The table of contents was searched for census layers, but no layers were found.

Solution
Layers in the active data frame that are classified as census layers must have the following qualities:

1. The data source must be valid.

2. The registered type must be set to 'Census'.

3. The layer must be contained in a Personal Geodatabase (.MDB).

4. The layer must have a geometry type of polygon.

Ensure that any layer in the table of contents that should qualify as a census layer follows the requirements above.

Recreate the census data using the OmegaGIS Demographic Data Loader to ensure these
requirements are met.

Error 6012 Loading the Demographic Viewer Dialog

Page 5 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"There are no layers in the active data frame."
Cause
The active data frame does not contain any valid layers. The utility cannot be opened if there are no layers in the table of contents.

Solution
Add the census layers from the Personal Geodatabase (.MDB) that houses the census data to the table of contents.

Error 6014 Selecting a new Census Layer in the Demographic Viewer Description
"Census layer not found in TOC."
Cause
The census layer selected in the Demographic Viewer Census layer list box has been removed from the project, or is corrupt.

Solution
Close the Demographic Viewer and re-import the census layer into the project.

Error 6016 Creating a New Census Layer in the Demographic Viewer Description
"The selected field was not created in the new census shapefile. The field checker may have modified this field name to accommodate the 10 character maximum width of shapefiles. Change the field name

Page 6 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
to continue."
Cause
The new layer that is created by the Demographic Viewer is a shapefile. Shapefiles have a 10 character limit on the field name. When the new layer is created, the fields from the source file are run through a field checker. The field checker automatically shortens any fields over 10 characters.

If in shortening the field names, duplicate fields are created, the field checker renames the duplicate field.

For example, if the fields ObjectID_12 and ObjectID_1 are contained in the same feature class, the field ObjectID_1 is changed to ObjectID_2 after being run through the field checker. Changing the field name creates a problem because in generating the new layer, if the calculations were supposed to be based on the field ObjectID_1, it no longer exists.

Solution
This problem does not occur if the census data provided by ESRI is used and is compiled using the OmegaGIS Demographic Data Loader. Recreate the data using this utility available as an extension to ArcCatalog. To avoid recreating the data, open the feature class in ArcCatalog, and rename any fields over 10 characters in length before using the Demographic Viewer.

Error 6020 Loading the Demographic Viewer
Description
"No fields found to populate the field selection list"
Cause
Although the census layer in the table of contents may contain fields, they may not be valid for display in the field list on the Demographic Viewer dialog. If the routine does not find any valid fields, for the census layer found in table of contents, the utility will not be available.

Solution
In order to be included in the field list, a field must be numeric and cannot be an area or length field. In addition, the following fields that occur in the census data provided by ESRI are not included as they do not create viable results with the Viewer:

Page 7 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
l Med_age Median Age
l Med_age_M Median Age Male
l Med_age_F Median Age Female
l Avg_hh_sz Average household size
l Avg_fam_sz Average family size
l Hse_Units Household units
l Rural
l Urban
l Vacant
l ID
The Demographic Viewer is designed to work exclusively with ESRI Census Tiger Line files.

Download the census data from the ESRI website, and compile the data using the OmegaGIS Demographic Data Loader available as an extension to ArcCatalog. 7000 to 7025: Crime Rate Generator.

The error numbers in this section are for the Crime Rate Generator.

Error 7001 Loading Crime Rate Generator
Description
"There are no layers in the active data frame. CrimeRate Generator is unavailable."

Page 8 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The project does not have any layers in the active data frame.

Solution
Crime Rate Generator is based on layers that contain incidents of crime and census layers containing the boundaries on which the statistics are based. If no layers exist in the data frame, the Crime Rate Generator utility is disabled as there is no data to analyze.

Error 7002 Loading Crime Rate Generator
Description
"Census data not found in the active data frame. Data must be located in a personal geodatabase and must be registered with a 'census' metadata tag. Crime Rate Generator is unavailable."Census data not found in the active data frame. Data must be registered as a census layer. Use the OmegaGIS Metadata Editor to ensure that census layers in the data frame are registered as 'Census_Block', 'Census_Blockgroup' or 'Census_Tract'."
Cause
Census data may appear to be in the table of contents, however if it is missing the criteria of a census data layer, it is not considered census data.

Solution
Ensure that for each of the layers considered to be census data, the following criteria is met:

1. The layer must have a registered type of 'Census_Tract', 'Census_Blockgroup' or 'Census_Block'. The registered type can be set using the OmegaGIS Metadata Editor , available in
the Omega Data extension in ArcCatalog.

2. The datasource of the layer must be valid. A red exclamation mark indicates an invalid data source.

Page 9 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A

3. The layer must have a geometry type of polygon.

Error 7003 Loading Crime Rate Generator
Description
"Incident layers not found in the data frame. CrimeRate Generator is unavailable." Cause
On loading Crime Rate Generator, the table of contents was searched for layers identified as incident layers, but none were found.

Solution
Identify the layers in the table of contents that should be classified as incident layers. Ensure that the following criteria is met for each layer so that it can qualify as an incident layer.

1. The layer must be a feature layer.

2. The layer must have a geometry type of point.

3. The data source of the layer must be valid.

4. If 'Use Registered Types' is selected in the OmegaGIS Setup database, the layer must be
registered as one of the selected types.

5. If 'Exclude layers created by OmegaGIS...' is selected in the OmegaGIS Setup database, the layer must not have been created by an OmegaGIS routine.

Page 10 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 7012 Opening Census Personal Geodatabase in Crime Rate Generator
Description
"Census geodatabase cannot be opened. The file is not longer accessible or has been removed." Cause
The Census personal geodatabase is either invalid or corrupt.

Solution
Recreate the personal geodatabase using the OmegaGIS Demographic Data Loader available in the Omega Data extension within ArcCatalog.

Error 7019 Locating Selected Incident Layer in Crime Rate Generator Description
"Incident layer not found in TOC. Close form to reset layers." Cause
The table of contents was searched for the incident layer selected on the dialog but was not found.

The layer has either been removed, renamed or is invalid.

Solution
Close the Crime Rate Generator dialog to refresh the layer list. Re-open the dialog and select an incident layer from the list. Do not modify the names, or sources of the layers in the table of contents while the Crime Rate Generator dialog is open.

Error 7020 Locating Selected Census Layer in Crime Rate Generator

Page 11 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Census layer not found in TOC. Close form to reset layers." Cause
The table of contents was searched for the census layer selected in the Crime Rate Generator dialog but was not found. The layer has either been renamed, removed or is invalid.

Solution
Close the Crime Rate Generator dialog to refresh the layer list. Re-open the dialog and select a census layer from the list. Do not modify the names, or sources of the layers in the table of contents while the Crime Rate Generator dialog is open.

Error 7022 Applying Attribute Query in Crime Rate Generator Description
"Attribute query error. Ensure attribute query in query tree is compatible with incident layer." Cause
The attribute query selected from the Saved Queries Tree, or the query created by the Query Editor is incorrect. The syntax is invalid.

Solution
Select the query from the Saved Query Tree. Use the Edit button to open the Query Editor. Click the Verify button. If the query is unsuccessful it may be modified using the editor to create the correct syntax. The new syntax should be updated in the Omega_Query.mdb database where the saved queries are stored.

Error 7024 Field Name Changed in Crime Rate Generator

Page 12 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"The field was not found in the new census feature class. The field name may have been changed by the field checker when it was reduced to 10 characters to accommodate the maximum field width of shapefiles. The field name must be changed to continue." Cause
The result of the Crime Rate Generator analysis is a new census layer that contains crime rate statistics. The new layer is created as a shapefile while the format is based on the layer selected from the census personal geodatabase. During the creation of the layer, a field checking process ensures that all fields are within 10 characters in width, and there are no field name duplications.

In doing so, field names are sometimes renamed to accommodate this criteria.

If a field name selected on the dialog, happens to be changed due to this process, Crime Rate Generator will not continue.

Solution
Crime Rate Generator is designed to work exclusively with census data downloaded from ESRI and compiled with the OmegaGIS Demographic Data Loader. Since a standardized file format is required, it is recommended that any census files used for Crime Rate Generator be created using this utility. If the tool is not used, field issues can be avoided by ensuring that all field names within the census layers are unique and within 10 characters in length.

Error 7025 Loading the Crime Rate Generator
Description
"No population fields found for census layers. Crime Rate Generator is unavailable." Cause
A census layer was found, but it did not contain any fields that can be displayed in the Crime Rate Generator.

Solution

Page 13 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
In order to be displayed in the Population field list box in Crime Rate Generator, a population field must meet the following criteria:

1. The field must be numeric.

2. The field must not be an area or length field.

3. The field cannot have the 'objectID' field type.

In order to be included in the field list, a field must be numeric and cannot be an area or length field. In addition, the following fields that occur in the census data provided by ESRI are not included as they do not create viable results with the Crime Rate Generator:
l Med_Age
l Med_Age_M
l Med_Age_F
l Ave_hh_sz
l Ave_fam_sz
l Hse_Units
l Rural
l Urban
l Vacant
To create a census database with a standardized format that can be used by Crime Rate Generator, visit ESRI's
website, download the census data, and then create the database using the OmegaGIS Demographic Data Loader, available in the Omega Data extension in ArcCatalog.

Page 14 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
9000 to 9010: Demographic Data Loader
The error numbers in this section are from the Demographic Data Loader.

Error 9000 Creating a New Database
Description
"Database name already exists. Create new database name." Cause
A personal geodatabase of the same name as that entered already exists in the folder selected.

Solution
Create the personal geodatabase in a different folder or use a different name to ensure that a duplicate database name is not created.

Error 9003 Overwriting a Personal GeoDatabase
Description
"Overwriting database is unavailable on 'create new database' option" Cause
Access to the database is limited. Overwriting the database is unavailable.

Solution
Create a new database instead of overwriting the existing geodatabase.

Page 15 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 9004 File Validation
Description
"After the OK button is clicked, the Data Loader issues a warning message that the shapefile join field is not found."
Cause
The shapefile must contain a join field called 'STFID', if this field is missing, a warning message is issued.

Solution
Download the shapefile from the ESRI website again and ensure that the STFID field is within the attribute table of the shapefile.

Error 9005 File Validation
Description
"Dbase join field not found."
Cause
The dbase file must contain a join field called 'STFID', if this field is missing, a warning message is issued.

Solution
Download the dbase file from the ESRI website again and ensure that the STFID field is within the attribute table.

Error 9006 File Validation

Page 16 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Join fields are of different types. Cannot join tables" Cause
Both the shapefile and the dbase file must contain a field called STFID in order to be joined. In addition, the field types of these files must be the same for the join to be successful.

Solution
Download both the shapefile and dbase files again from the ESRI website. If the data is downloaded properly, both of these fields should exist in the correct format. 10000 to 10050: Exception Reporting
This section contains error messages for Exception Reporting and the Exception Report Viewer.

Error 10008 Creating the Exception Report Table
Description
"Join Field not found in layer. Exception Reporting cannot continue" Cause
The boundary layer field selected on the dialog when selecting boundaries by field value, is used to group the crime statistics for the final map layer. During the processing of the Exception Report, this field was not found in the boundary layer.

Solution
Close and re-open the Exception Reporting dialog. Select the boundary layer, and the 'By Field Value' option. The fields are refreshed when the dialog is opened again.

Error 10009 Loading the Exception Reporting Viewer

Page 17 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Exception reporting database not found. Run an Exception Report before attempting to use the Viewer."
Occurs when opening the Exception Reporting Viewer.

Cause
Exception Viewer is used to view the results of the Exception Reporting routine. When Exception Reporting is run an Exception Reporting database is created in the \Analyses project workspace.

The error is due to the fact that this database is missing.

Solution
Run an Exception Report routine before trying to open the Viewer. Exception Reporting is available from the Analysis button on the OmegaGIS Main Menu.

Error 10016 Loading the Exception Reporting Viewer
Description
"No datasets found in the exception reporting database. Run Exception Report routine to create datasets to view in the Exception Report Viewer."
Occurs when opening the Exception Reporting Viewer.

Cause
The Exception Report database does not contain any feature classes on which to base new Exception Viewer layers.

Solution
Run an Exception Report routine before trying to open the Viewer. Exception Reporting is available from the Analysis button on the OmegaGIS Main Menu.

Page 18 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10017 Loading the Exception Report Viewer
Description
"Cannot find ERViewer.xsl stylesheet in installation folder. Cannot continue." Occurs when opening the Exception Reporting Viewer.

Cause
The ER_Viewer.xsl file is required to view the metadata about each Exception Report available to the Viewer. The file was not found when loading the Viewer.

Solution
Seach the \program files\omegagis\desktop\style folder for the file er_viewer.xsl using Windows Explorer. If the file is missing contact The Omega Group to receive a replacement file.

Error 10019 Running the Exception Report
Description
"The boundary layer is missing from the XML tag. Cannot load previous boundary selection." Cause
To run an Exception Report routine, settings selected on the dialog are written to the project XML document. This error indicates that the process was interrupted and the boundary layer information was not copied to the file.

Solution
Re-open the dialog and run the routine again. If the project XML document has become corrupted, and the routine still does not run, go to the project workspace, and delete the project XML file from disk. This file is automatically created each time an OmegaGIS routine is run. The project XML file is identified by a name similar to MyProject.XML.

Page 19 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10020 Validating Exception Report Selections
Description
"The current incident layer is missing from the XML tag. Cannot load current incident layer selection." Cause
To run an Exception Report routine, settings selected on the dialog are written to the project XML document. This error indicates that the process was interrupted and the current incident layer information was not copied to the file.

Error 10021 Validating Exception Report Selections
Description
"The previous incident layer is missing from the XML tag. Cannot load previous incident layer selection."
Cause
To run an Exception Report routine, settings selected on the dialog are written to the project XML document. This error indicates that the process was interrupted and the previous incident layer information was not copied to the file.

Page 20 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10022 Validating Exception Report Selections
Description
"There are no boundaries selected in the XML tag. Cannot load boundary selections." Cause
To run an Exception Report routine, settings selected on the dialog are written to the project XML document. This error indicates that the process was interrupted and the boundaries on which to perform the analysis were not copied to the file.

Error 10024 Validating Exception Report Selections
Description
"A new layer name is missing from the XML tag. Cannot load the new layer name selection." Cause
To run an Exception Report routine, settings selected on the dialog are written to the project XML document. This error indicates that the process was interrupted and the name for the new layer was not copied to the file.

Page 21 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10026 Symbolizing New Layer
Description
"Defaultlegend.lyr file does not exist in the installation folder. Cannot continue." Occurs when using the Exception Reporting Viewer.

Cause
A default legend file called DefaultLegend.lyr is used to create the symbology for the new layer.

The file should be located in the c:\program files\omegagis\desktop\symbology folder. This message is issued when the file has been removed from this folder.

Solution
Contact your project manager to obtain a new copy of this file.

Error 10027 Selecting an Attribute Query
Description
"A query is not selected. Select a query to continue or use Cancel to exit." Cause
The Saved Query dialog is open to add a new query to the query list, but the OK button was pressed before a new query was selected.

Solution
Select a query before trying to return to the main Exception Reporting dialog, or use the 'Cancel' button to exit the form.

Error 10028 Creating the Project XML Metadata

Page 22 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Boundary layer does not have an objectID field or the layer is corrupt." Cause
The project XML file contains the settings selected on the Exception Reporting dialog that will be used to create the new map layer and report. The boundary layer selected for analysis was checked for an Object ID field, but the field does not exist in the layer. The ObjectID field is a required field that is created when the feature class is created. The field is used to uniquely identify features within the layer.

Solution
Right click on the boundary layer name selected and ensure that the layer has an ObjectID field. If the field does not exist, the layer cannot be used by the Exception Reporting routine.

Error 10031 Opening the Exception Report
Description
"The Exception Report cannot be opened. Check that it exists in the \reports folder; is a valid Crystal Report, and uses data in a table within a personal geodatabase." Occurs when the Exception Report is opened from the Exception Report Viewer.

Cause
An error exists with the Exception Report, and the report cannot be opened. The file may be corrupt, missing, or based on data that is not located in a personal geodatabase or not linked correctly.

Solution
Use Crystal Reports to open the report. Update the link to the data if necessary.

Error 10035 Validating the Exception Report Layers

Page 23 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"The boundary layer is no longer valid. Restart the routine to refresh." Cause
The table of contents was searched for the boundary layer selected on the dialog but was not found. The layer has either been removed, renamed or is invalid.

Solution
Close the Exception Reporting dialog to refresh the layer list. Re-open the dialog and select a boundary layer from the list. Do not modify the names, or sources of the layers in the table of contents while the Exception Reporting dialog is open.

Error 10036 Validating the Exception Report Layers
Description
"The previous incident layer is no longer valid. Restart the routine to refresh." Cause
The table of contents was searched for the previous incident layer selected on the dialog but was not found. The layer has either been removed, renamed or is invalid.

Solution
Close the Exception Reporting dialog to refresh the layer list. Re-open the dialog and select an incident layer from the list. Do not modify the names, or sources of the layers in the table of contents while the Exception Reporting dialog is open.

Error 10037 Validating the Exception Report Layers
Description
"The current incident layer is no longer valid. Restart the routine to refresh."

Page 24 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The table of contents was searched for the current incident layer selected on the dialog but was not found. The layer has either been removed, renamed or is invalid.

Error 10038 Loading the Exception Report Routine
Description
"No incident layers found in the active data frame. Exception reporting is unavailable." Cause
On loading Exception Reporting, the table of contents was searched for layers identified as incident layers, but none were found.

1. The layer must be a feature layer.

2. The layer must have a geometry type of point.

3. The data source of the layer must be valid.

Page 25 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A

4. If 'Use Registered Types' is selected in the OmegaGIS Setup database, the layer must be registered as one of the selected types.

5. If 'Exclude layers created by OmegaGIS...' is selected in the OmegaGIS Setup database, the layer must not have been created by an OmegaGIS routine.

Error 10039 Loading the Exception Report Routine
Description
"No boundary layers found in the active data frame. Exception reporting is unavailable." Cause
On loading Exception Reporting, the table of contents was searched for polygon layers but none were found.

Solution
Exception Reporting is based on boundary layers that form the geographic area used in the analysis. A boundary layer is classified as a layer with polygon geometry, and a valid data source.

Add boundary layers to the project in order to load the Exception Reporting routine.

Error 10040 Adding Query to Query List
Description
"Crime query is no longer valid for selected layers. Delete query to continue." Cause
Each crime query stored in the listview has a syntax attached. The syntax is related to the layer type, and is created when the query is added to the list. If the layer type has changed in any way, making the sql syntax invalid, this message appears.

Page 26 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Solution
The query is no longer valid for the layer. Remove the query from the list, and recreate the query using the 'Add' button.

Error 10041 Creating a Selection of Boundary Polygons
Description
"Selection field not found in boundary table."
Cause
The boundary layer field selected on the dialog when selecting boundaries by field value, is used to group the crime statistics for the final map layer. During the processing of the Exception Report, this field was not found in the boundary layer.

Solution
Close and re-open the Exception Reporting dialog. Select the boundary layer, and the 'By Field Value' option. The fields are refreshed when the dialog is opened again.

Error 10042 Opening the Summary Dialog
Description
"The stylesheet used to display summary information about the routine is missing. The file Omega_exsum.xsl must be located in the installation folder to continue." Cause
The stylesheet file called Omega_excsum.xsl is used to display information in the Summary dialog when a routine is run. If this file is missing from the OmegaGIS installation folder, an error occurs.

Solution
This file is installed when OmegaGIS is installed. If the file is missing from the c:\program files\omegagis\desktop\style folder, contact The Omega Group for a new file.

Page 27 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10045 Searching for the Exception Report Template Description
"The installation folder containing the exception report is missing. Ensure that the folder 'c:\program files\omegagis\desktop\reports\exception.rpt exists."
Cause
The Crystal Report template delivered with OmegaGIS called Exception.rpt has been deleted from the OmegaGIS installation folder.

Solution
In order to display Exception Report results in a report, the Crystal Report template called Exception.rpt must exist in the installation folder c:\program files\omegagis\desktop\reports.

Contact The Omega Group for a copy of this report if it is missing from the folder.

Error 10048 Validating the Selected Features
Description
"SQL syntax error. The values for the query do not exist in the query database." Cause
Saved queries are generated by creating SQL syntax for each feature class type that may be included in a project. Common feature types include: shapefile, personal geodatabase, or ArcSDE.

Each type has a unique SQL syntax that is used to query features. If the syntax required for the layer selected for the analysis is missing, this error is generated.

Solution
Check the data source of the layer in question. Open the Saved Query database using the Saved Queries editor. Ensure that the SQL syntax required for the data type is included in the Saved Queries database.

Page 28 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 10049 Loading the Exception Report Viewer
Description
"Error opening the ExceptionData.mdb file. Ensure ArcCatalog is closed and restart ArcMap." Occurs when opening the Exception Reporting Viewer.

Cause
The Exception Reporting database called ExceptionData.mdb is open in ArcCatalog. The Exception Report Viewer cannot load successfully with the database open.

Solution
Close ArcCatalog and restart ArcMap to reset the database.

Error 300110 Opening the Exception Report
Description
"Could not find the Exception Report."
Cause
The Exception Report that is opened when the checkbox is selected on the dialog is based on a file called Exception.rpt. This file could not be found by the Exception Viewer.

Solution
The Exception.rpt file must be placed in the project \reports folder in order for the Exception Viewer to find this file. If the file is missing, copy the file from c:\program files\omegagis\desktop\reports. and place in the project \reports folder. 11000 to 11010: Metadata Editor

Page 29 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
This section contains the error messages for the Metadata Editor.

Error 11000 Loading the Metadata Editor Dialog
Description
"An error has occurred loading the selected layer. The layer may be corrupt. Metadata Editor is unavailable for this layer."
Cause
The layer may be corrupt.

Solution
Recreate the layer to allow the Metadata Editor access to the stored metadata for the layer.

Error 11002 Using the Add Button on Reports
Description
"Report name already exists in list. Cannot add report name." Cause
The report name is already contained within the list. Duplicate report names are not possible.

Solution
Change the name of one of the reports to a unique name.

Error 11003 Opening the Saved Query Database

Page 30 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Error opening the query database. Ensure a valid query database is selected to continue." Cause
The Query Database is invalid. Either the format of the database is incorrect, or the database has become corrupt.

Solution
Ensure a valid query database is selected to continue.

Error 11004 Opening the Metadata Editor
Description
"The OmegaXSL stylesheet is not in the installation folder. The file must be installed in the following directory: * to be installed"
Cause
The OmegaGIS.xsl file provided in the c:\program files\omegagis\common\style folder is missing.

Solution
Contact The Omega Group to obtain a new OmegaGIS.xsl file.

Error 11005 Saving the Metadata Settings
Description
"Write permissions are unavailable for this account. See the database administrator to update the metadata."

Page 31 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The dataset selected is stored in ArcSDE and the connection used to access the dataset lacks write permissions.

Solution
Have the database administrator change the permissions on the layer, or have the database administrator add the metadata revisions.
13000 to 13010: Statistical Profiler
This section contains error messages for the Statistical Profiler.

Error 13001 Loading Statistical Profiler Dialog
Description
"There are too many shp_map shapefiles in the \analyses project folder. Clean up files to continue." Cause
If a layer type is selected as the output format for the statistical profile, a new shapefile is created in the project workspace \Analyses folder called spa_map* (where * is a number). The way in which the layer name is created is by iterating through the list of file names already created in the folder, and finding the next available file number. If after iterating fifty times looking for a new filename, one is not found, this error is issued.

Solution
Open OmegaGIS Setup
and select the General category. Click on the 'Project Clean Up' button to clear out the \Analyses folder of all of the shapefiles that are currently not used in the project.

Aside from the \Analyses folder, the 'Project Clean Up' button also cleans all OmegaGIS folders that contain files that are not in the current project.

Page 32 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 13005 Loading Statistical Profiler Dialog
Description
"An OmegaGIS date and time field must exist to run the date-time profiler." Cause
The Date-Time profiler is based on OmegaGIS fields created in the layer. An OmegaGIS date or time field was not found.

Solution
Use the OmegaGIS Metadata Editor available in the OmegaGIS Data Management Extension in ArcCatalog to check that the layer contains OmegaGIS fields. Create new OmegaGIS fields using the OmegaGIS Fields Manager, also available from the OmegaGIS Data Management Extension in ArcCatalog.

Error 13006 Selecting a Layer for the Statistical Profiler Description
"The layer selected is no longer valid. Reopen the dialog to refresh valid layer list." Cause
The layer was either removed or renamed in the table of contents, after the Statistical Profiler dialog was opened.

Solution
Close the Statistical Profiler dialog and re-open. The layer list is refreshed, excluding any invalid layers. Do not modify the table of contents while using the Statistical Profiler dialog.

Page 33 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 13007 Running the Statistical Profiler
Description
"No geocoded features were found within the recordset. Statistical profiler cannot be run." Cause
The data selected for the analysis does not contain any geocoded points.

Solution
The data may exist in the table, but it was not geocoded. The Statistical Profiler can only run on geocoded features.
14000 to 14015: Spatial Trend Analysis
This section outlines the errors messages with Spatial Trend Analysis.

Error 14000 Checking the Spatial Analyst Extension
Description
"Cannot Find Spatial Analyst License."
Cause
Spatial Trend Analysis requires the Spatial Analyst license. On searching for the license to open the routine, the license could not be found.

Solution
Spatial Analyst is an extension to ArcGIS, and must be installed and licensed separately. To check whether the extension is installed, click on the Tools menu item in the ArcMap toolbar. Select 'Extensions' and ensure Spatial Analyst exists in the list. If the extension is listed, ensure it is

Page 34 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
selected.

If the extension is missing, or the license is invalid, use the ArcGIS CD to re-install Spatial Analyst, and license the software.

Error 14001 Checking the Spatial Analyst Extension
Description
"Spatial Analyst License is unavailable."
Cause
Spatial Trend Analysis requires the Spatial Analyst license. On searching for the license to open the routine, the license could not be found.

If the extension is missing, or the license is invalid, use the ArcGIS CD to re-install Spatial Analyst, and license the software.

Error 14002 Checking the Spatial Analyst Extension
Description
"Spatial Analyst License is available, but is disabled." Cause

Page 35 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Spatial Trend Analysis requires the Spatial Analyst license. The license is installed but is disabled.

Solution
To enable the Spatial Analyst extension, click on the Tools menu item in the ArcMap toolbar. Select 'Extensions' and ensure Spatial Analyst exists in the list. If the extension is listed, ensure it is selected.

Error 14003 Checking the Spatial Analyst Extension
Description
"Could not find Spatial Analyst extension."
Cause
Spatial Analyst is not licensed.

If the extension is missing, or the license is invalid, use the ArcGIS CD to re-install Spatial Analyst, and license the software.

Error 14008 Selecting a boundary layer in Spatial Trend Analysis Description
"The boundary layer selected is no longer valid. Restart routine to refresh."

Page 36 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The boundary layer selected as the geographic layer for analysis has most likely been removed from the project, or is no longer valid.

Solution
Ensure that the boundary layer is still in the project, has the same name, and that the data source is valid. If the data source is invalid, a red exclamation mark is placed beside the name of the layer in the table of contents.

Error 14009 Selecting a Field in Spatial Trend Analysis Description
"The boundary layer selected in no longer valid. Restart routine to refresh." Cause
While updating the field values list box, the boundary layer is found to be missing or invalid.

Error 14019 Launching ClearAll with F11 from Spatial Trend Analysis Description
"Unable to run clear all. There is an installation problem." Cause
To clean up the project while Spatial Trend Analysis is open, the hot-key F11 can be used. The F11

Page 37 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
key launches the Clear All button, available from the OmegaGIS Toolbar in ArcMap. If a problem exists with the Clear All button, cleaning the project is not possible.

Solution
Contact The Omega Group to retrieve the appropriate files.

Error 14020 Setting the Layers for Spatial Trend Analysis Description
"No incident layers found in the active data frame. Spatial Trend Analysis is unavailable." Cause
During the setup of the Spatial Trend Analysis dialog, the table of contents in ArcMap is searched for layers that meet certain criteria for querying. To show up in the Spatial Trend Analysis dialog, a layer must meet this criteria otherwise the layer is not added to the list.

This error is issued if there are no layers on which to base Spatial Trend Analysis.

Solution
Identify the layers that should be used in a Spatial Trend Analysis, ensure they meet the following criteria:

1. The layer has a geometry type of point

2. The layer is a feature layer

3. The layer is not a selection layer. For example, the data source of the layer is not based on another layer in the table of contents.

Page 38 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A

4. The layer has a valid data source.

5. If 'Use Registered Types' is selected in OmegaGIS Setup, ensure the layer is registered with one of the types selected, or unselect the 'Use Registered Types' option.

6. If 'Exclude layers created by OmegaGIS...' is selected in OmegaGIS Setup, ensure the layer was not created by an OmegaGIS routine, or turn off this option.

Error 14011 Boundary Layer Selection Field in Spatial Trend Analysis Description
"Selection field does not exist in the boundary layer. Spatial Trend Analysis cannot continue." Cause
The field used to select polygons from the boundary layer is missing.

Solution
Open the Spatial Trend dialog, and select the boundary layer again. Select a field name from the list provided.

Error 14013 Map Units for Spatial Trend Analysis
Description
"The map units are not set for the active data frame. Spatial Trend Analysis cannot continue." Cause

Page 39 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
The map units are not set on the active data frame in ArcMap. The units are necessary for the Spatial Trend Analysis calculations.

Solution
Right click on the data frame and select properties. Select the General tab, and ensure that the Map Units are set.
15000 to 15050: Layout Metadata Editor
This section contains the error messages for the Layout Metadata Editor.

Error 15000 Opening Dialog
Description
"The active view must be a 'Data View' rather then the 'Layout View' in order to open OmegaGIS dialog."
Will not enable the tool until this issue has been resolved.

Cause
The active data frame is in layout view rather than data view. The data view shows the data in the map and hides the map layout.

Solution
Switch to active data frame to the layout view by selecting the button with the image of the paper at the bottom right of the active data frame

Page 40 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 15032 Setup Settings
Description
"Disclaimer not found in setup database."
Occurs when the Layout Metadata Editor dialog is opened.

Cause
The setup database has been expanded to accept many more settings than before. This means that new settings are referenced in OmegaGIS tools but might not exist in setup database used in previous products. This error is caused by the setting 'Disclaimer' not existing in the Setup.mdb.

Solution
Open the setup dialog either by opening the Main Menu and clicking the setup button or by opening it up through the tool bar. Once a setup database from a previous version is opened, it is automatically upgraded to the current version.
6701001 to 7800999
6701001 Dialogs in ArcCatalog
Description
"ArcCatalog must be restarted to use OmegaGIS. Ensure that ArcGIS Service Pack 1 is installed." Occurs when an OmegaGIS dialog is opened in ArcCatalog.

Cause
An error was introduced at ArcGIS 9.0 that prevents non-modal dialogs from opening in ArcCatalog.

Solution

Page 41 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
This issue has been resolved with Service Pack 1 for ArcGIS 9.0 that is available from the ESRI support web site. If Service Pack 1 for ArcGIS 9.0 has been installed, then restart ArcCatalog as changes to the registry have been made that require a restart of ArcCatalog to take effect. 7800102 Query and Density Dialog
Description
"The active view must be a 'Data View' rather then the 'Layout View' in order to open OmegaGIS dialog."
Occurs when the Query or Density dialog is opened.

Cause
The active data frame is in layout view rather than data view. The data view shows the data in the map and hides the map layout.

Solution
Switch to active data frame to the data view by selecting the button with the image of the globe at the bottom right of the active data frame
7800103 Query and Density Dialog
Description
"There are no Feature Layers in the active data frame; unable to open OmegaGIS dialog." Occurs when the Query or Density dialog is opened.

Cause
This error occurs when there are no valid feature layers in the active data frame. A feature layer is

Page 42 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
defined as a layer based on a feature class in a vector geographic dataset such as a geodatabase, ESRI shapefile or ArcInfo coverage.

A layer is not valid when the data source of the layer is missing. When the data source is missing the layer has a red exclamation mark in the table of contents.

Solution
l Change the active data frame to one that contains feature layers. l Add feature layers to the active data frame.
l Fix the issue that caused the missing data source.
7800211 Near a Feature Routine
Description
"The feature layer to be used with routine is no longer in the active data frame." Occurs when a layer is selected from the list of feature layers on the Where? tab for the Near a Feature routine.

Cause
The selected layer in the list of feature layers on the Where? tab for the Near a Feature routine has been
removed from the active data frame.

Solution
Close the query dialog and then add the layer back to the active data frame. Then open the query dialog again.

Page 43 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
780221 Near An Address Routine
Description
"The address was not geocoded."
This warning occurs when the Check Address button is selected while running the Near An Address routine.

Cause
The address entered could not be geocoded.

Solution
l Ensure that the address is spelled correctly.
l Alter the geocoding properties by reducing the spelling sensitivity or minimum match score. 7899226 Hot Spot Routine
Description
"Unable to use the Hot Spot routine; the Spatial Analyst extension must be enabled." Occurs when the Hot Spot
button is selected on the Density Map dialog.

Cause
The Spatial Analyst extension is not enabled. Information on which extensions are enabled is based on the current user logged into the machine, and is stored in the computers registry (HKEY_CURRENT_USER). When an extension is enabled all new or existing ArcMap documents have that extension enabled. If a different user logs into the machine, the Spatial Analyst extension must be enabled.

Page 44 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Solution
Enable the Spatial Analyst extension. To enable the extension, Spatial Analyst must have been installed and it must be licensed appropriately from ESRI. There are two ways to enable the Spatial Analyst extension:
l From the Tools pull-down menu in ArcMap, select Extensions. Check the Spatial Analyst extension. If Spatial Analyst is not available in the list of extensions, then it has not been installed. If the Spatial Analyst extension is not licensed there is a message box issued when the extension is selected.
l To automatically enable the extension, check the "All extensions used with OmegaGIS routines will be automatically enabled..." option in the OmegaGIS Setup dialog. 7800400 Date Range Validation
Description
"Invalid date range selected. FROM date (*) is greater then the TO date (*)." This validation error occurs when the Finish button is selected and all of the parameters of either a query or density map routine have been entered.

Cause
The FROM date (the beginning of the date range) that has been selected occurs after the To date (end of the date range).

Solution
Change the date range
selected ensuring the beginning of the date range is before the end date. 7800401 Boundary Layer Validation

Page 45 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"No features selected in the boundary layer (*)."
This validation error occurs when the Finish button is selected for the Incidents Within A Boundary , Hot
Spots or Repeat Calls routine.

Cause
When the "By Pointing" selection method is used to identify features in the boundary layer, the routine checks to ensure that there are selected features in the boundary layer. This error occurs when no features have been selected in the boundary layer.

Solution
l Select features in the boundary layer using the "By Pointing" selection method. l Use the "By Field Value" method to select features in the boundary layer.

Tip:

One way to determine how many features are selected in a layer is to use the Omega tab. 7800402 Date Range Validation
Description
"The query layer (*) has no information for at least one of the dates selected (* to *)." This warning occurs when the Finish button is selected for Queries and Density Maps routines. There is an option with this warning to continue to run the routine.

Cause
The FROM and TO calendars have the option to display the query layer’s available date range . When
the date range is displayed and either the beginning date or the end date selected is not within the query

Page 46 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
layer's available date range this warning occurs.

Solution
Either select "Yes" and continue to run the routine with the selected date query or "No" and alter the date query.
7800413 Feature Layer Validation
Description
"No items have been selected in the feature layer (*)." This validation error occurs when the Finish button is selected for the Near A Feature routine.

Cause
When the "By Pointing" selection method is used for selecting features in the feature layer, the routine checks to ensure that there are selected features. The error occurs when no features have been selected in the feature layer.

Solution
l Select features in the feature layer using the "By Pointing" selection method.
l Use the "By Field Value" method to select features in the boundary layer.

Tip:

One way to determine how many features are selected in a layer is to use the Omega tab. 7800420 User Defined Area

Page 47 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Invalid user-defined area; only one polygon graphic element can be selected in the active data frame, currently there are *."
This validation error occurs when the Finish button is selected for the Within A Boundary, Density Map, Hot Spot and Repeat Calls routine; and a user defined area is used to identify the spatial query.

Cause
Only one graphic element may be selected when using a user defined area . An element is selected when
it has handles around it's envelope.

Solution
l Select only one graphic element by using the Select tool in ArcMap. Make the Select tool active and then select the graphic element to be used with the routine. l Remove all of the graphic elements using the Clear All routine and then create a new user-defined area.
7800423 User Defined Area
Description
"Invalid user-defined area; the selected graphic element is a union of multiple polygons which is not supported."
This validation error occurs when the Finish button is selected for the Within A Boundary, Density Map, Hot Spot and Repeat Calls routine; and a user defined area is used to identify the spatial query.

Cause
The selected graphic element that is to be used as the user defined area has more then 1 exterior ring.

Solution

Page 48 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Remove all of the graphic elements using the Clear All routine and then create a new user-defined area. 7810000 to 7810500
7810120 Query Layers
Description
"Unable to find query layer(s): *"
This error occurs during the running of a Query or Density Map routine.

Cause
One or more query layers
could not be found in the data frame. The layer has either been renamed, removed or is not valid.

Another potential cause is that the layer name has trailing spaces. These trailing spaces are the source of the problem as the routine is searching for the layer by it's name without the trailing spaces.

Solution
l Close the Query or Density dialog and open it again. This will ensure that the list of query layers is updated based on the layers in the active data frame. With the list of query layers updated, select the appropriate layers and run the routine again. l Remove any trailing spaces from the layer name.

Page 49 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
7810124 Boundary Layer
Description
"The boundary layer '*' is not valid; check the data source of the layer." This error occurs during the running of a Query or Density Map routine.

Cause
The boundary layer data source has been moved, renamed, deleted or is currently unavailable. When the data source is missing the layer will have a red exclamation mark in the table of contents.

Solution
l Determine the problem with the data source of the boundary layer and make the necessary correction. One solution would be to remap the data source, this is done by selecting the Set Data Source button on the "Source" tab on the Layer Properties dialog. l Use a different boundary layer.
7810126 Boundary Layer
Description
"The boundary layer '*' could not be found in the data frame (*)." This error occurs during the running of a Query or Density Map routine.

Cause
The boundary layer could not be found in the data frame, the layer has either been removed or renamed.

Solution

Page 50 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Close the dialog and then open it again; the list layers to use for a boundary layer will be updated.

Select a boundary layer.
781028 Feature Layer
Description
"The feature layer '*' is not valid; check the data source of the layer." This error occurs when running the Near A Feature routine.

Cause
The feature layer data source has been moved, renamed, deleted or is currently unavailable. When the data source is missing the layer will have a red exclamation mark in the table of contents.

Solution
l Determine the problem with the data source of the feature layer and make the necessary correction. One solution would be to remap the data source, this is done by selecting the Set Data Source button on the "Source" tab on the Layer Properties dialog. l Use a different feature layer.
7810138 Near An Address
Description
"The geocoding service '*', cannot be found in the ArcMap document." This error occurs when running the Near An Address
routine.

Cause

Page 51 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
A geocoding service is required to run the Near An Address routine. The error occurs when the geocoding service is no longer referenced by the ArcMap document.

Solution
Add a reference to a geocoding service with the Geocoding Services Manager dialog. This can be opened from the Tools -> Geocoding pull-down menu in ArcMap or by selecting the Add/Remove button on the Where? tab for the Near An Address routine. 7810305 SQL Query
Description
"SQL syntax error when querying the layer '*' (*)."
The error occurs when running a Query or Density routine that uses additional query layers .

Cause
The error occurs when selecting the incidents in an additional query layer with a SQL attribute query.

The problem is with the syntax of the SQL query.

Solution
Check the syntax of the SQL query. ArcMap's Select By Attribute dialog is useful in determining the correct SQL syntax. If necessary, update the Saved Query with the OmegaGIS Saved Query Editor. 7810306 Additional Query Layers
Description
"No features have been selected. Unable to complete the routine." This error occurs when running a Query or Density routine that uses additional query layers .

Page 52 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
No features in the query layer and the additional query layer(s) satisfied the attribute and or spatial query.

Solution
Use a different attribute or spatial query and then run the routine again. 7810307 SQL Query
Description
"SQL syntax error when querying the layer '*' (*)."
This error occurs when running a Query or Density routine that does not use additional query layers.

Cause
The error occurs when selecting incidents in the query layer with a SQL attribute query. The problem is with the syntax of the SQL query.

Solution
Check the syntax of the SQL query. ArcMap's Select By Attribute dialog is useful in determining the correct SQL syntax. If necessary, update the Saved Query with the OmegaGIS Saved Query Editor. 7810308 Query Layer
Description
"No features have been selected. Unable to complete the routine." This error occurs when running a Query or Density routine that does not use additional query layers.

Page 53 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
No features in the query layer satisfied the attribute and or spatial query.

Solution
Use a different attribute or spatial query and then run the routine again. 7810415 Near An Address
Description
"Unable to geocode the address [*]."
The error occurs when running the Near An Address routine.

Cause
The address provided cannot be geocoded, consequently the Near An Address routine cannot be completed.

Solution
l Ensure that the address is spelled correctly.
l Alter the geocoding properties by reducing the spelling sensitivity or minimum match score. l Use the "Check Address" button on the Where? tab to determine if the address can be geocoded before running the routine.

Page 54 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
1100101 to 1100150: OmegaGIS Setup
This section contains the error messages for the OmegaGIS Setup dialog.

Error 1100102 Opening Dialog
Description
"This user does not have permisions to write to the Setup database." Error can occur when dialog is loading.

Cause
The Setup.mdb located in the project workspace lacks write permissions.

Solution
Open Windows Explorer and navigate to the project directory. Right-click the file Setup.mdb and select 'Properties' from the menu. If the 'Read Only' box is checked then click it off.

Warning 1100105 Processing Request
Description
"To use registered layers to make new queries, at least one registered type must be selected."
Error can occur when 'OK' or 'Apply' is clicked.

Cause
This warning occurs when in the 'Queries' Category on the 'Registered Types' tab the check box is checked but no vales in the list are checked.

Page 55 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Solution
Check the registered types in the list that will be used as query layers.

Warning 1100106 Processing Request
Description
"Some Threshold Alert recipient Email addresses reference the default SMTP server.

There is no default SMTP server set."
Error can occur when 'OK' or 'Apply' is clicked.

Cause
This warning occurs when in the 'Threshold Alert' Category emails are specified but no default server is specified. Each email must be associated with an SMTP Server. If there are no servers set then the emails are added to the default server. If no default server is set when 'OK' or 'Apply' is clicked then this warning will result.

Solution
On the 'SMTP Server' tab of the 'Threshold Alert' Category set one of the servers in the list as the default. This is done by selecting the server clicking the 'Edit' button and checking the 'Use this server as the default' box.
4100100 to 4100300: Threshold Alert
This section outlines the error messages for Threshold Alert. 4100112 Accessing the Threshold Alert Database
Description
"Release_Info table was not found."
Cause

Page 56 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
When threshold alerts are run, the project folder is searched for the threshold_alert.mdb database.

Within the database is a table called Release_Info that provides the major and minor release codes of the database. This information is important to determine whether the database is up to date with the release of the OmegaGIS software.

This error occurs because while searching for this information in the threshold_alert.mdb database, the table was not found.

Solution
Contact your project manager to either upgrade the database or modify the existing structure to work with OmegaGIS Threshold Alerts.
4100113 Accessing the Threshold Alert Database
Description
"Database is out of date."
Cause
When threshold alerts are run, the project folder is searched for the threshold_alert.mdb database.

If the major and minor release codes are not current to the release of the OmegaGIS software, this message is issued.

Solution
Contact your project manager to upgrade the database.
4100101 Accessing the Threshold Alert Database

Page 57 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Description
"Database file has not been set."
Cause
While the path to the Threshold_Alert.MDB database was being set, the path was lost.

Solution
The processing of the threshold alert was interrupted, and the database path was not completed.

Run the threshold alert again to update the database path. 4100102 Accessing the Threshold Alert Database
Description
"Database file was not found."
Cause
The threshold_alert.mdb database should be located in the root folder of the project. On searching for the database in this folder, the database was not found.

Solution
Find the threshold_alert.mdb database using Windows Explorer, and move the database to the project folder if required. Ensure the database is called threshold_alert.mdb. 4100103 Running Threshold Alert Automatically
Description
"Database password has not been set."

Page 58 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The program was interrupted when collecting the password information for the threshold_alert.mdb database.

Solution
The processing of the threshold alert was interrupted, and the database password was not set. Run the threshold alert again to update the password.
4100104 Running Threshold Alert Automatically
Description
"Database password is incorrect."
Cause
The password used to open the threshold_alert.mdb database is incorrect.

Solution
Contact your project manager, to ensure that the correct version of the threshold_alert.mdb database is in use.
4100202 Running Threshold Alert Automatically
Description
"Database password is incorrect."
Cause

Page 59 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
The password used to open the threshold_alert.mdb database is incorrect.

Solution
Contact your project manager, to ensure that the correct version of the threshold_alert.mdb database is in use.
4100600 to 4100700: Cyclical Reports
This section contains error numbers for Cyclical Reports. 4100610 Updating the Save Cyclical Dialog
Description
"Project XML file cannot be found."
Cause
The project XML file is not in the project workspace.

Solution
Run an OmegaGIS Query, Density or Analysis routine to recreate the project XML file. 4100611 Accessing the Setup Database
Description
"Error connecting to Setup database."
Cause

Page 60 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
An ADO connection is used to connect to the Setup.mdb in the project workspace. This error occurs when the connection fails.

Solution
The Setup.mdb database may be corrupt, or the table itself may be corrupt. Delete the setup database from the project workspace. It is recreated the next time OmegaGIS is run. 4100612 Accessing the Setup Database
Description
"Error connecting to table Omega_SetupLoc in setup database." Cause
The Setup.mdb database contains a table called Omega_SetupLoc that identifies the paths that should be searched for report templates, when a report is run. If a problem occurs while trying to access this table, this error is issued.

Solution
The Setup.mdb database may be corrupt, or the table itself may be corrupt. Delete the setup database from the project workspace. It is recreated the next time OmegaGIS is run. 4100637 Running a Cyclical Report
Description
"Unable to run Cyclical Report; the Clear All routine is not installed correctly." Cause
The Clear All routine is used to refresh the layers in ArcMap after a Cyclical Report is run. If this routine is not installed correctly, has become corrupt or is missing, this error is issued.

Page 61 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Solution
Reinstall OmegaGIS to refresh the Clear All routine.
4100638 Running a Threshold Alert
Description
"Unable to run Threshold Alert; the Clear All routine is not installed correctly." Cause
The Clear All routine is used to refresh the layers in ArcMap after a Threshold Alert is run. If this routine is not installed correctly, has become corrupt or is missing, this error is issued.

Solution
Reinstall OmegaGIS to refresh the Clear All routine.
470000 to 470100: OmegaGIS Field Manager
This section contains the error messages for the OmegaGIS Field Manager.

Error 470002 Duplicate Field Name
Description
"The field name is already contained in the dataset."
Before the Field Manager creates and adds the new field to the dataset, the dataset is searched for the field name entered in order to prevent duplicate field names.

Page 62 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Cause
The field name entered was found in the dataset. The field cannot be created.

Solution
Enter a new field name that is not already contained in the dataset.

Error 470001 Source Field Not Found
Description
"A source field no long exists in the feature class. It may have been removed or updated. Close the utility and reopen to refresh the list of source fields." The routine is validating whether the source field identified for creating either a Date or Time OmegaGIS field is in the selected feature class.

Cause
The source field to be used to create the new OmegaGIS Date or Time field could not be found in the selected feature class.

Solution
Close the OmegaGIS Fields Manager, and reopen. Closing the utility refreshes the list of available source fields.

Error 470002 Duplicate Day of Week Field
Description
"The name selected for the new Day of Week field already exists in the feature class. Enter a new name to continue."
The routine is validating whether the Day of Week field name selected already exists in the select

Page 63 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
feature class.

Cause
The Day of Week field name entered on the form already exists in the feature class. Duplicate field names cannot be added to the same feature class.

Solution
Enter a different name into the Day of Week field name text box on the form.

Error 470003 Duplicate Field Name in Metadata
Description
"A duplicate field name was found in the metadata. Open the OmegaGIS Metadata Editor on the selected layer, and click the 'OK' button in order to remove duplicate metadata."
The field manager is reading the metadata of the selected layer. A duplicate field name was found in the metadata. Layers cannot contain duplicate field names.

Cause
While the Field Manager was reading the names of the fields in the metadata, a duplicate field name was encountered. The Remove and Update field lists cannot contain duplicate field names.

The Field Manager will not load with duplicate field names in the metadata. has been registered as versioned. The Omega Import Wizard only supports the updating of non-versioned feature classes.

Solution
Use the OmegaGIS Metadata Editor in order to clean up the metadata of the layer. The Metadata Editor will remove duplicate field names generated in the layer's metadata. Open the Metadata Layer with the layer in question, and click the OK button to clean the metadata.

Page 64 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Error 470004 Missing Information
Description
"Unable to perform the test due to missing information. Ensure that the sample and format text boxes contain information."
The Test button was clicked in order to test whether the selected format matches the source information.

Cause
The Sample text box and the Format text box information are both required in order to perform the test. At least one of these text boxes on the dialog is missing information.

Solution
Ensure that both the Sample text box and the Format text box contain information that can be used to test whether the source data matches the format selected.

Error 470007 OmegaGIS Reserved Field Names
Description
"The new field name is an OmegaGIS reserved field name. Select a new name to continue."
The new field name selected by the user is a reserved field name used by OmegaGIS routines.

Cause
Before the OmegaGIS Fields Manager creates a new field, the field name is checked to ensure that it is not a reserved field name created by other OmegaGIS routines. The field name entered is found to be one of these names.

Solution

Page 65 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Enter a new field name that is not an OmegaGIS reserved field name.

Error 470009 Invalid Characters
Description
"The new field name contains an invalid character."
The new field name entered contains an invalid character, for example an apostrophe or pound sign.

Cause
Field names cannot include certain characters. A character that cannot be used with the dataset selected has been found in the new field name.

Solution
Create a new field name that does not include special characters.

Error 470010 Field Name Length
Description
"The new field name is too long."
Depending on the data type of the dataset, fields may have a length limitation. In this case, the field name entered has exceeded the allowable length.

Cause
The field name entered has exceeded the allowable field length for the dataset. The allowable field length may change according to the type of dataset selected.

Page 66 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Solution
Create a new field name that does not contain as many characters.

Error 470011 SQL Reserved Words
Description
"The new field name is a SQL reserved word."
The field name is a SQL reserved word. Standard SQL reserved words include 'SELECT', 'UPDATE', 'DATE' and 'TIME'. Other words may also be included in this list, but are dependent on the format of the dataset.

Cause
The new field name is a SQL reserved word and cannot be created in the dataset.

Solution
Create a new field name that is not a SQL reserved word. Read the ArcGIS documentation for an explanation of SQL reserved words.
8010000 to 8020999: Omega Street Network
This section contains the error messages for the Omega Street Network. The Omega Street Network is used to provide networking functionality and this is used by the FireView routines. 8020566 Summarize Running Order
Description
"Unable to summarize the running order. Ensure appropriate version of the JET engine is installed (Windows 2000, Service Pack 4 required). [*]"

Page 67 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
Occurs when a Cost Matrix is being generated.

Cause
The RunOrder field in the CostMatrix_* feature class is summarized and the results are placed in the RunOrder_Lookup_* table. The SQL functionality used to summarize the RunOrder field is the cause of the problem. The RunOrder field in the CostMatrix_* feature class has the Memo field type and there is an issue with the Microsoft Jet 4.0 engine and Memo fields. Refer to Microsoft Knowledge Base Article 304431 for more information.

Solution
l Install the latest Microsoft Jet 4.0 service pack.
l When the computer is running Windows 2000, install Windows 2000 Service Pack 4 as this contains a Microsoft Jet 4.0 service pack that will resolve the issue.

Page 68 of 68 ends

3/4/2022file:///C:/Users/onf4901/AppData/Local/Temp/arc896D/~hh2A00.htm Attachment A
(♦~ CENTRALSQUARE

TECHNOLOGIES
Cybersecurity Program Overview
The CentralSquare Cybersecurity Program implements a series of comprehensive physical and logical controls that align with the NIST Cyber Security Framework and standards to provide a secure, layered defense for all hosted information. CentralSquare maintains annual Payment Card Industry (PCI) and Statement on Standards for Attestation Engagements (SSAE18) compliance through a series of ongoing assessments and security testing performed by a PCI Qualified Security Assessor and AICPA auditor. Adherence to these standards ensures all controls are met specific to access, transmission, processing, and storage of data.
• Secure Software Development
• Vulnerability Management
• Incident Response
• Business Continuity
Management
• Government Cloud
• Regulatory Compliance
www. central sq r.com

POLICY&

CONTROLS INCDENT
MGMT
Attachment B
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Secure Software Development
CentralSquare implements secure coding best practices throughout the development lifecycle . Where supported , CentralSquare-developed applications undergo rigorous automated and manual testing and analysis . The lifecycle approach ensures that security is embedded into every application we develop .

Secure Software Lifecycle Management:
• Requirements & Design
Annual OWASP-based Developer training
Application Readiness Assessments to identify security gaps • Software Construction/Development
Developer IDE Code Analysis
Real-time feedback on coding best practices & potential security flaws • Deployment & Maintenance
Weekly Security "Scrum " with key stakeholders to address open security flaws Monthly review with Product Directors to address application security strategy & timelines Static Application Code Analysis
• Service: Third Party Independent Service
• Methodology
Binary code scan, executed during software construction stage of SDLC Performed in a non-runtime environment ; evaluates both web and non-web applications Inspect compiled versions for flaws , malicious code , back doors etc.

Risk-based approach to remediation
Dynamic Web Application Scanning
• Service: Third Party Independent Service & Internal Scan Utility • Methodology
Phase 1: Spider phase . Enumerate exposed funct ionality & attack surface Phase 2: Attack & detect exploitable vulnerabilities as the application operates Baseline derived from SANS Top 25 & OWASP Top 10 vulnerabilities Risk-based approach to remediation
Advanced Application Security Assessments
• Service: Third Party Independent Service
• Methodology
Penetration testing of web-based applications , executed testing/validation stage of SDLC Phase 1: Active & passive discovery including vulnerability scan Phase 2: Manual, authenticated assessment to identify logic flaws , privilege escalation etc.

Remediation required for all confirmed findings . Timeline dependent on severity + overall risk www.centra lsqr .com 2
Attachment B
o
o
o
o
o
o
o
o
o
o
o
Vulnerability Management
Scanning and Remediation
The CentralSquare Scanning and Remediation Program is a critical component of secure software development & maintenance . Through a holistic approach to vulnerability management, CentralSquare identifies and correlates application , network and system issues to ensure effective , timely remediation and resolution .

External Perimeter Scanning
• Frequency : Weekly, or Ad Hoc upon request
• Methodology
Detect & classify network and system vulnerabilities for all owned/leased/hosted IP ranges Remediation or Risk Acceptance required for all confirmed issues Remediation timeline dependent on severity + overall risk to the Business Unit Payment Card Industry Vulnerability Scanning & Penetration Testing • Service : Third Party Independent Service
• Frequency : Quarterly (Vulnerability Scan) & Annual (Penetration Test) • Methodology
Detect & exploit vulnerabilities as per PCI scanning requirements Segmentation testing to ensure logical separation of Card Data Environment Remediation required for external issues w/CVSS score of 4.0 or higher, to maintain PCI compliance Remediation required for internal issues identified as High or Critical, to maintain PCI compliance Advanced Network Security Assessments
• Service : Third Party Independent Service, performed by Depth Security • Frequency : Annual
• Methodology
Phase 1: Information Gathering , define attack surface
Phase 2: Cross-reference open services with known vulnerabilities Phase 3: Penetration test of network perimeter
Phase 4: Attempt to compromise target systems
Application & Scanning Vulnerability Remediation Process • Confirmed Critical vulnerabilities are driven to a 30 day remediation timeline • Confirmed High vulnerabilities are driven to a 60 day remediation timeline • Vulnerabilities are driven to remediation or risk acceptance, per prescribed timelines • Open vulnerabilities are reported weekly, with remediation plans updated bi-weekly www.centra lsqr .com 3
Attachment B
Incident Response
The Security Incident Response Policy establishes the steps needed to properly handle information security incidents, both suspected and actual, at CentralSquare . Incidents can include any event that could disrupt the confidentiality, integrity, or availability of CentralSquare systems and/or company and customer information .

Procedures for detecting and responding to incidents are in place and employees are aware of the appropriate escalation steps.

DETECTION
Signs of a security incident may be obvious or subtle. Electronic security incidents may not immediately appear to affect sensitive systems or information, but could occur in a supporting system that directly or indirectly allows access to this information . Thus, any unusual activity or irregularity to configuration of systems or applications can signify a breach. CentralSquare has multiple tools in place to alert on an incident, including but not limited to: Security Information & Event Managers (SIEM), Syslog, Intrusion Prevention Systems (IPS), Web Filtering Services, Web Application Firewalls, and Advanced Threat Protect Engines.

RESPONSE
• Assess the nature of the incident. Invoke the CentralSquare Playbook for Managing a Data Breach, if necessary .
• Determine if CentralSquare staff or customers are affected by the incident. If customers are affected, an immediate plan will be developed to mitigate the problem and notify affected individuals . If customers are impacted the CentralSquare legal team will be notified. • Determine potential signs of fraud. If fraud is suspected, the Human Resources and Legal departments will be notified .
• CentralSquare will notify impacted staff and customers within two business days (48 hours) of a confirmed incident.

REPORTING
In the event of a confirmed security incident, a detailed report is written that includes; • Affected staff, customers, data, computing systems, and other property • Response steps
• Root cause analysis

TESTING
The incident response plan will be tested annually via one of the following methods, unless already invoked during the current year for a suspected or actual incident:
• Table top exercise. Each employee will simulate their response based on the scenario given. • Simulated incident. Notify appropriate management staff in advance and schedule a date to begin test.

Establish protocols that will distinguish the test from a real security incident.

REVISION
The incident response plan will be refreshed on an as-needed basis, not to exceed 12 consecutive months. • After a confirmed incident, a lessons learned analysis will be performed with relevant policy revisions . www.centralsqr.com 4
Attachment B
• All plan revisions are reviewed and approved by management.

Business Continuity Management
The Business Continuity Management program (BCM Program) is a process designed to oversee the CentralSquare's ability to provide adequate business and technology recovery plans, capabilities to manage recovery of operations, identification of resiliency risks and rapid response during a disaster recovery crisis event.

All CentralSquare business functions develops, maintains and continually improves business continuity and disaster recovery plans. The purpose of these Plans are to:
• Protect life, information and assets of CentralSquare, respectively. • Conform to applicable regulatory, insurance and ethical business practices . • Support and be in agreement with the CentralSquare's tactical and strategic business plans. • Minimize the impact of Disaster on our clients, employees and the business associates to whom services are provided .

CentralSquare has a comprehensive BCM Program in place including . • Business Impact Analysis (BIA).
• Business Continuity Plan (BCP)
• Defined SLAs (Service Level Agreement), RTOs (Recovery Time Objective) and RPOs (Recovery Point Objective) .
• Annual Disaster Recovery tests and/or Tabletop exercises, to include validation of recovered environment. • Training and Annual Review
www.centra lsqr .com 5
Attachment B
Government Cloud Solutions
The CentralSquare Cloud Security Program ensures 24x7 availability, integrity, and protection of customer information by leveraging a multi-faceted, layered approach to data security.

Physical & Environmental
Recorded Internal and External CCTV
Proximity Card Access Control to Facility; Dual Factor in Secure Areas Intruder and Door Alarms
Best of Breed HVAC, Fire Suppression, and Physical Security Monitoring & Availability
24x365 Staffed Operations Facility
24x365 Automated Network Monitoring, Incident Creation and Escalation 24x365 Distributed Denial of Service Mitigation
24x365 Intrusion Detection and Prevention Systems
Vulnerability Management
3rd Party and Internal Perimeter Vulnerability Scanning Formal Application Security Scanning Program
Annual 3rd Party Penetration Testing
Centrally Managed Endpoint Protection on all Servers
Centrally Managed Patching and Operating System Hardening Program Logical Access
VLAN Data Segregation
Extensive Deny-By-Default Access Control Lists
Multi-Factor Authentication for System Administration
Business Continuity
Daily Encrypted Backups stored offsite
Virtual Tape Backup Technology eliminates threat of lost physical media Replication to Disaster Recovery Location
Internet Redundancy and High Availability using Multiple Carriers Audit Compliance
Annual SSAE16/ISAE 3402 Data Center Audit
Annual SSAE16 Operations Audit
Annual Control Self-Assessment
Annual PCI-DSS Compliance Audit
Defined Information Security Program and Policy Framework Network Security
SSL and IPSEC VPN with 256 Bit Encryption
Data-At-Rest Secured with 256 Bit AES Encryption where available Web Application Firewall Protection
Multi-layer Infrastructure Security Model
www.centralsqr.com 6
Attachment B
Regulatory Compliance
As a provider of public administration and public safety software to government organizations , CentralSquare is subject to a comprehensive set of regulatory and customer audit obligations . These requirements drive the security and compliance framework that governs the CentralSquare business strategy and its employees, products, processes, and technology .

Maintaining customer data security requirements and industry regulatory compliance helps enable CentralSquare to be a market leader, as well as a trusted partner for the customers we serve. Most importantly, it helps to ensure the safety of sensitive citizen information .

PCI DSS: Payment Card Industry Data Security Standard. CentralSquare is a Level 1 provider of credit card processing which means we store, process, and transmit over 6 million one-time and/or recurring credit card transactions per year on behalf of the citizens we serve. Level 1 compliance carries the most stringent requirements as directed by the PCI DSS standard . These requirements are becoming increasingly complex and challenging every year, as bad actors discover new and easier ways to exploit systems that process, store, or transmit credit card data.

Compliance requirements include but are not limited to the following : annual onsite audit at the CentralSquare Center of Excellence in Lake Mary, recurring internal and external system vulnerability scanning, and application penetration testing . If your role in CentralSquare is to perform duties such as customer support, Cloud administration, application development, or professional services, it is imperative that you understand the proper operating requirements when supporting the CentralSquare Cloud and associated Credit Card Data Environment. The methods in which you access, support, and administer systems in the CentralSquare Cloud must adhere to the requirements set forth by the PCI Council and the CentralSquare Security & Compliance Program.

Maintaining PCI compliance not only means that CentralSquare is adhering to the requirements of the PCI Council, but most importantly it means that we are providing a safe and secure operating environment for the citizens we serve every day.

SSAE18: Standards of Statements on Attestation Engagements, #18. The SSAE18 Audit Standard is governed by the American Institute of Certified Public Accountants [AICPA], and focuses specifically on Data Center Controls relevant to the Hosting of Customer Financial Records . These controls consist of people, processes , and technology implemented to protect customer financial data. Examples include change management for customer production systems and financial applications, physical and environmental data center systems, backup and disaster recovery planning, and proper authentication and authorization into hosted customer environments .

CentralSquare Cloud stores, processes, transmits, and hosts customer financial information and is therefore audited on an annual basis, per the SSAE18 Standard . The audit outcome, along with a formal Auditor Opinion , is detailed in the System and Organizational Controls Report, or SOC Report. www.centralsqr.com 7
Attachment B
Customers often require the CentralSquare SOC report as part of their annual internal financial audit. The SOC Report is considered sensitive in nature , and should only be provided to active CentralSquare Cloud customers . A redacted version of the report is available for premise customers that process credit card data through the CentralSquare Cloud Hub environment, and a high-level attestation letter can be provided for prospective customers or for purposes of Request For Proposal (RFP).

Ensuring proper protections exist in CentralSquare hosted data centers proactively helps to enable a secure operating environment and successful overall customer experience .

CJIS: Criminal Justice Information Services. Governed by the Federal Bureau of Investigation, the CJIS regulation pertains to proper access , handling, transmitting, processing and storing of Criminal Justice Information , or CJI. Criminal Justice Agencies must comply with all aspects of the CJIS policy , which also extends to non-Criminal Justice Agencies such as CentralSquare .

CentralSquare has an obligat ion to comply with CJIS specifically for the development , installation, and support of Public Safety solutions that we provide to Criminal Justice Agencies for the purpose of interfacing with FBI CJIS systems that may contain CJI. These applications include CAD, RMS, MCT, OSMCT, Freedom, StateConnect , and Message Switch .

CJIS requirements also extend to the Support system in use by CentralSquare when accessing public safety environments . Currently , Securelink is the approved CJIS Customer Support system due to enhanced features such as multi-factor authentication and FIPS (Federal Information Processing Standard) 140-2 compliance .

CJIS requirements also extend to CentralSquare personnel. To be cleared for support access to customer environments that may contain CJI, employees must complete annual training with a test component , get fingerprinted, and be willing to undergo a background check should the customer require one.

CentralSquare is subject to CJIS audit at both the state and federal levels , as part of overall compliance for our public safety customers . Ultimately , the customer is responsible for ensuring vendor compliance with CJIS , which means the customer can engage CentralSquare for compliance assurances during any CJIS audit engagement.

HIPAA: Health Insurance Portability & Accountability Act. CentralSquare provides public safety software solutions to many customers that fall within the purview of HIPAA ; therefore we must meet the Administrative, Technical, and Physical control specifications specific to the safeguarding of Protected Health Information , or PHI.

Specifically , CentralSquare is subject to the requirements of a Business Associate (BA) to a Covered Entity. A Covered Entity is defined as any provider (City, County , University , etc.) that processes , transmits , or stores Protected Health Information .

As a Business Associate , CentralSquare is bound by a Business Associate Agreement for each Covered Entity.

Business Associate Agreements set forth requirements to ensure the protection and prevent the disclosure of health information, and set specific provisions for breach reporting as they relate to the exposure of PHI.

FERPA: Family Educational Rights and Privacy Act &
PPRA: Protection of Pupil Rights Amendment. FERPA and PPRA are Federal laws intended to protect the rights of students and their families , and the privacy of student education records . The law applies to all institutions that receive funds through the U.S. Department of Education . www.centralsqr.com 8
Attachment B
CentralSquare is a solution provider to many educational institutions, and therefore must abide by the laws of FERPA & PPRA in regards to proper handling of student data.

GDPR: European General Data Protection Regulation. EU legislation took effect on May 25, 2018 , GDPR is designed to protect the Personally Identifiable Information (PII) of European citizens. The scope of GDPR extends to citizens residing in EU member countries as well as citizens defined as residing in the European Economic Area .

Federal, State & Local Data Privacy, Handling, and Incident Reporting. The requirements for proper handling, security, and privacy of customer data can vary with each customer depending on federal, state, and /or local requirements . Certain states such as Florida impose laws such as the Florida Information Protection Act, or FIPA, requiring any entity that acquires, maintains, stores or uses personal information of individuals in the state to abide by specific requirements in regard to data breach reporting and records disposal. CentralSquare works closely with each customer to ensure that all data security requirements are addressed to satisfaction of the customer as well as state and local law.

Additional information regarding the CentralSquare Information Security Program can be obtained by contacting [email protected]. www.centralsqr.com 9
Attachment B
Analytics Product Security Overview
CentralSquare Technologies Analytics system provides security for Customer data through a layered approach. This security includes 1) Access controls to the application; 2) Secure infrastructure hosted at the hosting facility; 3) access limited to CentralSquare personnel with the required security approval. Analytics products, such as CrimeView and CrimeMapping, include data imported from the Customer’s public safety systems (such as CAD and RMS).

CentralSquare Technologies Analytics products are deployed either on-premise at the Customer site or in a Cloud deployment. This document will primarily focus Cloud deployments. On -premise systems are protected by the customer through their physical and infrastructure security.

A common question regarding Analytics products is do these products store Criminal Justice Information (CJI) data.

Analytics products does not directly query, display or store Criminal Justice Information (CJI) data. Analytics data imports exclude the import of CJI data. The imported data may include narrative fie lds referred to as “remarks.” If the source data for remarks includes CJI data, CentralSquare recommends excluding remarks from the import process.

While the Analytics products do not import CJI, CentralSquare uses CJIS -level security for storage and access as a best practice for managing Customer operational data within Analytics.

CrimeView Security (including Subsystems such as CrimeView Analytics, FireView Analytics, CrimeView Dashboard, FireView Dashboard, Advanced Reporting Module, and NEARme)

1. Application security through CrimeView includes the following:
• Role-based security restricts user access by agency, data sensitivity, and individual entities. The Customer’s CrimeView system administrator controls user accounts and role -based security assignments. • CrimeView encryption of data in motion is through certified FIPS 140-2 encryption components. All data exchanged is encrypted CrimeView utilizes encryption components with the following FIPS 140 -2 Certificates:
o FIPS 140-2 Certificate 1337
o FIPS 140-2 Certificate 1894
Note: The encryption method is RSA, and the length is 2048 bit • The initial data load into CrimeView is extracted from the Customer’s source system. This data is transmitted from the Customer’s site utilizing an encrypted transfer tool. Once the initial data is loaded on the servers – either on-premise or in a Cloud deployment, a data update process is initiated between the Customer’s source systems and the Analytics CrimeView servers. • CrimeView Cloud data is stored in Amazon Web Services (AWS) Government and encrypted at rest using Microsoft BitLocker.
• CrimeView Cloud deployments hosted in AWS Government provide encryption through Bit -Locker (certified FIPS 140-2 encryption components – Microsoft BitLocker FIPS140-2-Jan2017-Certs-2932-2933- 2934).

Attachment C

2. CrimeView is hosted from an Amazon Web Services (AWS) Government facility. Each of these facilities meet the stringent FBI CJIS Policy standards and guidelines with the following protect ion features on site:
• Monitored by both fixed and pan-tilt/zoom security cameras • Protected by intrusion detection system
• Two-factor authentication required for building access • Biometric iris authorization required for data center access • Extensive pre-employment background investigation process • On-site building security and data center monitoring staffed 24/7/365

The Cloud system infrastructure is managed and controlled by CentralSquare. CentralSquare Technologies currently hosts the Cloud CrimeView system at Amazon Web Services (AWS) Government. • The AWS Government deployment is through AWS infrastructure as a service. AWS allocates infrastructure based upon a CentralSquare defined template and CentralSquare security authorized staff setup storage, OS, DBMS (SQL Server), applications and security. • CentralSquare manages application and security updates as well as Operating System, DBMS and application upgrades at both hosting sites.
• Hosting facility personnel do not have access to the system and do n ot perform system setup or maintenance.

3. Cloud CrimeView access to implement and support the system is limited to personnel that have completed CentralSquare Technologies’ CJIS compliant security approval process. • Access to the Cloud CrimeView infrastructure requires approved personnel to complete a layered secure login process that includes personally assigned passwords, advanced authentication to gain access to the CentralSquare Technologies network and secure access login to the applicable Cloud Crime View domain, application and SQL Server database.
• Pre-employment background check.
• Training - Each of security approved employee successfully completed CJIS On -Line Security and Awareness training and testing. Their certifications are current and must be renewed every two years. In addition to CJIS required training, CentralSquare Technologies also does periodic training for security approved personnel on CentralSquare Technologies security policies. • Criminal background checks have been completed on each of these personnel by CentralSquare Technologies as part of employee screening and by one or more law enforcement agencies (CentralSquare Technologies Customers and in some cases, State law enforcement agencies). • Fingerprints – each of these personnel have been fingerprinted and their prints have been submitted to one or more law enforcement agencies for background check. • Security approved personnel are the same personnel that are utilized for supporting Customers with on premise deployments of CAD, Mobile, RMS and other CentralSquare products.

CrimeMapping Security

Crimemapping.com is hosted in the Microsoft Azure non-government cloud, where only non-sensitive data is stored. The Crimemapping architecture is like that of CrimeView, but Crimemapping data is presented to the public. Crimemapping.com records are first transmitted to the CrimeView AWS Government cloud then sent to the Crimemapping environment in Microsoft Azure. Hosted data at AWS and Azure is encrypted through Microsoft BitLocker and Microsoft FIPS 140-2 compliant encryption is utilized for data in transit (the same encryption components as CrimeView).

Attachment C
Analytics Product Security Overview
CentralSquare Technologies Analytics system provides security for Customer data through a layered approach. This security includes 1) Access controls to the application; 2) Secure infrastructure hosted at the hosting facility; 3) access limited to CentralSquare personnel with the required security approval. Analytics products, such as CrimeView and CrimeMapping, include data imported from the Customer’s public safety systems (such as CAD and RMS).

A common question regarding Analytics products is do these products store Criminal Justice Information (CJI) data.

While the Analytics products do not import CJI, CentralSquare uses CJIS -level security for storage and access as a best practice for managing Customer operational data within Analytics.

CrimeView Security (including Subsystems such as CrimeView Analytics, FireView Analytics, CrimeView Dashboard, FireView Dashboard, Advanced Reporting Module, and NEARme)

Attachment D

CrimeMapping Security

Attachment D
City of Oakland-CentralSquare PSA Attachment E

1 PROFESSIONAL SERVICES AGREEMENT

BETWEEN

THE CITY OF OAKLAND

AND CENTRALSQUARE TECHNOLOGIES

City of Oakland-CentralSquare PSA Attachment E

2 TABLE OF CONTENTS

1. Security ......................................................................................................................................... 5

2. Priority of Documents .............................................................................................................5

3. Conditions Precedent ..............................................................................................................5

4. Statement of Work ..................................................................................................................6

5. Initial Term .............................................................................................................................6

6. City Requirements and Project Deliverables ..........................................................................6

7. Contractor Warranty and Indemnification of Services ............................................................6

8. Payment...................................................................................................................................8

9. Reserved ....................................................................................................................................... 8

10. Proprietary or Confidential Information of the City ...............................................................9

11. Ownership of Results ............................................................................................................10

12. Amendments .........................................................................................................................10

13. Limitation on Liability ..........................................................................................................11 14 Security of and Access to City’s Information Technology Systems ....................................11

15. Indemnification .......................................................................................................................... 11

16. Termination ...........................................................................................................................11 17 Dispute Resolution ................................................................................................................14

18. Implementation .....................................................................................................................15 19 Bankruptcy ............................................................................................................................16

20. Assignment ...........................................................................................................................16 21, Agents/Brokers .....................................................................................................................16

22. Publicity ................................................................................................................................17

23. Conflict of Interest ................................................................................................................17

24. Validity of Contracts .............................................................................................................17

25. Governing Law .....................................................................................................................19

26. Headings ...............................................................................................................................19

27. Construction ..........................................................................................................................20

28. Waiver ...................................................................................................................................20

29. Independent Contractor .........................................................................................................20

30. Attorneys’ Fees ....................................................................................................................20

31. Counterparts ..........................................................................................................................22

32. Remedies Cumulative ...........................................................................................................22

33. Severability/Partial Invalidity ...............................................................................................22

34. Access ...................................................................................................................................22

35. Entire Agreement of the Parties ............................................................................................22

36. Modification ..........................................................................................................................23

37. Notice ....................................................................................................................................23

38. No Third Party Beneficiary ...................................................................................................23 39 Survival .................................................................................................................................24 40 Time is of the Esssence .........................................................................................................24

41. Authority ...............................................................................................................................24

City of Oakland-CentralSquare PSA Attachment E

3 EXHIBITS

Exhibit 1 Statement of Work
Exhibit 2 End User License Agreement and Support Terms
Exhibit 3 Pricing and Payment Milestones
Exhibit 4 Security Provisions
a. CentralSquare Cybersecurity Program Overview
b. CentralSquare Analytics Product Security Overview
Exhibit 6 City Contract Compliance Provisions
Exhibit 7 City Schedules

City of Oakland-CentralSquare PSA Attachment E

4 This Agreement to provide Professional Services and Related Products as applicable and as set for with specificity herein [“Agreement”] is by and between CentralSquare Tehnologies, a public safety software [INSERT NATURE OF ORGANIZATION AND WHERE ORGANIZED] located at 1000 Business Center Drive, Lake Mary, FL 32746 (“Contractor”) and the City of Oakland (“City”), a municipal corporation, located at One Frank H. Ogawa Plaza, Oakland, California 94612, who agree as follows:

RECITALS

This Agreement is made with reference to the following facts and objectives:

A. WHEREAS, the City Council has authorized the City Administrator to enter into contracts for professional or specialized services if the mandates of Oakland City Charter Section 902(e) have been met; and

B. WHEREAS, Contractor is the developer of public safety software products and related professional services [“Services”]; and

C. WHEREAS, City is part of and provides information technology services to the various City departments, offices, and programs; and

D. WHEREAS, City wishes to acquire Contractor’s Services and products as specifically set forth in this Agreement, including the Statement of Work [“SOW”] attached hereto.

E. WHEREAS, the following Exhibits and Schedules are attached to and incorporated by reference into this Agreement:

Exhibit 1 Statement of Work
Exhibit 2 Software Support Agreement
Exhibit 3 Pricing and Payment Milestones
Exhibit 4 CentralSquare Cybersecurity Program Overview
Exhibit 5 CentralSquare Analytics Product Security Overview Exhibit 6 City Contract Compliance Provisions
Exhibit 7 City Schedules

NOW THEREFORE, THE PARTIES TO THIS Agreement COVENANT AND AGREE AS FOLLOWS:

City of Oakland-CentralSquare PSA Attachment E

5 1. Security

a. Contractor’s Security Program

In entering into this Agreement, City is relying upon Contractor’s averment that it maintains a Security program for managing access to City dat a – particularly HIPAA and CJIS information which includes 1) a Pre -employment background check, 2) security training required by Federal CJIS regulations, and 3) criminal background checks/fingerprints required by Federal or State regulations .

Contractor’s Security program is detailed in the Security Provisions Exhibit 4 Contractor’s Cybersecurity Program Overview and Exhibit 5 Contractor’s Analytics Product Security Overview. In addition, Contractor avers to provide City the required documentation (such as the CJIS Security Addendum Certification form and VPN documents).

b. System Security

(i) Contractor shall at all times maintain and ensure that all of City’s information technology systems which Contractor interfaces with or has access to remain secure and do not through any of Contractor’s actions or lack of action thereof including, but not limited to, ransomeware attacks upon Contractor, become vulnerable to breach, hacking into or in any way provide any unauthorized access to third parties. Contractor shall be liable for and indemnify City for all liabilities, claims, losses, damages and expenses, restorative or protective measures made necessary made necessary by any of the foregoing, including without limitation, reasonable attorney’s fees.

(ii). Contractor shall not work on any City information technology system unless Contractor first contacts and obtains prior written authorization from the City’s Director of Office of Information Technology, or his or her designee. Contractor warrants and represents that it will provide all information, reports, and data that fully informs the City with respect to any work, software deliverables, or products that the Contractor works on or which alter or affect the City’s information technology systems, including without limitation, any source code and passwords necessary to access or make any such work, software, deliverables or products usable by the City.

c. Cloud Security

Contractor understands that, in contracting for Contractor’s Cloud Storage Service is relying upon Contractor’s representations that the methods and procedures it has in place to protect City’s data as set forth in Exhibit X [INSERT CITE TO VENDOR’S SECURITY DOCUMENT], prevent unauthorized access to, corruption of and use of City’s data including, but not limited to, ransomeware attacks upon Contractor.

Contractor further warrants and represents that it shall be liable for and fully indemnify the City for all liabilities, claims, losses, damages and expenses, including without limitation, reasonable attorney’s fees, arising from claims against City due to a breach City of Oakland-CentralSquare PSA Attachment E

6 of or other unauthorized access to the systems Contractor uses to provide City the services hereunder.

d. Data Incidents. Contractor shall implement and maintain a program for managing unauthorized disclosure of, access to, or use of City Data however they may occur (“Data Incidents”). In case of a Data Incident, or if Contractor confirms or suspects a Data Incident, Contractor shall: (1) promptly, and in any case within 24 hours, notify City by email, telephone, in person, or by other real-time, in-person communication; (2) cooperate with City and law enforcement agencies, where applicable, to investigate and resolve the Data Incident, including without limitation by providing reasonable assistance to City in notifying injured third parties; and (3) otherwise comply with applicable laws governing data breach notification and response. In addition, if the Data Incident results from Contractor’s other breach of this Agreement or negligent or unauthorized act or omission, including without limitation those of its subcontractors or other agents, Contractor shall (a) compensate City for any reasonable expense related to the Data Incident. Contractor shall give City prompt access to such records related to a Data Incident as City may reasonably request. City will treat such records as Contractor’s Confidential Information pursuant to Section b., below. Contractor is not required to give City access to records that might compromise the security of Contractor’s other customers.

In the event of a Data Incident, City will coordinate with Contractor on the content of any intended public statements or notices to the relevant authorities regarding the Data Incident.

This provision does not limit City’s other rights or remedies, if any, resulting from a Data Incident.

2. Priority of Documents

In the event of conflicting provisions as between the following documents, except as otherwise expressly stated, the provisions shall govern in the following order: the Amendments to this Agreement, in reverse chronological order of adoption, this Agreement and its Exhibits. The Exhibits shall govern in numerical order as set out in this Agreement.

3. Conditions Precedent

a Contractor must provide City with the following before the Agreement will become effective:

(1). A copy of Contractor’s City of Oakland Business Tax License which must be kept current for the duration of the Agreement and shall be attached to this Agreement as part of Exhibit 6

City of Oakland-CentralSquare PSA Attachment E

7 (2). A completed set of the City of Oakland Schedules which shall be attached to this Agreement as Exhibit 7;

b. Contractor and City must complete and agree upon and execute a Statement of Work before the Agreement will become effective and which shall be attached to this Agreement as Exhibit 1.

4. Statement of Work

Contactor avers and covenants to perform the services (“Services”) and provide the deliverables (“Deliverables”) specified in Exhibit 1, the Statement of Work including, but not limited to, the as requested or required Additional Items, Maintenance and Support for its Crimemapping.com and CrimeView Desktop products and providing its CrimeView Analytics product as a Software as a Service, all as set forth with specificity in the SOW

5. Term

This Agreement shall start when it is executed in full by the parties {“Effective Date”] and end on December 31, 2024. Should City decide, in its sole discretion, to exercise either or both of the authorized one-year extensions, and the parties mutually agree on the extensions, the Agreement may be extended until December 31, 2026.

6. City Requirements for Project Deliverables

Contractor avers and covenants to provide its Services and Deliverables which will include, but not be limited to, expanding the utility of Contractor’s CrimeView Analytics and crimemapping.com products, licensing and providing maintenance and support for those products and providing CrimeView Desktop to City as a Software as a Service, all as set forth in the SOW.

7. Contractor Warranty and Indemnification of Services
a. Contractor will provide its software [“Software”] and Maintenance and Support Services under this Agreement “as is”, without warranty, and will support that “Software” from the date of live operational use (“Go Live”) in accordance with Contractor’s End User License Agreement and Software Support terms attached hereto as Exhibit 2.

Subscription services are also provided “as is”, without warranty, and will be supported in accordance with the Contractor’s subscription terms in Exhibit 2 b. Notwithstanding paragraph 7.a. above, Contractor warrants and represents that the Software does not contain any back door, time bomb, Trojan horse, worm, drop dead device, or other program or routine inserted and intended to provide a means of City of Oakland-CentralSquare PSA Attachment E

8 unauthorized access to, or a means of disabling, or rendering the Software unusable or inoperable.

c. Contractor acknowledges that City is a provider of public and municipal services to the public and residents of the City of Oakland and that City’s reliance on and use of Contractor’s Deliverables will be vital to: (a) the business operations of the City; (b) the orderly and efficient provision of public and municipal services by the City; and (c) the health and safety of City’s residents; and therefore, that any unauthorized interruption of City’s business and operations could result in substantial liability to City. In recognition of City’s status as a provider of such public and municipal services, Contractor warrants and represents that Contractor shall not at any time during the term of this Agreement and thereafter render the Software unusable or inoperable, or otherwise disable the Contractor’s software, take possession of the Software or if any, the Hardware provided to City by Contractor or Contractor’s subcontractors or in any way deliberately take actions limiting Contractor’s liability under this Agreement. If Contractor takes any such actions, Contractor shall be liable for and indemnify City for all liabilities, claims, losses, damages and expenses, including without limitation, reasonable attorney’s fees, arising from Contractor’s actions.
d. The Services and Deliverables (a) will conform in all material respects to the Specifications
e. Contractor represents that it will use commercially reasonable efforts, including appropriate testing, to ensure that the Software does not contain viruses, contaminants, or other harmful code that may harm the Software, City systems or other City software. f. Contractor represents that it owns or has the unencumbered right to license to City, the Deliverables and all results of Services delivered to City hereunder, including all required Intellectual Property Rights therein.
g. Contractor represents that it has the requisite experience, certifications, skills and qualifications necessary to perform the Services in: (i) a timely, competent, and professional manner, and (ii) accordance with applicable governmental requirements, statutes, regulations, rules and ordinances including, without limitation, applicable data privacy laws and regulations (“Law”);
h. Contractor further warrants and represents that the methods and procedures it has in place to protect City’s data as set forth in Exhibit 4 [Central Square Security Overview letter], prevent unauthorized access to, corruption of and use of City’s data, Contractor further warrants and represents that, subject to the coverage limits of its Cyber Insurance, it shall be liable for and fully indemnify the City for all liabilities, claims, losses, damages and expenses, including without limitation, reasonable attorney’s fees, arising from claims against City due to a breach of or unauthorized access to the systems Contractor uses to provide City the services hereunder.

i. EXCEPT FOR THE EXPRESS REPRESENTATIONS AND WARRANTIES

MADE IN THIS AGREEMENT, THE CONTRACTOR MAKES NO

REPRESENTATION, ACKNOWLEDGEMENT, CONDITION OR WARRANTY OF City of Oakland-CentralSquare PSA Attachment E

9 ANY KIND WHATSOEVER UNDER THIS AGREEMENT OR OTHERWISE,

INCLUDING WITHOUT LIMITATION, ANY STATUTORY, EXPRESS, IMPLIED

OR OTHER WARRANTIES OR ANY WARRANTY OF MERCHANTABILITY OR

FITNESS FOR ANY PARTICULAR PURPOSE REGARDING ANY SERVICES,

DELIVERABLE OR ANY OTHER PRODUCT DELIVERED TO THE CITY
UNDER THIS AGREEMENT.

8. Payments.`

City shall pay Contractor the CrimeView Analytics, CrimeView Desktop and Crimemapping Services fees along with the annual Software License Fees and the Additional Items Reserve for those services City requests Contractor to provide, the not to exceed fees set forth in Exhibit 3 [Pricing and Payment Milestones].

9. [RESERVED]

10. Proprietary or Confidential Information

10.1 Confidentiality Obligations. Confidential Information shall mean all proprietary or confidential information disclosed or made available by the other Party pursuant to this Agreement that is identified as confidential or proprietary at the time of disclosure or is of a nature that should reasonably be considered to be confidential, and includes, but is not limited to, the terms and conditions of this Agreement, and all business, technical and other information (including without limitation, all product, services, financial, marketing, engineering, research and development information, product specifications, technical data, data sheets, software, inventions, processes, training manuals, know-how and any other information or material), disclosed from time to time by the disclosing Party to the receiving Party, directly or indirectly in any manner whatsoever (including without limitation, in writing, orally, electronically, or by inspection); provided, however, that Confidential Information shall not include the Content that is intended to be published on the website(s) of either Party.

10.2 Each Party agrees to keep confidential and not disclose to any third party and to use only for purposes of performing or as otherwise permitted under this Agreement, any Confidential Information. The receiving Party shall protect the Confidential Information using measures similar to those it takes to protect its own confidential and proprietary information of a similar nature but not less than reasonable measures. Each Party agrees not to disclose the Confidential Information to any of its Representatives except those who are required to have the Confidential Information in connection with this Agreement and then only if such Representative is either subject to a written confidentiality agreement or otherwise subject to fiduciary obligations of confidentiality that cover the confidential treatment of the Confidential Information.

10.3 Exceptions.

The obligations of this Section 10 shall not apply if the receiving Party can prove by City of Oakland-CentralSquare PSA Attachment E

10 appropriate documentation, where appropriate, that such Confidential Information (i) was known to the receiving Party as shown by the receiving Party’s files at the time of disclosure thereof, (ii) was already in the public domain at the time of the disclosure thereof, (iii) entered the public domain through no action of the receiving Party subsequent to the time of the disclosure thereof, (iv) is or was independently developed by the Contractor without access to or use of the Confidential Information; (v) was provided to the Contractor by a third party who, to the best of the Contractor’s knowledge, was not bound by any confidentiality obligation related to such Confidential Information; or (vi) is required by law or government order to be disclosed by the receiving Party, provided that the receiving Party shall (i) notify the disclosing Party in writing of such required disclosure as soon as reasonably possible prior to such disclosure, (ii) use its commercially reasonable efforts at its expense to cause such disclosed Confidential Information to be treated by such governmental authority as trade secrets and as confidential.

10.4 Contractor acknowledges that City is subject to public disclosure laws and that City will comply with requests for information (“RFI”), as it is required to do under the federal Freedom of Information Act, California Public Records Act, City of Oakland Sunshine Act or judicial or administrative court order. Contractor acknowledges that an RFI may pertain to any and all documentation associated with City’s use of Contractor’s Services. Contractor further acknowledges that it is obligated to assist and cooperate with City by producing all documentation that City requests as responsive to the RFI so that City may comply with its statutory obligations. City agrees to give Contractor as timely written notice as possible of the RFI such that Contractor may oppose the RFI or exercise such other rights at law as Contractor believes it has.

However, Contractor must produce to City all documents City requests as RFI responsive and City will comply with the RFI unless, within the time frame established by the statute, judicial or court order under which the RFI is made, Contractor procures a Temporary Restraining Order or similar injunctive relief from a court or other tribunal of competent jurisdiction ordering City not to comply with the RFI pending final determination of Contractor’s protest of the RFI. Contractor further agrees to accept City’s tender of defense and to defend City and pay all City costs of defense in any litigation brought against City with respect to City not complying with an RFI that Contractor protests and will hold City harmless against any claims, attorneys’ fees, damages, fines, judgments, or administrative penalties, which may arise from any such actions.

11. Ownership of Results

Excluding the Contractor’s intellectual property, or if applicable, any subcontractor intellectual property, any interest of Contractor or its Subcontractors, in specifications, studies, reports, memoranda, computation documents in drawings, plans, sheets prepared by Contractor or its Subcontractors under this Agreement shall be assigned and transmitted to the City. However, Contractor may retain and use copies for reference and as documentation of its experience and capabilities.

City of Oakland-CentralSquare PSA Attachment E

11 12. Amendments

Changes to this Agreement will only be made by mutually agreed upon Amendments in writing.

13. Limitation on Liability

(a) Either party's liability to the other party for any and all liabilities, claims or damages arising out of or relating to this Agreement [Direct Damages], howsoever caused and regardless of the legal theory asserted, including breach of contract or warranty, tort, strict liability, statutory liability or otherwise, shall not, in the aggregate, exceed twice the total value of this Agreement as set forth in Exhibit 3 [Pricing and Payment Milestones].

(b) IN NO EVENT SHALL EITHER PARTY BE LIABLE TO THE OTHER FOR

ANY PUNITIVE, EXEMPLARY, SPECIAL, INDIRECT, INCIDENTAL OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, LOST

PROFITS, LOST BUSINESS OPPORTUNITIES, LOSS OF USE OR EQUIPMENT

DOWN TIME, AND LOSS OF OR CORRUPTION TO DATA) ARISING OUT OF

OR RELATING TO THIS AGREEMENT, REGARDLESS OF THE LEGAL

THEORY UNDER WHICH SUCH DAMAGES ARE SOUGHT, AND EVEN IF THE

PARTIES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR LOSS.

(c) This limitation of liability shall not apply to Contractor’s [Indemnification] obligations as set forth in this Agreement.

14. Reserved

15. Indemnification

(a) General Indemnification.

Notwithstanding any other provision of this Agreement, Contractor shall indemnify and hold harmless (and at City’s request, defend) City, and each of their respective Councilmembers, officers, partners, agents, and employees (each of which persons and organizations are referred to collectively herein as "Indemnitees" or individually as "Indemnitee") from and against any and all liabilities (of every kind, nature and description), claims, lawsuits, losses, damages, demands, debts, liens, costs, judgments, obligations, administrative or regulatory fines or penalties, damages, (incidental or consequential) costs, actions or causes of action, and expenses, including reasonable attorneys' fees, (collectively referred to herein as “Actions”) caused by or arising out of:

(i) A claim for personal injury (including death) or property damage to the extent based on the strict liability or caused by any negligent act, error or omission of Contractor;
City of Oakland-CentralSquare PSA Attachment E

12 (ii) Unauthorized use or disclosure by Contractor of Confidential Information as provided in Section 10 above.

(b) Proprietary Rights Indemnity. Contractor shall indemnify, defend, save and hold harmless Indemnitees from any and all actions arising out of third party claims that the Contractor’s Services, or Software, if any infringes upon or violates the Intellectual Property Rights of a third party. If the Services or Software will become the subject of an Action or claim of infringement or violation of the Intellectual Property Rights of a third party, Contractor may, in addition to its obligation to defend and indemnify City hereunder, in its discretion, and at Contractor’s sole expense: (1) procure for City the right to continue using the Services or Software; or (2) replace or modify the Services or Software so that no infringement or other violation of Intellectual Property Rights occurs, if City determines that: (A) such replaced or modified Services or Software will operate in all material respects in conformity with the then- current specifications for the Services or Software; and (B) City’s use of the Services or Software is not impaired thereby. Contractor’s obligations under this Agreement will continue uninterrupted with respect to the replaced or modified Services or Software as if it were the original Software. If Contractor concludes in its sole judgement that none of the foregoing options are commercially reasonable, and the City’s use of the Contractor’s Services or Software is permanently enjoined this Agreement and the license granted herein shall terminate.

(c) Contractor shall have no duty under Section 15 (b) and shall not be liable for any Actions arising from;
(1) modifications made to Contractor’s Software or the Services by the City unless the City has made such modifications at the request or direction of Contractor; (2) the Contractor having been required to conform to all or part of specific product designs of the City, provided that the Contractor has informed the City that any such requirement to conform may result in a claim under clause 16(b); (3) the use by the City of Contractor’s Software or Services or any part of them with programs, hardware, or software supplied by other parties, unless the Contractor has represented to the City that its Software or Services or any part of them are designated for use with such other programs, hardware, or software; (4) use of Contractor’s Software or Services or any part of them by the City in a manner contrary to the Contractor's specifications and/or documentation provided by or through the Contractor and accepted by the City; (5) use of Contractor’s Software or Services or any part of them by the City on any hardware for which the Software or Services or any part of them was not designed; or
(6) the City not using corrections to the Software or Services or any part of them made known and available by the Contractor.

(d) For the purposes of the indemnification obligations set forth herein, the term “Contractor” includes, without limitation, Contractor, its officers, directors, employees, representatives, agents, servants, sub consultants, and subcontractors.

City of Oakland-CentralSquare PSA Attachment E

13 (e) Contractor acknowledges and agrees that it has an immediate and independent obligation to indemnify and defend Indemnitees from any Action which potentially falls within this Indemnification provision, which obligation shall arise at the time an Action is tendered to Contractor by City and continues at all times thereafter, without regard to any alleged or actual contributory negligence of any Indemnitee.

Notwithstanding anything to the contrary contained herein, if a claim, lawsuit or liability results from or is contributed to by the actions or omissions of an Indemnitee, Contractor’s liability under this provision shall be reduced to the extent of such actions or omissions based upon the principle of comparative fault.

(f) City shall give Contractor prompt written notice of any Action and shall fully cooperate with Contractor in the defense and all related settlement negotiations to the extent that cooperation does not conflict with City’s interests. Notwithstanding the foregoing, City shall have the right, if Contractor fails or refuses to defend City with Counsel acceptable to City, to engage its own counsel for the purposes of participating in the defense. In addition, City shall have the right to withhold payments due Contractor in the amount of reasonable defense costs actually incurred. In no event shall Contractor agree to the settlement of any claim described herein without the prior written consent of City.

(g) All of Contractor’s Indemnification obligations hereunder are intended to apply to the fullest extent permitted by law (including, without limitation, California Civil Code Section 2782) and shall survive the expiration or sooner termination of this Agreement.

(h) Contractor’s Indemnification obligations hereunder shall not be limited by the City’s insurance requirements contained in Schedule Q hereof, or by any other provision of this Agreement.

16. Termination

(a) Termination for Breach. If Contractor breaches any material obligation under this Agreement and fails to cure the breach within 30 days of receipt of written notice from City of said breach, City may terminate the Agreement and, subject to the Limitation on Liability (Section 13), recover all Direct Damages it incurs as a result of Contractor’s breach.

(b) Contractor may terminate this Agreement if City breaches a material provision of the Agreement and does not cure the breach within 30 days of written notice from Contractor of said breach. In such event, Contractor will be entitled to payment of all fees for Services or Deliverables the City has Accepted but not paid Contractor up to the date of termination.

(c) Bankruptcy. Either party may immediately terminate this Agreement if (i) the other party files a petition for bankruptcy or has filed against it an involuntary petition for bankruptcy which is not dismissed within 60 days of its filing, (ii) a court has appointed a receiver, trustee, liquidator or custodian of it or of all or a City of Oakland-CentralSquare PSA Attachment E

14 substantial part of the other party’s property, (iii) the other party becomes unable, or admits in writing its inability, to pay its debts generally as they mature, or (iv) the other party makes a general assignment for the benefit of its or any of its creditors.

(d) Termination for Convenience by City. City may terminate this Agreement for any reason at any time upon not less than sixty (60) days' prior written notice to Contractor. After the date of such termination notice, Contractor shall not perform any further services or incur any further costs claimed to be reimbursable under this Agreement, any Purchase Order, Change Order, or Change Notice without the express prior written approval of City. As of the date of termination, City shall pay Contractor for Services or Deliverables the City has Accepted but not paid Contractor
(e) Transition Services after termination. In connection with the expiration or other termination of this Agreement or the expiration of this Agreement, Contractor may provide transition services as requested by City. Contractor shall provide a quotation to City for any transition services, and shall not be obligated to provide any services until both parties have mutually agreed in writing to such quotation.
(f) Effect of Termination. Upon termination of this Agreement, City shall remove all Contractor Software from its computer system and certify in writing to Contractor that it has destroyed all Contractor Software and its associated documentation. Any City data in Contractor’s possession shall either be returned to the City or destroyed as directed by the City.

17. Dispute Resolution

a. If dispute or disagreement among the Parties arises with respect to either Party’s performance of its obligations hereunder, or any provision of or interpretation of the Agreement, the Parties agree in good faith to attempt to resolve such dispute or disagreement (a “Dispute”) prior to submitting the Dispute to mediation, arbitration or litigation in accordance with this Section 17. Such resolution efforts shall involve the City Administrator of the City of Oakland and an executive officer of Contractor, together with such other persons as may be designated by either Party.

b. Any Party may commence said resolution efforts by giving notice, in writing, to any other Party. Such notice shall include at least a description of the Dispute and any remedial action that the Party commencing the resolution procedure asserts would resolve the Dispute. Upon receiving such notice, the Party against whom the Dispute is brought shall respond in writing within five (5) Business Days. The Parties shall then meet and confer in a good faith attempt to resolve the Dispute.

City of Oakland-CentralSquare PSA Attachment E

15 c If the Dispute has not been resolved within ten (10) Business Days after the Subsection 17.b. notice is given, said period to be extended by the parties’ mutual agreement and, unless the Party initiating the Dispute does not wish to pursue its rights relating to such Dispute or desires to continue the Pre-Mediation Dispute Resolution, then such Dispute will be automatically submitted to mediation. The mediation will be conducted in Alameda County by a single mediator selected by the Parties to the Dispute by mutual agreement or by the use of the Commercial Arbitration Rules of the American Arbitration Association for selecting an Arbitrator [“AAA RULES”] The Parties to the Dispute shall evenly share the fees and costs of the mediator. The mediator shall have twenty (20) Business Days from the submission to mediation to attempt to resolve such Dispute. If the Dispute is not resolved within that time period, the parties will be entitled to pursue such matter by demanding arbitration under the AAA RULES or instituting litigation.

18. Implementation

A mutually agreed upon Project Schedule will be developed for implementation of the Project under this Agreement as defined in the Statement of Work. The Project Schedule will define timelines and responsibilities of each Party and may be modified at the mutual agreement of the Parties.

19. Bankruptcy
All rights and licenses granted to City pursuant to this Agreement are, and shall be deemed to be, for purposes of Section 365(n) of the U.S. Bankruptcy Code, licenses of rights to “intellectual property” as defined under Section 101 of the U.S. Bankruptcy Code. In a bankruptcy or insolvency proceeding involving Contractor, the parties agree that City, as licensee of such rights, shall retain and fully exercise all of its rights and elections under the U.S. Bankruptcy Code, and the provisions thereof shall apply notwithstanding conflict of law principles. The parties further agree that, in the event of the commencement of a bankruptcy or insolvency proceeding by or against Contractor under the U.S. Bankruptcy Code, City shall be entitled to a complete duplicate of any such intellectual property, including the source code for Contractor’s Licensed Software which Contractor has placed in escrow as required under this Agreement and all embodiments of such intellectual property, to which City would otherwise be entitled under this Agreement, and the same, if not already in City’s possession, shall be promptly delivered to City (a) upon any such commencement of a bankruptcy proceeding upon written request therefore by City, unless Contractor elects to continue to perform all of its obligations under this Agreement, or (b) if not delivered under (a) above, upon rejection of this Agreement by or on behalf of Contractor upon written request therefore by City. If, in a bankruptcy or insolvency proceeding involving Contractor, the provisions of the U.S. Bankruptcy Code referenced above are determined not to apply, City shall nevertheless be entitled to no less than the protection offered by the provisions of the U.S. Bankruptcy Code with respect to its entitlement to and rights to the use and possession of all intellectual property to which City has been granted rights under this Agreement notwithstanding the bankruptcy or insolvency of Contractor.

City of Oakland-CentralSquare PSA Attachment E

16 20. Assignment

Contractor shall not assign or otherwise transfer any rights, duties, obligations or interest in this Agreement or arising hereunder to any person, persons, entity or entities whatsoever without the prior written consent of the City Attorney and City Administrator or their respective designees, which shall not be unreasonably withheld. City’s consent to any assignment shall be conditioned upon retaining all rights it has at law against Contractor as Assignor. Any attempt to assign or transfer without such prior written consent shall be void. Consent to any single assignment or transfer shall not constitute consent to any further assignment or transfer. In the event that Contractor assigns this Agreement in compliance with this provision, this Agreement and all of its provisions shall inure to the benefit of and become binding upon the parties and the successors and permitted assigns of the respective parties.

21. Agents/Brokers

Contractor warrants that Contractor has not employed or retained any subcontractor, agent, company or person other than bona fide, full-time employees of Contractor working solely for Contractor, to solicit or secure this Agreement, and that Contractor has not paid or agreed to pay any subcontractor, agent, company or persons other than bona fide employees any fee, commission, percentage, gifts or any other consideration, contingent upon or resulting from the award of this Agreement. For breach or violation of this warranty, the City shall have the right to rescind this Agreement without liability or, in its discretion, to deduct from the Agreement price or consideration, or otherwise recover, the full amount of such fee, commission, percentage or gift.

22. Publicity

Any publicity generated by Contractor for the project funded pursuant to this Agreement, during the term of this Agreement or for one year thereafter, must be approved by the City in advance and will make reference to the contribution of the City of Oakland in making the project possible.

The words “City of Oakland” will be explicitly stated in all pieces of publicity, including but not limited to flyers, press releases, posters, brochures, public service announcements, interviews and newspaper articles.

City staff will be available whenever possible at the request of Contractor to assist Contractor in generating publicity for the project funded pursuant to this Agreement. Contractor further agrees to cooperate with authorized City officials and staff in any City-generated publicity or promotional activities undertaken with respect to this project.

23. Conflict of Interest

(a) Contractor

City of Oakland-CentralSquare PSA Attachment E

17 The following protections against conflict of interest will be upheld:

(1) Contractor certifies that no member of, or delegate to the Congress of the United States shall be permitted to share or take part in this Agreement or in any benefit arising there from.

(2) Contractor certifies that no member, officer, or employee of the City or its designees or agents, and no other public official of the City who exercises any functions or responsibilities with respect to the programs or projects covered by this Agreement, shall have any interest, direct or indirect in this Agreement, or in its proceeds during his/her tenure or for one year thereafter.

(3) Contractor shall immediately notify the City of any real or possible conflict of interest between work performed for the City and for other clients served by Contractor.

(4) Contractor warrants and represents, to the best of its present knowledge, that no public official or employee of City who has been involved in the making of this Agreement, or who is a member of a City board or commission which has been involved in the making of this Agreement whether in an advisory or decision-making capacity, has or will receive a direct or indirect financial interest in this Agreement in violation of the rules contained in California Government Code Section 1090 et seq., pertaining to conflicts of interest in public contracting. Contractor shall exercise due diligence to ensure that no such official will receive such an interest.

(5) Contractor further warrants and represents, to the best of its present knowledge and excepting any written disclosures as to these matters already made by Contractor to City, that (1) no public official of City who has participated in decision-making concerning this Agreement or has used his or her official position to influence decisions regarding this Agreement, has an economic interest in Contractor or this Agreement, and (2) this Agreement will not have a direct or indirect financial effect on said official, the official’s spouse or dependent children, or any of the official’s economic interests. For purposes of this paragraph, an official is deemed to have an “economic interest” in any (a) for-profit business entity in which the official has a direct or indirect investment worth $2,000 or more, (b) any real property in which the official has a direct or indirect interest worth $2,000 or more, (c) any for-profit business entity in which the official is a director, officer, partner, trustee, employee or manager, or (d) any source of income or donors of gifts to the official (including nonprofit entities) if the income totaled more than $500 in the previous 12 months, or value of the gift totaled more than $350 the previous year.

Contractor agrees to promptly disclose to City in writing any information it may receive concerning any such potential conflict of interest.

City of Oakland-CentralSquare PSA Attachment E

18 Contractor’s attention is directed to the conflict of interest rules applicable to governmental decision-making contained in the Political Reform Act (California Government Code Section 87100 et seq.) and its implementing regulations (California Code of Regulations, Title 2, Section 18700 et seq.).

(6) Contractor understands that in some cases Contractor or persons associated with Contractor may be deemed a “City officer” or “public official” for purposes of the conflict of interest provisions of Government Code Section 1090 and/or the Political Reform Act. Contractor further understands that, as a public officer or official, Contractor or persons associated with Contractor may be disqualified from future City contracts to the extent that Contractor is involved in any aspect of the making of that future contract (including preparing plans and specifications or performing design work or feasibility studies for that contract) through its work under this Agreement.

(7) Contractor shall incorporate or cause to be incorporated into all subcontracts for work to be performed under this Agreement a provision governing conflict of interest in substantially the same form set forth herein.

(b) No Waiver

Nothing herein is intended to waive any applicable federal, state or local conflict of interest law or regulation.

In addition to the rights and remedies otherwise available to the City under this Agreement and under federal, state and local law, Contractor understands and agrees that, if the City reasonably determines that Contractor has failed to make a good faith effort to avoid an improper conflict of interest situation or is responsible for the conflict situation, the City may (1) suspend payments under this Agreement, or (2) terminate this Agreement, (3) require reimbursement by Contractor to the City of any amounts disbursed under this Agreement. In addition, the City may suspend payments or terminate this Agreement whether or not Contractor is responsible for the conflict of interest situation.

24. Validity of Contracts

The Oakland City Council must approve all Agreements greater than $15,000. This Agreement shall not be binding or of any force or effect until signed by the City Manager or his or her designee and approved as to form and legality by the City Attorney or his or her designee.

City of Oakland-CentralSquare PSA Attachment E

19 25. Governing Law

This Agreement shall be governed and construed in accordance with the laws of the State of California, without reference to its conflicts of laws principles. Any action or proceeding to enforce the terms of this Agreement shall be brought in the courts of Alameda County, Oakland, California and each party agrees to waive any objections to personal jurisdiction and venue in the courts of Alameda County, Oakland, California.

26. Headings

Headings and captions used to introduce Sections and paragraphs of this Agreement are for convenience, only, and have no legal significance.

27. Construction
(a) Acceptance or acquiescence in a prior course of dealing or a course of performance rendered under this Agreement or under any Change Order, or Change Notice, shall not be relevant in determining the meaning of this Agreement even though the accepting or acquiescing party has knowledge of the nature of the performance and opportunity for objection. (b) The language in all parts of this Agreement and any Purchase Order, Change Order, or Change Notice, shall in all cases be construed in whole, according to its fair meaning, and not strictly for or against, either Contractor, City regardless of the drafter of such part.

28. Waiver

No covenant, term, or condition of this Agreement may be waived except by written consent of the party against whom the waiver is claimed and the waiver of any term, covenant or condition of this Agreement shall not be deemed a waiver of any subsequent breach of the same or any other term, covenant or condition of this Agreement.

29. Independent Contractor

(a) Rights and Responsibilities

It is expressly agreed that in the performance of the services necessary to carry out this Agreement, Contractor shall be, and is, an independent contractor, and is not an employee of the City. Contractor acknowledges and agrees that all of Contractor’s employees and subcontractors are under the sole direction and control of Contractor and City shall have no authority over or responsibility for such employees and subcontractors of Contractor. Contractor has and shall retain the right to exercise sole direction and supervision of the services, and full control over the employment, direction, compensation and discharge of all persons City of Oakland-CentralSquare PSA Attachment E

20 assisting Contractor in the performance of Contractor’s services hereunder.

Contractor shall be solely responsible for all matters relating to the payment of his/her employees, including compliance with social security, withholding and all other regulations governing such matters, and shall be solely responsible for Contractor's own acts and those of Contractor’s subordinates and employees.

Contractor will determine the method, details and means of performing the services described in EXHIBIT 1.

(b) Contractor’s Qualifications

Contractor represents that Contractor has the qualifications and skills necessary to perform the services under this Agreement in a competent and professional manner without the advice or direction of the City. This means Contractor is able to fulfill the requirements of this Agreement. Failure to perform all of the services required under this Agreement will constitute a material breach of the Agreement and may be cause for termination of the Agreement. Contractor has complete and sole discretion for the manner in which the work under this Agreement is performed. Contractor shall complete and submit to City, Schedule M- Independent Contractor Questionnaire, prior to the execution of this Agreement.

Contractor is responsible for paying, when due, all income taxes, including estimated taxes, incurred as a result of the compensation paid by the City to Contractor for services under this Agreement. On request, Contractor will provide the City with proof of timely payment. Contractor agrees to indemnify the City for any claims, costs, losses, fees, penalties, interest or damages suffered by the City resulting from Contractor’s failure to comply with this provision.

(d) Non-Exclusive Relationship

Contractor may perform services for, and contract with, as many additional clients, persons or companies as Contractor, in his or her sole discretion, sees fit.

(e) Tools, Materials and Equipment

Contractor will supply all tools, except those tools, materials, equipment specified herein, if any, required to perform the services under this Agreement.

(f) Cooperation of the City

The City agrees to comply with all reasonable requests of Contractor necessary to the performance of Contractor’s duties under this Agreement.

City of Oakland-CentralSquare PSA Attachment E

21 (g) Extra Work

Contractor will do no extra work under this Agreement without first receiving prior written authorization from the City.

30. Attorneys’ Fees
If either party commences an action or proceeding to determine or enforce its rights hereunder, the prevailing party shall be entitled to recover from the losing party all expenses reasonably incurred, including court costs, reasonable attorneys' fees and costs of suit as determined by the court.

31. Counterparts

This Agreement may be executed in any number of identical counterparts, any set of which signed by both parties shall be deemed to constitute a complete, executed original for all purposes.

32. Remedies Cumulative

The rights and remedies of either Party provided in this Agreement shall not be exclusive and are in addition to any other rights and remedies provided by law, including the California Uniform Commercial Code.

33. Severability/Partial Invalidity

If any term or provision of this Agreement, or the application of any term or provision of this Agreement to a particular situation, shall be finally found to be void, invalid, illegal or unenforceable by a court of competent jurisdiction, then notwithstanding such determination, such term or provision shall remain in force and effect to the extent allowed by such ruling and all other terms and provisions of this Agreement or the application of this Agreement to other situation shall remain in full force and effect.

Notwithstanding the foregoing, if any material term or provision of this Agreement or the application of such material term or condition to a particular situation is finally found to be void, invalid, illegal or unenforceable by a court of competent jurisdiction, then the Parties hereto agree to work in good faith and fully cooperate with each other to amend this Agreement to carry out its intent.

34. Access

Access to City’s premises by Contractor shall be subject to the reasonable security and operational requirements of City. To the extent that Contractor’s obligations under this Agreement or any Purchase Order, Change Order, or Change Notice, require the performance City of Oakland-CentralSquare PSA Attachment E

22 of Services or Work by Contractor on City’s property or property under City's control, Contractor agrees:

(i) to accept full responsibility for performing all Services or work in a safe manner so as not to jeopardize the safety of City's personnel, property, or members of the general public; and
(ii) to comply with and enforce all of City's applicable regulations, policies, and procedures including, without limitation, those with respect to security, access, safety and fire protection, City’s policy against sexual harassment, and all applicable state and municipal safety regulations, building codes or ordinances.

35. Entire Agreement of the Parties

This Agreement supersedes any and all Agreements, either oral or written, between the parties with respect to the rendering of services by Contractor for the City and contains all of the representations, covenants and Agreements between the parties with respect to the rendering of those services. Each party to this Agreement acknowledges that no representations, inducements, promises or Agreements, orally or otherwise, have been made by any party, or anyone acting on behalf of any party, which are not contained in this Agreement, and that no other Agreement, statement or promise not contained in this Agreement will be valid or binding.

36. Modification

Any modification of this Agreement will be effective only if it is in a writing signed by all parties to this Agreement.

37. Notices

If either party shall desire or be required to give notice to the other, such notice shall be given in writing, via facsimile and concurrently by prepaid U.S. certified or registered postage, addressed to recipient as follows:

(City of Oakland) Oakland Police Department
Nicole Freeman
455 7th Street, 2nd Floor
Oakland, CA 94607

(Contractor) CentralSquare Technologies
Attn: Legal/Contracts
1000 Business Center Drive
Lake Mary, FL 32746

City of Oakland-CentralSquare PSA Attachment E

23 Any party to this Agreement may change the name or address of representatives for purpose of this Notice paragraph by providing written notice to all other parties ten (10) business days before the change is effective.

38. No Third Party Beneficiary

This Agreement shall not be construed to be an agreement for the benefit of any third Party or parties, and no third party or parties shall have any claim or right of action under this Agreement

39. Survival

Sections (2, 6, 7, 8, 9, 10, 13, 14, 15, 16, 17, 20, 25, 30 and 38) of this Agreement, along with any other provisions which by their terms survive, shall survive the expiration or termination of this Agreement.

40. Time is of the Essence

The Special Circumstances of this Agreement require each Party’s timely performance of its obligations under this Agreement. Each Party agrees perform its applicable obligations for implementation in accordance with the mutually agreed upon Project Schedule.

41. Authority

Each individual executing this Agreement or any Purchase Order, Change Order or Change Notice, hereby represents and warrants that he or she has the full power and authority to execute this Agreement or such Purchase Order, Change Order or Change Notice, on behalf of the named party such individual purports to bind.

City of Oakland-CentralSquare PSA Attachment E

24 SO AGREED:

City of Oakland, CentralSquare Software Systems
a municipal corporation

____________________________________ ___________________________________ (City Administrator’s Office) (Date) (Signature) (Date)

00200550
____________________________________ ___________________________________ (Department Head Signature) (Date) Business Tax Certificate No.

Approved as to form and legality: _______________________ Resolution Number

____________________________________
(City Attorney’s Office Signature) (Date)

City of Oakland-CentralSquare PSA Attachment E

25 ATTACHMENT A

Schedule Q

INSURANCE REQUIREMENTS
Professional/Cyber Liability Exposures
(Revised 1/13/2017:dkg)

a. General Liability, Automobile, Workers’ Compensation and Professional Liability

Contractor shall procure, prior to commencement of service, and keep in force for the term of this contract, at Contractor's own cost and expense, the following policies of insurance or certificates or binders as necessary to represent that coverage as specified below is in place with companies doing business in California and acceptable to the City. sThe insurance shall at a minimum include:

i. Commercial General Liability insurance shall cover bodily injury, property damage and personal injury liability for premises operations, independent contractors, products-completed operations personal & advertising injury and contractual liability. Coverage shall be at least as broad as Insurance Services Office Commercial General Liability coverage (occurrence Form CG 00 01)

Limits of liability: Contractor shall maintain commercial general liability (CGL) and, if necessary, commercial umbrella insurance with a limit of not less than $2,000,000 each occurrence. If such CGL insurance contains a general aggregate limit, either the general aggregate limit shall apply
separately to this project/location or the general aggregate limit shall be twice the required occurrence limit. Such limits may be met through a combination of primary and umbrella/excess coverages.

ii. Automobile Liability Insurance. Contractor shall maintain automobile liability insurance for bodily injury and property damage liability with a limit of not less than $1,000,000 each accident. Such insurance shall cover liability arising out of any auto (including owned, hired, and non-owned autos). Coverage shall be at least as broad as Insurance Services Office Form Number CA 0001.

iii. Worker's Compensation insurance as required by the laws of the State of California, with statutory limits, and statutory coverage may include Employers’ Liability coverage, with limits not less than $1,000,000 each accident, $1,000,000 policy limit bodily injury by disease, and $1,000,000 each employee bodily injury by disease. The Contractor certifies that he/she is aware of the provisions of section 3700 of the California Labor Code, which requires every employer to provide Workers' Compensation coverage, or to undertake City of Oakland-CentralSquare PSA Attachment E

26 self-insurance in accordance with the provisions of that Code. The Contractor shall comply with the provisions of section 3700 of the California Labor Code before commencing performance of the work under this Agreement and thereafter as required by that code.

iv. Technology Professional Liability (Errors and Omissions) OR Cyber Liability Insurance appropriate to the Consultant’s profession, with limits not less than $2,000,000 per occurrence or claim, $2,000,000 aggregate. Coverage shall be sufficiently broad to respond to the duties and obligations as is undertaken by Consultant in this agreement and shall include, but not be limited to, claims involving infringement of intellectual property, including but not limited to infringement of copyright, trademark, trade dress, invasion of privacy violations, information theft, damage to or destruction of electronic information, release of private information, alteration of electronic information, extortion and network security. The policy shall provide coverage for breach response costs as well as regulatory fines and penalties as well as credit monitoring expenses with limits sufficient to respond to these obligations.

b. Terms Conditions and Endorsements

The aforementioned insurance shall be endorsed and have all the following conditions:

i. Insured Status (Additional Insured): Contractor shall provide additional insured status including the City of Oakland, its Councilmembers, directors, officers, agents, employees and volunteers as insured’s under the Commercial General Liability policy. General liability coverage can be provided in the form of an endorsement to the Consultant’s insurance (at least as broad as ISO Form CG 20 10 11 85 or both CG 20 10, CG 20 26, CG 20 33, or CG 20 38; and CG 20 37 forms if later revisions used). A STATEMENT OF ADDITIONAL

INSURED STATUS ON THE ACORD INSURANCE CERTIFICATE FORM

IS INSUFFICIENT AND WILL BE REJECTED AS PROOF OF MEETING THIS REQUIREMENT; and

ii. Coverage afforded on behalf of the City, Councilmembers, directors, officers, agents, employees and volunteers shall be primary insurance.

Any other insurance available to the City Councilmembers, directors, officers, agents, employees and volunteers under any other policies shall be excess insurance (over the insurance required by this Agreement); and

iii. Cancellation Notice: Each insurance policy required by this clause shall provide that coverage shall not be canceled, except with notice to the Entity; and

City of Oakland-CentralSquare PSA Attachment E

27 iv. Certificate holder is to be the same person and address as indicated in the “Notices” section of this Agreement; and

v. Insurer shall carry insurance from admitted companies with an A.M. Best Rating of A:VII, or better.

c. Insurance Interpretation

All endorsements, certificates, forms, coverage and limits of liability referred to herein shall have the meaning given such terms by the Insurance Services Office as of the date of this Agreement.

d. Proof of Insurance

Contractor will be required to provide proof of all insurance required for the work prior to execution of the contract. Failure to provide the insurance proof requested or failure to do so in a timely manner shall constitute ground for rescission of the contract award.

e. Subcontractors

Should the Contractor subcontract out the work required under this agreement, they shall include all subcontractors as insured’s under its policies or shall maintain separate certificates and endorsements for each subcontractor. As an alternative, the Contractor may require all subcontractors to provide at their own expense evidence of all the required coverages listed in this Schedule. If this option is exercised, both the City of Oakland and the Contractor shall be named as additional insured under the subcontractor’s General Liability policy. All coverages for subcontractors shall be subject to all the requirements stated herein. The City reserves the right to perform an insurance audit during the course of the project to verify compliance with requirements.

f. Waiver of Subrogation

Contractor waives all rights against the City of Oakland and its Councilmembers, officers, directors, employees and volunteers for recovery of damages to the extent these damages are covered by the forms of insurance coverage required above.

g. Evaluation of Adequacy of Coverage

The City of Oakland maintains the right to, acting reasonably, modify, delete, alter or change these requirements, with reasonable notice, upon not less than ninety (90) days prior written notice.

City of Oakland-CentralSquare PSA Attachment E

28 h. Higher Limits of Insurance

If the contractor maintains higher limits than the minimums shown above, the City shall be entitled to coverage for the higher limits maintained by the contractor.

k. Claims Made Policies
If any of the required policies provide coverage on a claims-made basis:

1. The Retroactive Date must be shown and must be before the date of the contract or the beginning of contract work.

2. Insurance must be maintained and evidence of insurance must be provided for at least three (3) years after completion of the contract of work.

3. If coverage is canceled or non-renewed, and not replaced with another claims- made policy form with a Retroactive Date prior to the contract effective date, the Consultant must purchase “extended reporting” coverage for a minimum of three (3) years after completion of contract work.

END OF SCHEDULE Q – INSURANCE REQUIREMENT

Attachment F – Oakland Central Square Contract Costing

One-time
Fees
Recurring Renewal/Maintenance Optional Optional

Year 1 Year 2

Application Software/Services Qty 5/1/2022-
4/30/2023
5/1/2023-
4/30/2024
5/1/2024-
4/30/2025
5/1/2025-
4/30/2026
5/1/2026-
4/30/2027

IQ CrimeView Advanced Reports
Annual Subscription Fee
Software 1 $
9,975.00
$
-
$
-
$
-
$
-

IQ - CrimeView Dashboard Annual
Subscription Fee
Software 1 $
13,615.88
$
-
$
-
$
-
$
-

IQ CrimeView Desktop License
Annual Maintenance Fee
Software 1 $
5,622.75
$
5,903.89
$
6,199.08
$
6,509.04
$
6,834.49

Crimemapping.com Software 1 $
-
$
-
$
-
$
-
$
-

Quote No. Q-63453

Professional Services -- Complete
P1 integration
Services N/A $
11,700.00

CrimeView Analytics:

Designer/Admin License
Subscription Annual Subscription
Fee
Software 4 $
3,000.00
$
3,150.00
$
3,307.50
$
3,472.88
$
3,646.52

CrimeView Analytics: Single Data
Set (3 years data) Non-CST Sys.

Subscription - RMS Arrests
Software 1 $
2,952.84
$
3,100.48
$
3,255.51
$
3,418.28
$
3,589.20

CrimeView Analytics: Single Data
Set (3 years data) Non-CST Sys.

Subscription - Stop Data (Using
field interview data template)
Software 1 $
2,952.84
$
3,100.48
$
3,255.51
$
3,418.28
$
3,589.20

Attachment F – Oakland Central Square Contract Costing

CrimeView Analytics: Single Data
Set (Add'l Yr) Subscription Fee - 7
additional years data- RMS
Arrests
Software 7 $
3,500.00
$
3,675.00
$
3,858.75
$
4,051.69
$
4,254.27

CrimeView Analytics: Single Data
Set (Add'l Yr) Subscription Fee - 7
additional years data - Stop Data
Software 7 $
3,500.00
$
3,675.00
$
3,858.75
$
4,051.69
$
4,254.27

CrimeView Analytics: Standard (3
years data) Non-CST System
Subscription - CAD Incident &
RMS Incident
Software 1 $
7,710.20
$
8,095.71
$
8,500.50
$
8,925.52
$
9,371.80

CrimeView Analytics: Standard
(Add'l Year) System Subscription -
7 additional years data CAD
Incidents & RMS Incidents
Software 7 $
4,900.00
$
5,145.00
$
5,402.25
$
5,672.36
$
5,955.98

Quote No. Q-62250

Professional Services Services N/A $
5,000.00

The following Services and Software fees will only be invoiced upon authorization to proceed from the agency. The dates for the Software - Recurring Renewal/Maintenance period are estimated. The actual renewal period will begin on the Go-Live date of the software.

Quote No. Q-64054

Professional Services --
CrimeView Analytics Upgrade
Services N/A $
16,380.00

CrimeView Analytics: Single Data
Set (3 years data) Non-CST Sys.

Subscription - LPR
Software 1 $
1,800.00
$
1,890.00
$
1,984.50
$
2,083.73
$
2,187.91

Attachment F – Oakland Central Square Contract Costing

CrimeView Analytics: Single Data
Set (3 years data) Non-CST Sys.

Subscription - Shotspotter
Software 1 $
1,800.00
$
1,890.00
$
1,984.50
$
2,083.73
$
2,187.91

Total $
33,080.00
$
61,329.51
$
39,625.56
$
41,606.84
$
43,687.18
$
45,871.54
$
265,200.63
The prices quantified above are for the software and services contained herein. If any additional software or services are r equested, then a change order/amendment shall be entered into with requisite pricing. An increase in the CentralSquare Software licenses granted to the City will result in an increase in the Annual Renewal fees.

Oakland City CouncilJuly 19, 2022

Oakland City Council
July 19, 2022