Laserfiche WebLink
associated with a related GIS asset and would be triggered both for corrective work (max or min threshold <br />hit) as well as preventive maintenance cycles (every 10 runtime hours) based on settings defined <br />in Cityworks. <br />Phase 5, Task 19: City Responsibility: <br />• City will schedule and provide attendance at discovery workshop for integration functional requirements & <br />design. (8-16 hours) <br />• Review of design documents once designed (2-4 FTE hours) <br />Phase 5, Task 19: Timmons Group Responsibilities and Deliverables: <br />• Develop integration per functional requirements <br />• Develop list of assets, their SCADA tag number, and associated work activities to be triggered by interval <br />or threshold readings. <br />• Verify GIS data will support the integration and recommend changes if needed. <br />• Configure work orders <br />• Configure asset reading settings for assets <br />• Design, build, test, and deploy application that will use Cityworks API to import asset readings from <br />SCADA historian into Cityworks. <br />Phase 5, Task 19: Assumptions: <br />• Everettis responsible for revising GIS data model and capturing asset data to support this integration. <br />• Everett is responsible for any changes to the network and IT infrastructure (if needed) to make the <br />SCADA historian data available to Cityworks. <br />• This integration will be designed to trigger work activities based off measured asset <br />reading value (pressure, runtime hours, eta) provided from SCADA The functionality will not include the ability <br />to trigger work from a combination of reading value and time. <br />• City will provide review comments within 10 business days or a mutually agreed upon timeframe <br />• It has been indicated by Everett that triggered PM activities only need to be based on asset readings and <br />do not need to include time. <br />Phase 5, Task 19: Estimated Timeframe: <br />• The development of the integration will require approximately 8-10 weeks <br />P hase 5, Task 20: TRAKiT Integration <br />U tilizing the methodology outlined above Timmons Group will design and develop the integration between <br />TRAKiT and Cityworks. <br />Phase 5, Task 20: City Responsibility: <br />• City will schedule and provide attendance at discovery workshop for integration functional requirements & <br />design. (8-16 hours) <br />• Review of design documents once designed (2-4 FTE hours) <br />Phase 5, Task 20• Timmons Group Responsibilities and Deliverables: <br />• Develop integration per functional requirements <br />• Develop Cityworks SOPs for integration workflows <br />Phase 5, Task 20; Assumptions: <br />• City will provide review comments within 10 business days or a mutually agreed upon timeframe <br />Phase 5, Task 20: Estimated Timeframe: <br />• The development of the integration will require approximately 3-5 weeks <br />P hase 5 Exit Criteria <br />• Functional Requirements workshop meeting minutes <br />• Integration Review meeting minutes <br />• Integration functionality, code, etc. required for integration migrated from the City provided off -site <br />Aszure development environment <br />• GraniteNet integration: <br />o Testing <br />o Knowledge transfer <br />o Migrated existing CCTV data <br />• Cayenta integration: <br />28IPage <br />