Laserfiche WebLink
<br />Page 37 of 58 <br /> <br /> <br />2. Inspection software functionality requirements <br />Functionality <br />D = Desired <br />R = Required <br />No Partial Full <br />Read asset data from ESRI ArcGIS web services to <br />import all assets from drainage and sewer system <br />into its database for use in inspection software <br />components. <br />R <br /> <br />Allow users to specify the scope of data to retrieve, <br />such as geographic areas or specific asset categories. R <br />Support secure connections, including authentication <br />methods such as API keys or tokens. Authentication <br />to the Portal for ArcGIS instance must be <br />configurable via: <br />a. Token-based authentication. <br />b. Built-in account authentication. <br />c. Single Sign-On (SSO). <br />R <br /> <br />Allow users to create and save customer filters for <br />dates and inspection statuses. R <br />Integrate with ESRI ArcGIS REST services (APIs) <br />hosted within the City’s Portal for ArcGIS. R <br />Group condition descriptions and codes for ease of <br />use. R <br />Retrieve all relevant asset data, including, but not <br />limited to: <br />a. Drainage and sewer system assets, such as <br />pipes, manholes, and catch basins. <br />b. Associated metadata, such as asset IDs, <br />dimensions, materials, and conditions. <br />c. Geospatial data, such as coordinates, spatial <br />relationships, and maps. <br />R <br /> <br />When importing data from the ArcGIS system to the <br />inspection software, the software must designate <br />mandatory and optional fields or properties for <br />assets. <br />R <br />