Laserfiche WebLink
<br />Page 8 of 58 <br /> <br />A. Historical inspection general import software requirements <br />Functionality <br />D = Desired <br />R = Required <br />Enable the import of all sewer and drainage inspection data, including related <br />metadata, from the CUES GraniteNET system into the target system, ensuring <br />data integrity and completeness. It must also import all past inspections from <br />historical records and comparison to current and future inspections. <br />R <br />Import all past completed inspections from the CUES GraniteNET system. It <br />must also import all recorded observations and their associated attributes, <br />including, but not limited to, defect codes, severity levels, and descriptions. <br />R <br />Import all inspection ratings and scoring data, ensuring alignment with <br />NASSCO7 inspection standards. R <br />Import all associated videos and still images of inspections. Media files must be <br />linked to their corresponding inspections for easy reference and retrieval. R <br />Import all relevant metadata, including, but not limited to: <br />a. Inspection dates and times. <br />b. Inspection locations, e.g., GPS coordinates and pipe segment identifiers. <br />c. Inspector details, e.g., name and ID. <br />d. Equipment used, e.g., camera model and calibration data. <br />R <br />Import any other related and associated data from the CUES GraniteNET system <br />necessary for comprehensive inspection records. R <br />Support importing data in formats generated by CUES GraniteNET, such as <br />database backups, export files, or XML/CSV files. R <br />Import process must include a mapping interface that allows users to align <br />CUES GraniteNET data fields with corresponding fields in the target system. <br />Field mappings must be saved as templates to reuse. <br />R <br />Validate data before import to identify missing or inconsistent information. All <br />errors detected during the import process must be logged, with detailed error <br />messages to facilitate troubleshooting. <br />R <br />Create detailed logs of each import process, including: <br />a. Start and end times of the import. <br />b. Number of records imported successfully. <br />c. Number and details of records with errors. <br />R <br />Generate reports summarizing issues encountered during the import process <br />for review. R <br />Provide an intuitive interface for configuring import settings, viewing logs, and <br />resolving errors. R <br /> <br />EXHIBIT D