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
i Costs <br /> 2) Gather configuration data and workflows with the Functional Groups for: <br /> • Asset categories <br /> • Work order and inspection workflows <br /> i. Employees <br /> ii. Equipment <br /> iii. Materials <br /> iv. Prioritization, Scheduling, and Backlog Management <br /> v. Dispatching <br /> vi. Notifications <br /> vii. Data to be collected <br /> viii. Inspection criteria <br /> • Interfaces/integration <br /> i. Functional requirements <br /> ii. User stories <br /> iii. Methodology <br /> • Reporting <br /> i. Data required <br /> ii. Format <br /> iii. Methodology <br /> • Data migration identified in the RFP <br /> These workshops are designed to establish and assess the Business Requirements, User Requirements. <br /> and Functional Requirements that must be considered when developing the Software Design and <br /> Configuration Plan (SD&C) as well as to design the Cityworks configuration and database necessary for <br /> implementation, the integrations and data conversion. It is expected that the City will provide the facilities <br /> for the on-site workshops and coordinate staff attendance for all workshops. <br /> For the first 30 minutes of the workshop our implementation team will conduct a brief software knowledge <br /> transfer session. The session will give the workshop attendees an opportunity to review and understand <br /> the software, potential impacts and changes in their daily business processes, and the purpose of <br /> adopting the new tools. It has been our experience that successful adoption of Cityworks is supported by <br /> continued, repeated exposure of the software during the workshops and review meetings. During the <br /> workshops, our implementation team will analyze the various technological, operational, and <br /> organizational elements of the City's business. This will be an essential procedure in order to ensure the <br /> planned Cityworks implementation and expected system interfaces are capable of delivering the feature- <br /> rich data needed to support the numerous complex operations and maintenance activities undertaken by <br /> the various departments. <br /> In support of these efforts, our implementation team will analyze with each Functional Group the following <br /> critical elements: <br /> ® Business Drivers—The core functions that will benefit from the implementation of the <br /> Cityworks solution. These may include inventory, custom billing, time tracking, engineering <br /> planning and design, construction inspection and administration, operations and maintenance, <br /> inspections, regulatory compliance, customer service, disaster preparedness and emergency <br /> response, executive decision processes, etc. <br /> Workflows—Current departmental/Functional Group (internal and external) business <br /> processes and workflows that will either contribute to, or be replaced by, the planned Cityworks <br /> implementation. Key workflows that should be analyzed include, but are not limited to, <br /> inventory/data capture and maintenance, work planning. scheduling, and tracking, data <br /> distribution, data consumption, system planning and analysis, customer inquiry, reporting, etc. <br /> 201Page <br />
The URL can be used to link to this page
Your browser does not support the video tag.