Arizona State University Police Department Request for Proposals #: CAD/RMS/Mobile. Mapping Functional Requirements

Transcription

1 Geofile Administration Map Data Map Functionality Map Navigation Item # Mapping S M A U Comments 1 Geofile Administration Ability to accommodate an unlimited number of map layers (if the 2 number of layers is limited, please specify the maximum number of layers in the comments section). 3 Ability to support scale dependent layers. 4 Ability to support a map layer for aerial spatial images. 5 Ability to add geofile layers as needed. 6 Ability to determine which map layers are available for each application (e.g., CAD, Mobile, RMS, AFR). 7 Ability to change reporting boundaries (e.g., areas, beats, districts). 8 Ability for a single geofile layer to contain overlapping polygons. Arizona State University Police Department Request for Proposals #: CAD/RMS/Mobile Mapping Functional Requirements System Functionality Modification Needed. At no extra Cos Modification needed at an additional cost Unable to meet the requirement Please explain any line items (from the left that are not an "out of the box" standard but are part of your overall proposal; specifically, why the particular line item is not an "out of the box" standard. Additionally, please identify what potential effect this may have upon meeting a January 13, 2020 implementation date. (Required for any items marked "M", "A", or "U") Your proposed solution will be evaluated based on the value of each of these items combined and will not negatively impact the proposal Ability to update the system with a new geofile without system downtime. Ability to update the system with a new geofile without system performance degradation. Arizona State University Police Department Mapping Functional Requirements 1 of 5

2 11 Ability to test new geofile updates "offline" for accuracy and errors, prior to updating the "live" geofile. 12 Ability for geofile updates to be recognized without requiring logging off and logging back on to the system. 13 Map Data 14 Ability to support the following location fields, including, but not limited to: 15 Apartment building name 16 Apartment number (e.g., ½, #5, 2D, D2) 17 Building number 18 Block range 19 Business name 20 Business owner 21 City 22 Civic associations (e.g., areas, neighborhoods, community names) 23 Common place name 24 County 25 District - Campus (West, Tempe, Polytechnic, Downtown) 26 Exact address: 27 Fractional addresses 28 Alphanumeric addresses 29 Floor plans 30 Intersections 31 Law enforcement Jurisdiction 32 On ramps, off ramps, exit numbers (including direction) 33 Prefix 34 Railway mile markers 35 Reporting area 36 Road classification 37 Street abbreviation 38 Street alias 39 Street name Arizona State University Police Department Mapping Functional Requirements 2 of 5

3 40 Street type 41 Suffix 42 Suite number 43 Trail markers 44 X/Y coordinates 45 X/Y/Z coordinates 46 Other agency defined data 47 Ability to associate geofile data with the following: 48 Address 49 Beats 50 Cross street 51 Entire common place or business name and aliases 52 High and low cross streets 53 Jurisdiction 54 Reporting district 55 Response area 56 Sectors 57 X/Y coordinates 58 X/Y/Z coordinates 59 Ability to cross-reference addresses and locations with: 60 Entire common place or business name and aliases 61 Law enforcement-defined reporting areas 62 Other identifiers 63 Street aliases 64 X/Y coordinates 65 X/Y/Z coordinates 66 Zip codes 67 Map Functionality 68 Ability to turn map layers off and on. 69 Ability to switch between night time and day time cartography versions. 70 Ability to save display settings at the user level. Arizona State University Police Department Mapping Functional Requirements 3 of 5

4 71 Ability to tie user driven map configurations and settings to login (e.g., roaming profiles). 72 Ability to measure the distances on the map. 73 Ability to measure area on the map. 74 Ability to attach files to addresses (e.g., apartment maps, photos, aerial images). 75 Ability to attach premise information (e.g., hazards) to addresses Ability to click on a location on a map and pull up any supplemental information (e.g., fire pre-plan, hazards, incident history) associated with that location. Ability to click on a location on a map and pull up any supplemental information associated with a Campus defined parameter around the location (address, building, block, etc.). Ability to display flags on locations containing additional information 78 (e.g., fire pre-plans, hazards, and Hazardous Materials, incident history). 79 Map Navigation 80 Ability to provide the following map navigation functionality: 81 Pan from given area to adjacent area 82 Return back to previous view 83 Zoom in on area for enhanced detail 84 Zoom out of an area 85 Move up and down 86 Move left and right 87 Ability to use a mouse to "click" a point at any zoom level and have the following information displayed: 88 Street name (including alias) 89 Street type 90 Block number or address range 91 Latitude/longitude Arizona State University Police Department Mapping Functional Requirements 4 of 5

5 92 Coordinates from various reference systems 93 Prefix directional (N, E, S, W, NE, NW, SE, SW) 94 Suffix directional (N, E, S, W, NE, NW, SE, SW) 95 Sub-address (e.g., unit number, building floor, apartment number). 96 Ability to use the mouse to "hover" on any point at any zoom level and have the following information displayed: 97 Street name (including alias) 98 Street type 99 Block number or address range 100 Latitude/longitude 101 Coordinates from various reference systems 102 Prefix directional (N, E, S, W, NE, NW, SE, SW) 103 Suffix directional (N, E, S, W, NE, NW, SE, SW) 104 Sub-address (e.g., unit number, building floor, apartment number). 105 Ability to configure list of what information is featured in mouse "hover" display. Arizona State University Police Department Mapping Functional Requirements 5 of 5