Laserfiche WebLink
<br />Page 40 of 58 <br /> <br />f. Pipe diameters. <br />g. Work order numbers. <br />h. Street names and other geospatial notations. <br />Provide dropdown menus to quickly select common <br />information, including defects, pipe materials, survey <br />purpose, locations, and pipe usage. <br />D <br /> <br />Layer elements must be color-coded, with options <br />for standard color schemes and user-configurable <br />color schemes. <br />D <br /> <br /> <br />3. Inspection data export and import <br />Functionality <br />D = Desired <br />R = Required <br />No Partial Full <br />Can export completed inspections from the <br />proposed inspection software to Cityworks. The <br />system must allow configuration for: <br />a. Inclusion or exclusion of certain inspection <br />statuses. <br />b. Specification of Cityworks Template to be <br />used when the completed inspection is <br />completed in Cityworks. <br />R <br /> <br />Include functionality to import new inspections from <br />a defined set of Trimble Cityworks inspection work <br />items into the inspection software as new inspection <br />tasks to be completed. <br />R <br /> <br />A user interface must be provided to configure data <br />mapping between Cityworks and the inspection <br />system. The interface must: <br />a. Specify the Cityworks entity type and the <br />entity type in the inspection software. <br />b. Specify the task mappings between <br />Cityworks and entity type and the inspection <br />system software. <br />c. Specify the criteria for setting the fields in <br />Cityworks, such as workorder status, <br />inspection status, and related task statuses. <br />R <br />