My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Timmons Group 12/4/2020
>
Contracts
>
6 Years Then Destroy
>
2025
>
Timmons Group 12/4/2020
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/19/2025 1:42:43 PM
Creation date
12/16/2020 12:26:53 PM
Metadata
Fields
Template:
Contracts
Contractor's Name
Timmons Group
Approval Date
12/4/2020
Council Approval Date
12/2/2020
End Date
12/31/2025
Department
Purchasing
Department Project Manager
Theresa Bauccio-Teschlog
Subject / Project Title
Computerized Maintenance & Asset Mgmt (CMAMS)
Tracking Number
0002581
Total Compensation
$639,925.00
Contract Type
Agreement
Contract Subtype
Professional Services
Retention Period
6 Years Then Destroy
Document Relationships
Timmons Group Inc 2/16/2025 Change Order 2
(Contract)
Path:
\Documents\City Clerk\Contracts\Agreement\Other Procurement Agreements
Timmons Group Inc. 11/8/2023 Amendment 1
(Contract)
Path:
\Records\City Clerk\Contracts\6 Years Then Destroy\2025
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
75
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
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 APl to import asset readings from <br /> SCADA historian into Cityworks. <br /> Phase 5,Task 19:Assumptions: <br /> • Everett is 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, etc.)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 /> e The development of the integration will require approximately 8-10 weeks <br /> Phase 5, Task 20: TRAKiT Integration <br /> Utilizing 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 (24 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 /> e The development of the integration will require approximately 3-5 weeks <br /> Phase 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 /> Azure development environment <br /> • GraniteNet integration: <br /> • Testing <br /> • Knowledge transfer <br /> 9 Migrated existing CCTV data <br /> • Cayenta integration: <br /> 281Page <br />
The URL can be used to link to this page
Your browser does not support the video tag.