HomeMy WebLinkAboutPROFESSIONAL SERVICES CONTRACT CHANGE ORDER TO IMPLEMENT CITYWORKS AMS SOFTWARE AND INTEGRATE WITH ENQUESTA CIS SOFTWARE PROFESSIONAL SERVICES CONTRACT CHANGE ORDER
CO NUMBER I
BID ITEM 12-221
DATE 1/22/2019
PROJECT TITLE Cityworks AMS Implementation
ORIGINAL CONTRACT DATE December 17,2013
OWNER AUGUSTA,GEORGIA PO NUMBER p230073
The following change is hereby made to the contract for the above project.
Description of Change(for a more detailed description see attached proposal):
Complete the final phase of the Cityworks AMS Implementation for Augusta Utilities to include the
Customer Service/Metering Division and integrate with enQuesta Customer Billing System.
PAYEE Woolpert,Inc.
TOTAL AMOUNT OF THIS CHANGE ORDER $ 200.000.00
The contract time will be INCREASED by 3.65 calendar days as a result of this change.
ORIGINAL CONTRACT AMOUNT $ 627,355.00
PREVIOUS CHANGE ORDER(INCREASE) $ $0.00
THIS CHANGE ORDER(INCREASE) $ 200,000.00
TOTAL REVISED CONTRACT AMOUNT WITH CHANGE ORDER $ 827,355.00
FUNDING NUMBER/ACCOUNT NUMBER 507-04-3490 54-24120
JL 81300015 54-24120
PROPOSED BY:
DATE: I I )5 l
CONSU '
REQUESTED BY: DATE: 1/25774:417
,
AUD P JECT AGER
SUBMITTED BY: /t:1Ma) DATE: Ilza//
1 1
DEPARTMENT HEAD I
APPROVED BY: %s
•ATE:
AftMAYOR_ __-.
410/14
STATEMENT OF WORK
City of Augusta
Utilities Meter Shop Cityworks Implementation
and Integration with enQuesta CIS
City of Augusta,Georgia
November 5,2018
Prepared by Woolpert,Inc.
7400 Beaufont Springs Drive
Suite 200
Richmond,VA 23225
www.woolpert.com
lkA/
WOO L P E R T
ARCHITECTURE I ENGINEERING I GEOSPATIAL
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Table of Contents
INTRODUCTION 2
OVERVIEW 3
TECHNICAL APPROACH 7
QUALITY MANAGEMENT PROCESS 8
PHASE 1 -PROJECT MANAGEMENT 11
Project Administration 11
Project Schedule Coordination 12
Project Manager Status Meetings 12
Internal Coordination Meetings 13
Change Control 14
PHASE 1 -INTEGRATION PLANNING 16
Task 1.1: Software Requirements Specification (SRS) Development 16
PHASE 2-SYSTEM DESIGN AND CONFIGURATION 18
Task 2.1: Develop Configuration Document 18
Task 2.2: Provide Asset Management System Configuration Training 19
Task 2.3: Facilitate Core AM Software Configuration 19
Task 2.4: Facilitate Storeroom Configuration 20
Task 2.5: Phase 2 Quality Control 21
Task 2.6: Phase 2 Acceptance and Close 21
PHASE 3-ADVANCED CONFIGURATION AND FUNCTIONALITY 22
Task 3.1: System Integrations 22
Task 3.2: Legacy Data Migrations 26
Task 3.3: Custom Reports and Metrics 26
WBS Task 3.4: Phase 3 Quality Control 26
WBS Task 3.5: Phase 3 Acceptance and Close 26
PHASE 4: SYSTEM DEPLOYMENT 27
Task 4.1: Develop Non-Integrated Configuration User Acceptance Testing Plans 27
Task 4.2: Facilitate User Acceptance Testing 28
Task 4.3: Provide End-User Training 29
Task 4.4: Go-Live Et Support 29
Task 4.5: Phase 4 Quality Control 30
Task 4.6: Phase 4 Acceptance and Close 30
Table of Figures
FIGURE 1 -PROJECT LIFE-CYCLE PROCESS GROUPS 11
FIGURE 2- WOOLPERT'S PROJECT COLLABORATION WEB SITE 11
FIGURE 3-MICROSOFT PROJECT GANTT CHART 12
FIGURE 4-SAMPLE CHANGE CONTROL NOTICE 14
FIGURE 5-CHANGE CONTROL PROCESS 15
FIGURE 6-SAMPLE AM SYSTEM CONFIGURATION DOCUMENTATION TABLE OF CONTENTS 18
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Introduction
The City of Augusta,Georgia Utilities Department implemented Cityworks Asset Management System (AMS)over four
(4)years ago to manage operations and maintenance(O&M)work activities for nearly all of its divisions and work
groups. One division that did not begin using Cityworks AMS at that time was the Meter Shop.The Meter Shop was in
the midst of planning an upgrade to their enQuesta Customer Information System (CIS). In order to fully leverage
Cityworks'work management capabilities it would need to be integrated with enQuesta,so the decision was made at
that time to hold off on bringing the Meter Shop onto Cityworks until the enQuesta upgrade was complete and the
implementation of Cityworks could include the development of an interface between the two systems.
The intent of the integration is to automatically send actionable Service Orders from enQuesta to Cityworks as Work
Order so they can be assigned to field crews and for the completed Cityworks Work Orders to be automatically
communicated back to enQuesta.The intent of the automation is to speed the communication between customer billing
service representatives and field maintenance staff,eliminate duplicate entry,and ensure accurate communication
between the two groups.
Prior to development of this scope of work document,Woolpert met with City Meter Shop and City Customer Service
staff to establish some boundaries around the integration.Those boundaries are stated as guiding assumptions within
this document.They include items that define the level of complexity of the integration;such as the amount of
integration triggers between the system and the number of Cityworks Work Order templates that will be involved.The
estimate cost of this effort is related to these assumptions holding true.
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Overview
CO The project includes aspects of a typical Cityworks AMS implementation, but it more heavily a software
I I integration project that drives new Cityworks
0 0 0 configurations. It is further complicated in that the
City is currently using Cityworks in a live environment,
so new configurations and data will require careful
migration from the Development to the Production
environment.
The approach for this project will be similar to
previous Woolpert-led Cityworks implementation at
the City with the following modifications.
1. The Planning phase will be focused on driving out integration specifications and will result in a Software
Requirements Specifications document.
2. There will be fewer rounds of Cityworks configuration workshops.
3. There will be a heavy reliance on the City's Customer Billing team members to participate in design and testing
workshops.The City or a third-party will co-develop the integrations with Woolpert.
Services, and associated deliverables,are categorized into several groupings called phases, as more fully detailed in the
following sections of this document. Completion of each phase will culminate with the execution of a Phase Acceptance
and Close document signifying the City's acceptance of the services rendered to date and authorization for Woolpert to
proceed with work on subsequent phases. In some cases,work in subsequent phases will not begin until the deliverables
in previous phases have been accepted by the City. In other cases,work in multiple phases will occur simultaneously.
Our project plan, its associated budget,and schedule were developed based on many bounding assumptions inferred
from information provided to us by the City and discussions with City staff. Both parties (Woolpert and City)agree to
these bounding assumptions and understand that if they are not adhered to,there is risk for scope,schedule,and
budget impact.The following assumptions apply to this scope of work:
• The make-up of the City's project team will be as follows:
o City Project Manager—The City is to identify and empower a Project Manager who will jointly
manage the project along with the Woolpert Project Manager.The City Project Manager will be
responsible for ensuring the availability, readiness,and participation of the City resources including
City-directed sub-consultants,as well as the execution of the City-assigned tasks and completion of
the City-assigned deliverables.
o City Implementation Team—The City is to identify and empower a set of individuals that constitute
the City Core Team,also referred to as the Implementation Team.The Team will consist of Subject
Matter Experts from the Meter Shop and Customer Billing department.The selected representatives
from each of the participating departments will be available for the project throughout its entirety.
Woolpert recommends two power users from each group.We strongly recommend that no single
set of expertise/knowledge is single threaded;each group should be championed by multiple core
team members so that staff workloads and turnover does not unduly affect the project.
o City Technical Team—The City is to identify and empower a set of IT professionals to support this
project.These individuals will be known collectively as the Technical Team.The selected
Page 3 AMER
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
representatives will be available for the project throughout its entirety.The Technical Team will be
comprised of experts on each of the software and hardware components involved in this project
including, but not limited to, City servers and workstations, City network infrastructure, Esri GIS and
the City's Esri deployment,the deployed and in-use Cityworks AMS solution and the enQuesta CIS
solution with which Cityworks will be implemented.When Technical Team participation is noted
within the detailed scope of services,the expectation is that the appropriate Technical Team experts
will participate, not all of the team members.
• As many as seventy-three(73)enQuesta Service Order types across twenty(20)distinct groups will be
integrated with Cityworks.Those Service Requests are listed in the following table:
1 20 New Site Meters&Ite 6 NS MTR/REM Install
2 50 Final Bills 300 Acct 52 Final Bill Seasonal Off
3 60 Final Bills 300/301 64 Final Bill Set New Acct
4 60 Final Bills 300/301 66 Final Vacant
5 60 Final Bills 300/301 70 Final Vacant MTR Remove
6 60 Final Bills 300/301 76 Final Vacant Lock WTR
7 80 Set&Activate Accts 84 SET VACANT SETA
8 80 Set&Activate Accts 86 CONTRACT MTR RENTED
9 80 Set&Activate Accts 89 SET VAC SETA MTR INST
10 80 Set&Activate Accts 5001 NON MOVEABLE 30 DAY
11 80 Set&Activate Accts 5002 NON MOVEABLE 90 DAY
12 80 Set&Activate Accts 5003 NON MOVEABLE 1 YR
13 80 Set&Activate Accts 5004 MOVEABLE 1 YER
14 90 WTR TURN ON/OFF 53 CS SEASONAL TURN ON
15 90 WTR TURN ON/OFF 96 WTR CUST REQUEST OFF
16 90 WTR TURN ON/OFF 98 WTR CUST REQUEST ON
17 90 WTR TURN ON/OFF 170 RETURN SERVICE CALL
18 100 MTR ORD EXCHG=<1" 100 MTR EXCHG ACCT ACTIVE
19 100 MTR ORD EXCHG=<1" 104 MTR EXCHG SIZE CHANGE
20 100 MTR ORD EXCHG=<1" 105 MTR EXCHG/REM EXCHG
21 100 MTR ORD EXCHG=<1" 106 MTR EXCHG/REM INSTALL
22 100 MTR ORD EXCHG=<1" 110 MTR EXCHG/REM INSTALL HW
23 100 MTR ORD EXCHG=<1" 113 ACCT VACANT
24 130 METER ORDERS INSTALL 130 MTR INST ACCT ACTIVE
25 130 METER ORDERS INSTALL 132 MTR INST ACCT VACANT
26 130 METER ORDERS INSTALL 136 MTR INST SPRINKLER
27 150 NEW ORDERS REMOVAL 150 MTR INSTACCTACTIVE
28 150 NEW ORDERS REMOVAL 151 MTR INST ACCT VACANT
29 150 NEW ORDERS REMOVAL 152 MTR INST SPRINKLER
30 150 NEW ORDERS REMOVAL 157 MTR RMOV/REM RMOV
31 160 METER ORDERS MISC 160 MTR BOX REPAIR/REPLACE
32 160 METER ORDERS MISC 164 MTR INVESTIGATION
33 160 METER ORDERS MISC 165 MTR INVST ENDPOINT
34 160 METER ORDERS MISC 166 MTR LEAK
35 230 HAND HELD BOX 236 HH BOX CLEANOUT
Page 4 AMIE
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
36 230 HAND HELD BOX 239 HH COVERED
37 230 HAND HELD BOX 246 HH REPLACE MTR LID
38 240 HAND HELD METERS 248 HHMTR LID STUCK
39 240 HAND HELD METERS 250 HH MTR COVERED
' 40 240 HAND HELD METERS 252 HH MTR WATER IN REG
41 240 HAND HELD METERS 255 ' HH MTR IN BACKWARDS
42 240 HAND HELD METERS 258 HH MTR LEAKING
43 240 HAND HELD METERS 262 HH REG BROKEN
44 240 HAND HELD METERS 265 HH MTR BROKEN CC
45 240 HAND HELD METERS 271 HH MTR CKREAD STUCK MTR
46 240 HAND HELD METERS 272 HH REGISTER OFF
47 240 HAND HELD METERS 274 HH MTR DULL REGISTER
48 240 HAND HELD METERS 276 HH MTR UNDER WATER
49 240 HAND HELD METERS 286 HH MTR CANT LOCATE
50 240 HAND HELD METERS 287 HH VACNT CONSUMPTION
51 240 HAND HELD METERS 290 TAMPERING/STRAIGHT LINE
52 1 240 HAND HELD METERS 297 HH MTR GATE LOCKED
53 i 280 HAND HELD MISC 291 HH MISC NO SERVICE
54 ' 330 CREDIT NSF 344 CC NSF SHUT OFF W/FEE
55 330 CREDIT NSF 347 CC NSF RET CHK W/FEE
56 330 CREDIT NSF 359 CC NSF TURN ON
57 350 CREDIT TURN OFF/ON 314 CC TURN-ON MTR INSTALL
58 350 CREDIT TURN OFF/ON 315 CC TURN-OFF RE-CHECK
59 i 350 CREDIT TURN OFF/ON 316 CC TURN-OFF MTR REMOVAL
60 350 CREDIT TURN OFF/ON 318 CC TURN-OFF
61 350 CREDIT TURN OFF/ON 320 CC TURN-ON
62 350 CREDIT TURN OFF/ON 2005 STOLEN METER
63 350 CREDIT TURN OFF/ON 3315 CC RE-CHECK AFTER BILL!
64 380 PRE-BILL READ EDIT 389 PB MTR PICK UP READ
65 480 CUST SERVICE READINGS 413 CS REREAD BILLING REQ
66 480 CUST SERVICE READINGS 414 CA REREAD CUST REQUEST
67 490 CUST SERVICE MISC 388 CC WATER RESTRICTION CD
68 490 CUST SERVICE MISC 4110 CITED BY MARCHALLS DEPT
69 490 CUST SERVICE MISC 4111 MARCHALLS CITED OFF
. 70 500 SPECIAL TESTS j 600 MA REQCTIVEATE ACCOUNT
71 530 QUALITY CONTROL 1000 ADD/CHG POLLUTION FILE
72 660 METER TESTING ORDERS 670 MTR TEST FIELD=<2"
73 660 METER TESTING ORDERS 676 MTR TEST FIELD=>3"
• As many as twenty(20)Cityworks Work Order templates will be configured;approximately one(1)for each
Service Order group.
• In general, each Cityworks Work Order template will require only the following 3 integration touch points:
• Upon creation in enQuesta or Cityworks, create a corresponding record in the other system. Each
Cityworks Work Order template will always be initiated in the same system.
Page 5 .411=1111
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
• Upon completion of the Cityworks Work Order,a standard set of information will be sent to enQuesta.
All work completion integrations will begin in Cityworks and end in enQuesta.
• Cancellation of the work activity can be triggered from either system for any Work Order template.
• All Cityworks Work Orders will be assigned to Service Location records in the GIS.
• Any relationship between Service Location records and Meters or ERTs will be managed using the
Cityworks Equipment Change Out tool.GIS record relationships will not be managed via the integration.
• Only Meters and ERTs will be assets in the GIS. Registers or other components of the service connection
will not be managed as an asset.
• The City will ensure that enterprise GIS structure and data for those asset classes that are involved in this
project are available before Woolpert can begin configuration of Cityworks AMS software and
development of the integration. QA/QC of the GIS data to be consumed by the Cityworks AMS software
will be the City's responsibility.
Page 6 AWE.
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Technical Approach
The Woolpert approach will consist of the following phases:
Phase PM: Project Management Support Phase
Phase 1: Integration Planning Technical Phase
Phase 2: System Design and Configuration Technical Phase
Phase 3: Advanced Configuration and Functionality Technical Phase
Phase 4: System Deployment Technical Phase
Project Management will occur throughout the project.
The Integration Planning phase consists of a single effort with the deliverable being a Software Requirements
Specification defining the integration to the level that it can be coded.
The System Design and Configuration phase consists of a set of efforts to define and make the Cityworks configuration
tasks that are required within the meter shop. Many will support the integration with enQuesta, but some Cityworks
configurations may not be integration-related.
The Advanced Configuration and Functionality phase consists of a single effort to develop and test the integrations to
the point where they're ready to deploy to the live Production Cityworks environment.
The System Deployment phase consists of a set of efforts to test the configured Cityworks solution,train users on
system use, deploy the Cityworks configuration and integration components to the live Production environment,and
support the system throughout the critical period immediately after go-live.
Page 7 ��
•
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Quality Management Process
Aligning expectations between the Woolpert and City teams is critical to producing results that satisfy the City.As each
task is planned and executed,the Woolpert and City project managers will discuss the scoped deliverables.The
Woolpert team will describe the deliverables that they intend to produce(agendas,documents,software configurations,
software code, etc.).Where possible,the Woolpert team will provide samples created on similar projects to illustrate
the deliverable. No task should begin until both Woolpert and the City expectations of the deliverables are aligned.
Each type of deliverable on a project serves a purpose.And the quality review process exists to ensure that the purpose
is met. In general,the deliverables that are intended for a larger audience or are expected to be used for a longer time
and possibly"survive"the project (be used beyond software go-live)will undergo a more intense quality review. Other
deliverables are simply a stepping stone to move the project forward. These are considered "disposable"deliverables.
The following examples illustrate how different deliverables serve different purposes.
• Disposable Example: Meeting Agenda will ensure that a meeting is planned according to expectations
(topics and durations),that the right attendees are invited, and that the time and place for the meeting
are appropriate.After the meeting,the agenda serves no further purpose.Agendas will be lightly peer-
reviewed by an appropriate team member to ensure that its content and message is appropriate.The
review will not place emphasis on writing style,grammar and spelling.
• Surviving Example:AM Program Foundational Document will be held to a high-quality standard.The
DRAFT deliverable will be reviewed for content, message,and writing style.The FINAL version will be
reviewed for content, message,writing style,grammar and spelling.
Deliverables will be reviewed for the following items,as appropriate for the deliverable:
1. Content: ensure that the deliverable contains the correct information and that the information is accurate
2. Messaging:ensure that the voice and tone of the writing conveys the appropriate message;ensure that the
message is clear and easily understood by the intended audience
3. Writing Style:ensure that the writing is easily read and presents the content in a logical manner;writing is
professional and uses minimal slang and jargon
4. Grammar:ensure that writing is free of grammatical errors that could affect the meaning of the statements
5. Spelling and Typos:ensure that the deliverable is free from spelling and typographical errors
The following table lists the typical types of deliverables that will be produced on this project and the extent and focus
of Woolpert's quality reviews.
Deliverable Extent of Review Areas of Focus
Meeting/Workshop Agenda Low Content
On-site Prep Sheets Low Content
Meeting/Workshop Medium Content, Messaging
Presentation
Stakeholder Presentation(for Medium Content, Messaging
audiences outside of the
project team)
Page 8 AO.
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Deliverable Extent of Review Areas of Focus
Stakeholder Documents(for DRAFT Version: Medium Content, Messaging
audiences outside of the FINAL Version: High Content, Messaging, Grammar and
project team) Spelling
Industry Presentations Medium Content, Messaging
Industry Documents(trade DRAFT Version: Medium Content, Messaging
journal articles) FINAL Version: High Content, Messaging,Grammar and
Spelling
AM Foundational Document DRAFT Version: Medium Content, Messaging
FINAL Version: High Content, Messaging,Grammar and
Spelling
System Configuration High Content
Integration Components High Content
Reports High Content
In general,Woolpert employs five types of quality control methods.The appropriate quality control activities are
executed prior to delivering to the City the DRAFT and FINAL versions of a deliverable.
• Subject Matter Expert(SME)Peer Review—A Woolpert SME that is not involved in the project will review the
deliverable prior to delivery to the City. External SMEs will review documents that do not require intimate
knowledge of the City's project.
• Project Team Member Peer Review—Many Woolpert deliverables will be produced by a two-person team after a
great deal of interaction with City team members.These deliverables require that the reviewer have detailed
working knowledge of the City's project. Deliverables that require such knowledge will be created by one member
of the two-person Woolpert team and reviewed by the other. In some instances,the Woolpert project manager
will also review the documents.Along with providing feedback on their quality,the project manager will also
perform periodic reviews so that they can stay abreast of decisions made by others, particularly in the areas of
system configuration,systems integrations and organizational change management.
• Technical Writing Review—Woolpert employs several technical writers who routinely review documents that
require the highest level of polish. Deliverables reviewed by these individuals are typically externally facing
documents that are designed to survive the project.
• Internal Demos to Peers—The Woolpert team stages an internal demonstration of deliverables such as system
configuration and integration code(non-document deliverables)to one or more Woolpert peers who are not
involved in the project as though they were providing the demonstration to the City team.The peer(s) prepares
for the demonstration by reviewing the project documentation (configuration and/or integrations documents).
They then sit through the demonstration and ask specific configuration and process questions of the presenters.
Along with ensuring that the look and feel of the deliverables are up to Woolpert standards,any gaps in the
configuration or documentation are addressed prior to delivery.
• Client Reviews—Woolpert employs an iterative approach to configuration.As a result,this approach reduces
defects and mitigates configuration issues because we're getting valuable feedback from the City throughout the
project.
Page 9 � I��
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Any time Woolpert observes or is otherwise made aware of a project deliverable or staff performance deficiency,the
Woolpert project manager will immediately undertake the efforts required to resolve the identified issue(s).This can
include executing a more rigorous quality control process, re-visiting/clarifying assumptions,or removing non-
performing project team members. Each quality issue often has its own set of unique circumstances that need to be
addressed.Woolpert's team dedicated to this Project takes quality and client satisfaction issues very seriously. Processes
are in place internally to immediately engage all necessary parties and employ all appropriate strategies to resolve all
quality issues that arise on this project.
Page 10 ��
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Phase 1 - Project Management
Woolpert's Project Management approach provides
the resources and tools needed to successfully
manage the project through all phases/processes, ;
including:
• Initiation: Project authorizations and
expectations. r►
• Planning:Project definitions,objectives, �♦
deliverables,analysis of alternatives.
• Execution:Coordination of resources,quality
management, product and service delivery.
• Monitoring and Controlling: Monitoring and Figure 1-Project Life-Cycle Process Groups
measuring to identify variances and imitate
corrective actions.
• Close-Out:Acceptance of project deliverables and results.
To fulfill each of these objectives,Woolpert will employ the various project management tools described in the following
sections.
Project Administration
Woolpert will provide the following general project management services:
• Develop, in cooperation with the Cli-
wOOL
ent's project manager, a project plan
and schedule; "U°C" *" 1-°i~
• Proactively manage and update pro- "" «.°«•u. ,
ject plan and schedule, as required, , ,
throughout the duration of the pro-
ject.
TM.,
Project plan and schedule modifi- , ,
odAwl
cations will be facilitated upon com- N ^ ° �•
mon agreement between the Client
and Woolpert in accordance with the
issue control process detailed in the
project plan;
Figure 2- Woolpert's Project Collaboration Web Site
• Coordinate project events with the Cli-
ent's project manager and Woolpert team members;
• Author, edit, review, and distribute project documentation and technical reports as required;
• Facilitate in-process review meetings with the Client's project manager, committees, management, and
end-users as scheduled,and appropriate,throughout the duration of the project;
• Perform miscellaneous project administration (e.g. arrange travel, internal project updates);and
• Anticipate problem areas and propose and facilitate solutions
• Develop, in cooperation with the City's Project Manager,a project plan and schedule.
Deliverables
• Draft and final project plan
I��
•
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
• Monthly project status reports
• On-going project management, including resource allocation, invoicing and general consulting
• Password protected project collaboration environment and issue log management
Assumptions
• The activities discussed in this section will begin once a Written Notice-to-Proceed is received from the Client
Client Responsibilities
• Assemble a team of domain and technical experts and have representation of all work groups within the division
to be involved throughout all phases of the project
• Provide a point of contact for all project management issues and questions
• Review, comment and accept draft project work plan within five days of document delivery
• Schedule appropriate internal staff and provide facilities for on-site meetings and off-site conference calls
• Review and accept project status reports, or otherwise provide comments on same within a reasonable time
frame
Project Schedule Coordination
Project schedule coordination and
, w:_. N»`,fN.f4{'{n.Y iW119i.GN;N ,d MM'iW Yyin N. N W b,M„'N 0.A -"Grw.ti
management will be performed using °"
Microsoft Project software. Project "' =emon*wag.mannl. aw.M °'•""'"'•"
schedules and tasks will be monitored and ,,,
"
adjusted as needed,depending upon the y � � M
.•
City's priorities and ability to make its staff 4$r• """ ^
and facilities available at the appropriateCAW ._ '"' ,.., ..1.2...1.0.1..004
times throughout the project.An updated ""��
project schedule delineating resources, TAM;;1,� _ •
00
scheduled tasks, and completed tasks will be $) "" "'"
maintained and available to all Woolpert ,"% "'ft 'WON^
and City project participants. w. ,•^
Figure 3-Microsoft Project Gantt Chart
Deliverables
• Woolpert to maintain a project schedule in Microsoft Project and to update the project schedule with
significant changes and percent completes on a regular basis.
Assumptions
• None.
City Responsibilities
• City to participate in project schedule reviews on a regular basis.
Project Manager Status Meetings
Woolpert will facilitate regular Project Manager Status Meetings with the City Project Manager.The Woolpert Project
Manager and other Woolpert project team members,as appropriate,will participate in regularly scheduled project
status meetings with the City Project Manager and designees,as appropriate,for the purpose of reviewing project issues
including: 1) activities,action items,and deliverables completed to date;2) activities, action items,and deliverables in
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
process or scheduled;3) upcoming activities, action items,and deliverables;and 4)technical or contractual issues that
require corrective action.Woolpert meeting participants will include Woolpert's Project Manager and ad hoc team
members,as required. City meeting participants will be as determined by the City Project Manager,or as requested by
the Woolpert Project Manager.
When feasible, Project Manager Status Meetings will be held on-site at City facilities in conjunction with other scheduled
on-site tasks. Otherwise, Project Manager Status Meetings will be facilitated remotely using teleconference and web
meeting tools.
Deliverables
• Woolpert to facilitate weekly Project Manager meetings.
• Woolpert to author Meeting Minutes for each Project Manager meeting and to upload the minutes to
project website.
Assumptions
• None.
City Responsibilities
• City to schedule appropriate internal staff and provide facilities for on-site meetings and off-site conference
calls.
• City to review and accept project status reports,or otherwise provide comments within a reasonable time
frame.
• City to schedule meeting space and supporting technology peripherals suitable for on-site meetings.
• City to coordinate and schedule meeting attendees.
Internal Coordination Meetings
Internal Woolpert-resource coordination meetings will be held on a regular basis to ensure continuous communication
about tasks in process,scheduled tasks, and any issues impacting a successful implementation.The Woolpert Project
Manager will utilize these meetings to gather information from project team members required to manage on-going
resource loading.
Deliverables
• Regularly scheduled internal coordination meetings attended by Woolpert team members.
Assumptions
• See previous assumptions.
City Responsibilities
• None.
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Change Control
This section defines how changes to the original objectives and/or —
r_._....
deliverables defined in this Statement of Work will be handled.
Both Woolpert and the City recognize that change is a normal part
of the project life cycle.Woolpert believes that managing change
WOOL P E PT Change Control Notice-04
to project scope,cost,and schedule is critical to a project's •m""'"'"P`Aleettereeet epees.
Pepteeeentetten
success.We employ a comprehensive approach to change control. i T¢ M_Asset warm r,PE•Project Manager
} A®: Edward SS PE•Project
Woolpert's established change control process is documented as , 1014;Revise rt„q„May
Appr,,,,,a,P2,2014
x
follows. ) Sdrject: UVYle mIW Matte 04•OrproAaAM6CaiCgWYbnfor UXSUse
This Contralto:dr.
Any project team member(City or Woolpert) may initiate a change Crop
""'""°`°"od"the
"'""'°°°`'a"'"'Sto°'°'Se
request whenever there is a perceived need for a change that will ( °proddid for=Mt ;impa ,al
affect the desired or anticipated outcome of the work or any "M"Mel"room
• Mobs MI
"°�`
• ClMmmaso
element of the project.The project team member will use a •
Change Control Notice (CCN)form as appropriate for the change: T,;e�lare•,▪ nampol�Mw amirP m, effect 31=r11:01.54�,,,,
II IMJ.Te MIMI PM.Tans Q6TMEroMad /IMlEf
617EMLL).TI�aiPlndP I�PTdsIP��e�PwiM fva Mudmnelrli
• Agreement to a change and execution of the CCN signifies
Tb ,d..•ia
agreement to a change in overall costs,functionality,time c.:
dete,eyes
tr .wa a+.
a..a '.r.reier.�rra.. �roe.m.'•
scales,schedule or other identified project impact. :,<d�. 6. be fully in --M—
.AMad p/e.aaP rrwChi yuw+MP MI;+M Ptr w.�PE+trl
meal...Ad prel a mo Mrgwra.oetlm wNi•b rid r tr apr
meal Min Curer Malmo.
• Changes will be identified and communicated by/to the eMar-as--°�- �w .r•�.G-M�.�.-.r
ab ii Ciy.vtr NO•.esf Pu.es ♦osteo!PPevdw drMaParA4 w
respective Project Managers by any of the prescribed i.pr..v.l ea MAOIS...:r.°...n Molar an(Maw Sr ae E.E
' h-pP�ig.r ra.dE ,
vim OMS b tr Prrenee ePr.AM.ee a.epm cc►Ip FAYS"wyle�ird=
Men
communication channels. Change requests may be loos 1 mi"'r"
introduced via verbal conversation or other form of
IMO mar. MI MAW RN.
MR
communication but must be supported by the appropriate """""`"�
CCN document.
• All CCN's will be signed by both the City and Woolpert Figure 4-Sample Change Control Notice
Project Managers to indicate acceptance of the changes.
• All project participants should understand that time is of the essence when initiating, reviewing,
negotiating,and approving requested changes,as any delays to work in progress caused by a CCN may
impact the overall project schedule and budget.
All change requests should be managed from their initiation through to their completion (acceptance or rejection)
within five (5) business days from the start of the process. If the City and Woolpert Project Managers cannot reach
common agreement on the request change within this time frame,the issue will be elevated to the next level of
management(both City and Woolpert)for resolution. During the resolution process, all downstream project tasks
potentially impacted by the requested change will be placed on hold until such time that resolution is achieved.
Page 14 /AVM
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
The following workflow diagram graphically depicts the above detailed process:
Project Team member Requested change is No Woolpert PM documents
(Woolpert or Client( introduced by Requestor Proceed request,discussion points
and discussed among PMs .. with and final den sum via
identifies a needed change
to the Scope of Services via verbal or written Change' Project Memorandum
communication methods
1Yes
7
Initiating PM!Client or Initiating PM
Woofpertl prepares and CCN Yes updates CCN as
submits CCN form(Scope, CCN reviewed by PMs and
other ie uir ed project Updates required and
Fee Schedule,Risk q p ',,..i Reaalred resubmits to
Assessment! team members ,
•...,,y the CCN
review process
I No
Wpplpert PM
update;_cdeo Updated Project
of erg{a-s and documents signed by/
distributed to appropriate
Wooipert implements
ti u•ated
a jea team members Chaeges
rrclur•c.
Figure 5-Change Control Process
Each Change Control Notice (CCN)will clearly document the following:
• Date
• Change Control Number
• CCN Initiated By
• Original Scope of Services (language from the original scope that is being considered for change)
• Proposed Change (narrative of the proposed change(s) being sought)
• Schedule Impact(details about the proposed change(s) impact to the overall project schedule
• Fee Impact(details on the proposed change(s) impact to the project budget)
• Risk Assessment(narrative discussion about the risks the proposed change(s)will introduce to the project
and the ways in which said risk will be mitigated)
• Acceptance Signatures (Woolpert and City Project Managers)
Page 15 e2111
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Phase 1 - Integration Planning
The only task in this phase is to plan the integration such that a complete
Software Requirements Specification(SRS)document can be created. The Integration Planning Deliverables
SRS defines the integration in its entirety. • Integration Software Requirement
Specification Document
The integration will be developed using a middleware called NService Bus
(NSB). (NSB)is a tool that Woolpert licenses for development purposes but
the City will use for free once the integration is deployed. NSB is a framework that allows the integration to reprocess errors(in the
event of a temporary issue)such that they can be re-sent a set number of times before they are trapped and reported to the inte-
gration administrator as an error. The integration administrator will use the free NSB portal to re-send the integration message once
the cause of failure has been corrected.
Critical Assumptions: The only business system involved in this integration effort are Cityworks,Esri and enQuesta. Woolpert will
develop the integration components that extract data from or insert data into either Cityworks or the Esri geodatabase and will de-
velop all code related to processing data through the NSB middleware. Woolpert will not develop any integration components that
extract data from or insert data into any system other than these two.The City will be required to ensure the development,either
by themselves or by a third-party,of all integration components that extract data from or insert data into enQuesta or any system/
database that is not Cityworks or the Esri geodatabase.All Woolpert-assigned integration component development tasks should be
assumed to include City-assigned integration component development tasks related to enQuesta.
Task 1 .1 : Software Requirements Specification (SRS) Development
Woolpert will conduct one remote Integration Pre-Planning Discovery meeting with Client project manager and key IT and Subject
Matter Expert staff. Participants will discuss Client IT architecture and environments;any relevant Client policies and standards re-
garding deployment of software into those environments;roles and responsibilities;and testing and deployment plans.Woolpert
will deliver the meeting minutes documenting our understanding of these items following the meeting.Should Woolpert's under-
standing be incorrect,Client team should immediately contact the Woolpert project manager and a follow up discussion will be
scheduled to gain clarity.
Woolpert will conduct an on-site requirements-gathering meeting with key stakeholders from Client.Stakeholders will include a
person designated as the lead Integration Administrator for Client; IT staff who will be responsible for administering the integra-
tions;Subject Matter Experts(SMEs)for each system,and/or staff that are the primary point of contact with the vendor of the sys-
tem;GIS staff(if the integration involves GIS assets);and end users of each system. During these meetings,Woolpert will lead stake-
holders through discussions to identify what data is to be sent;whether the integration will be one-way or bi-directional;how fre-
quently data will be sent;and what user workflows are involved. During or before these meetings,Client will provide Woolpert with
necessary technical specifications to work with each 3rd party software interface(such as flat file format definitions;web service
definitions;interface database table schema;etc.)as well as representative sample data.
The result is a detailed,draft Software Requirements Specification(SRS)that Woolpert will provide to Client,which will include inte-
gration requirements,data mappings,environment specifications,and assumptions.Woolpert will facilitate a remote review meet-
ing with the stakeholders to discuss the comments and feedback from Client regarding their internal review of the SRS.Woolpert
will finalize the SRS and submit a final version to Client's integration team.
During requirements meetings,the requirements and technical specifications defined in this scope(below)will be refined and,inevi-
tably,changed.It is expected that the changes will not represent a significant difference in the total level of effort required;however
if they do,Woolpert will discuss priorities and options with the client to determine what can be performed within the existing scope,
and determining options for addressing anything that exceeds the original scope.
Deliverables
• Remote meeting of up to four(4) hours to discuss the architecture and environments;any relevant Client
policies and standards regarding deployment of software into those environments; roles and
responsibilities;and testing and deployment plans.
• Up to two(2) days of onsite workshops to define the integrations to the point where the DRAFT SRS can be
created.
Page 16 ARSE
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
• DRAFT version of the SRS document;sections to include:
• Overview
• Key relationships between records within and across systems
• Data Work Flows and Assumptions
• Integration Requirements
• Data Mappings
• Configuration Requirements
• Formal remote review of the DRAFT SRS with City team for up to four(4) hours.
• FINAL version of the SRS document.
Assumptions
• Woolpert will develop a DRAFT SRS in collaboration with the City so that there are few errors or omissions
and the City team is delivered a document with the information that they are expecting.Therefore, a single
review of,and update to,the DRAFT SRS will result in the FINAL version that is accepted by the City team.
City Responsibilities
• Many sections within the SRS document will require information about the enQuesta system as well as the
Cityworks/Esri solutions with which it will integrate.The City is to ensure that these sections are written
accurately and delivered to Woolpert for inclusion prior to delivery of the DRAFT and FINAL versions of the
SRS document.
• Review the DRAFT version of the SRS and be prepared to provide all feedback at the formal review meeting.
• Accept the FINAL version of the SRS after all items identified in the formal review meeting have been
addressed.
•
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Phase 2 -System Design and Configuration
Though this project is largely an integration effort,the Meter Shop may require some workflows
d that are not integrated with the enQuesta solution. During this phase, Woolpert will lead discover,
0 0 0 document findings, and build the identified configurations to support both the enQuesta-
integrated and non-integrated Cityworks configurations required by the Meter Shop staff.
Woolpert will provide a short demonstration of the
_ ! Cityworks functionality to the Meter Shop core System Design and Configuration
1 implementation team members. Following that Deliverables
introductory session,Woolpert will facilitate a single . Configuration Document
round of Configuration effort to include discussions
about the Service Request/Work Order/Inspection • Configured Cityworks Solution
processes and the material management/
storeroom processes.
Critical Assumptions: The Utilities Department has been successfully using Cityworks to process
service requests,work orders and inspections for several years. They have strong analyst/
technical/GIS support personnel who will facilitate the collection of configuration information
beyond the onsite workshop time, if necessary,and provide that information to the Woolpert
team in a format consistent with information they've provided to Woolpert on past implementation projects.
Task 2.1 : Develop Configuration Document
Woolpert will compile the asset management program data gathered and docu-
mented through the multiple on-site workshops and other related project meet Table of Contents
ings completed project-to-date(pre-planning discovery)and distill this infor-
mation into a series of organized configuration documents.This configuration Document Purpose and Structure 5
documentation,consisting of standard AM system elements,as well as the cus- Overview 5
SeMce Requests,Work riders,and Inspections 5
tomized details required to support the Client's specific asset management pro- Standard Service Request 5
gram,will be used to guide the configuration of the AM system such that it is lo- s�Na Accounts 6
calized to the Client's specific work order and asset maintenance management re- P''""r'g 7
Work Order 7
quirements. Tasks 8
Printing 8
Inspection 9
Deliverables Printing 9
Global Technical Configuration 10
Domain and Employee Setup 10
• Woolpert team members will develop a set of configuration documents as Domain Background 10
more fully detailed above.
Domain Grow around 11
Employees Background 12
• Woolpert will facilitate a remote review meeting up to two(2)hours in dura- GIS and Asset Setup 13
Geocoding 13
tion with the Client's technical team. ArcGISServer Confguration 14
Material Setup 16
Assumptions material list 16
material Mrarchy 16
Equipment Setup 16
• All above listed tasks will be performed remotely. equipment lm 16
equipment heirarchy 17
Client Responsibilities Contractors Setup 17
Projects Setup 18
• Review the prepared Draft Configuration documentation. SiteS Site Security Setup Setup 19
• Participate in the remote review meeting. Auditing 19
Email 19
Windows Authentification 20
User Interface Design 21
Storeroom 21
Reports 22
Figure 6:Sample AM System Configuration Documentation
Table of Contents
I��
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Task 2.2: Provide Asset Management System Configuration Training
Woolpert will facilitate an on-site configuration training course for the purpose of providing the Client's project team members with
the AM software knowledge needed to support the system design and implementation decisions.Configuration Training will be
comprised of a two-day curriculum designed to cover all relative aspects of the AM system configuration.Completion of the configu-
ration training will ensure the Client's project participants(those with implementation responsibilities)are provided with enough
exposure to,and understanding of,the AM software work order and asset management functionality such that they are able to
make smart and informed configuration decisions as they relate to the overall implementation objectives.The intent of the Configu-
ration Training is not to provide the skills needed to maintain the daily operations of the system.This End-User Training is provided
at a later date.
Configuration Training will be facilitated in a classroom environment(computer lab or training room)on-site at the Client's facilities.
Deliverables
• Woolpert will develop a Configuration Training agenda and provide same to the Client project manager.
• Woolpert will provide a single four(4)hour session for Configuration Training.
Assumptions
• Training will be facilitated utilizing the existing Cityworks TEST environment.
• Woolpert will have the necessary access to the AM software environment installed on-premises to perform training.
Client Responsibilities
• Client project manager to review and accept agenda for training.
• Client project manager to schedule and accommodate the appropriate Client project team members such that they are availa-
ble,without undue interruption,for the required number of days.
• Client project manager will ensure site readiness and staff participation for the training.
• Client project manager will provide a conference room or training room with a projector. During Configuration Training,individ-
ual computers are not needed for the participants.The software functionality will be demonstrated from the instructor's com-
puter.
• Client project manager will secure an appropriate training facility suitable for participants.
Task 2.3: Facilitate Core AM Software Configuration
Woolpert will facilitate the Core AM Software Configuration in a single on-site configuration workshop.The workshop will address:
• Work Orders.Templates for each of the type of maintenance activities that will be performed on each asset in the system.
• Tasks. Individual work items associated with a work order. For example,a repair sewer main work order might have tasks for
establishing traffic control, utility locate,excavate,etc.
• Materials Hierarchy.Organization and rules for items that are used to repair assets. Examples of materials are things such as
pipes and meters.
• Equipment Hierarchy.Organization and rules for items that are utilized to complete a work order but are not consumed. Exam-
ples are items such as backhoes,vehicles,vacuum trucks,etc.
• Service Requests.Templates for requests for service. Many times,maintenance activities are initiated starting with a service
request whose purpose is to determine if work is necessary or not.
• Inspections.Templated for inspections where detailed results are recorded for each observation.
• Reporting.Current or future expected reports will be discussed and designed.
Woolpert will update the System Configuration Document upon completion of the configuration workshops.At the end of the work-
shops,there will be a set of action items for the Client team members,such as compiling a list of employees,work crews,and con-
tractors,as well as hard copies of work orders, reports,inspection forms,and other relevant data sets.Woolpert will prepare a de-
tailed list of action items and submit them to the Client project manager.
Page 19 ,=1111
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Deliverables
• Woolpert will facilitate one(1)on-site configuration workshops for up to eight(8)hours.
• Woolpert will update the configuration documentation based on the outcome of the workshop and the information provided as
a result of the workshop requests.
• Woolpert will perform system configuration in the Client's on-premises development environment via remote access.
• Woolpert will facilitate a single remote in-process configuration review meetings for up to two(2)hours in duration,with the
Client's technical team.
Assumptions
• All workshop preparation activities will be performed remotely.
• Actual workshops will be administered on-site at Client facilities.
• Client staff participating in the configuration workshops will do so uninterrupted.
• Most of the configuration requirements will be generated from the integration discussion,which is why only one configuration
workshop is scheduled.
• Client Cityworks administrator can provide configuration guidance to the client team after the workshop,if necessary,and pro-
vide any new information to Woolpert for inclusion in the system configuration.
• There will be approximately 20 Cityworks Work Order templates that integrate with enQuesta. No Cityworks Work Order tem-
plates will integrate with any other systems.
• No Cityworks Service Request or Inspection templates will integrate with enQuesta or any other system.
Client Responsibilities
• Secure an appropriate workshop facility.
• Coordinate and schedule workshop participants.
• Workshop participants shall actively participate in workshop activities.
• Populate the updated GIS database with the missing asset inventory.
• Client Cityworks administrator will follow up with client core implementation team regarding any configuration items not final-
ized during the workshop.
Task 2.4: Facilitate Storeroom Configuration
Materials management and inventory control procedures play a significant role in properly deployed asset maintenance manage-
ment solutions.As materials are added to work orders,they need to be depleted from the stock and the cost of the materials added
to the work orders;as materials are depleted from stock,they need to be requisitioned from the various vendors.This task is fo-
cused on configuring the materials management module of the AM software to achieve these objectives.The effort required to inte-
grate the AM software with the Client's purchasing and inventory system of record is addressed in the Systems Integration tasks.
Deliverables
• Woolpert will facilitate one on-site configuration workshops immediately following the AMS configuration workshop for up to
four(4)hours.
• Woolpert will update the configuration documentation based on the outcome of the first round of configuration workshops.
• Woolpert will perform system configuration in the Client's on-premises development environment via remote access.
• Woolpert will facilitate in-process configuration review meetings,each up to two(2)hours in duration,with the Client's tech-
nical team.
• Woolpert will facilitate a remote review meeting up to two(2)hours in duration with the Client's technical team.
Assumptions
• All workshop preparation activities will be performed remotely.
• Actual workshops will be administered on-site at Client facilities.
• Client staff participating in the configuration workshops will do so uninterrupted.
• Client Cityworks administrator can provide configuration guidance to the client team after the workshop,if necessary,and pro-
vide any new information to Woolpert for inclusion in the system configuration.
Page 20 AIMMI
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
• All components at a Servicer Location will be tracked as materials. Two of those materials(Meters and ERTs)will also be
tracked as assets in the GIS.
Client Responsibilities
• Secure an appropriate workshop facility.
• Coordinate and schedule workshop participants.
• Workshop participants shall actively participate in workshop activities.
Task 2.5: Phase 2 Quality Control
41111101 Woolpert will apply the Quality Management Process stated earlier in this scope document to Phase 2
tasks, activities and deliverables.
DUALITY MANA3FUE NI
Task 2.6: Phase 2 Acceptance and Close
This is the Phase exit document that the City Project Manager signs indicating Woolpert has delivered the Configuration
phase in accordance with the Scope of Work and Project Plan.
Page 21 AIME
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Phase 3 - Advanced Configuration and Functionality
0 The sole effort in this phase is to develop and test the Citywors-enQuesta integration components
to the point where they are accepted by the City team and ready to be moved into the live
0 0 Production Cityworks environment..
Legacy data migrations and custom report development efforts are not included in this scope of
services.
To some degree,data migration may be accomplished via the integration, if synchronizing the
meter and ERT records between enQuesta and the GIS tables is deemed necessary. Else,the City
team will determine the best method for ensuring that
the initial data sets are loaded in the proper locations Advanced Configuration and Func-
prior to going live with the Meter Shop's use of Cityworks. tionality Deliverables
• Cityworks-enQuesta System
I rui Custom reports have been excluded from this scope of Integration
work be the City has staffed the Utilities Department with
an experienced Cityworks Administrator who can design
and develop advanced reports without assistance.Cityworks queries and inboxes will be identified
during the configuration workshops and developed with users during the end-user training tasks.
Task 3.1 : System Integrations
This task is to develop and test the integration components necessary to support the Cityworks-enQuesta integration.To
support the integration,asset data for the Meters and ERTs will be synchronized between enQuesta and the GIS.
Cityworks-enQuesta Integration
There will be many touch-points to the Cityworks-enQuesta integration. Each time the systems exchange information,
there are two end-points to develop,one for extracting data to be sent from the source system and one for inserting
data into the target system.Woolpert will use a middleware called NService Bus(NSB)to manage the hand-off between
the endpoints. NSB will provide error handling. Errors will be automatically re-processed a set number of times. If the
error reprocesses successfully,then the data transferred is considered a success and no further action is required. If the
error persists after the re-processing efforts,then the data transfer message is sent to a queue for manual intervention.
An integration administrator will need to investigate the error,correct the issue,and manually trigger the data transfer
to re-try.When the data successfully processes,the error is resolved. Managing errors using NSB will be documented in
an Integration Admin Guide.
GIS-enQuesta Integration
The enQuesta database will be the system of record for Meter and ERT records.This integration will be a one-way syn-
chronization between the records in enQuesta and the records in the GIS.There are several approaches to creating this
integration. Using the preferred approach, a regularly scheduled integration will retrieve newly added and updated me-
ter/ERT records from CIS and add or update them in GIS.The integration will use an ArcGIS Server feature service to
add and update features.
This assumes Enquesta or a 3rd party vendor will provide an interface (API or database table)which allows for the re-
trieval of added or updated records by timestamp.When an updated record is received,the integration will simply over-
write all supplied data fields with the new values; it will not attempt to compare new and old values to identify or con-
firm changes.
I��
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
If it is not possible to retrieve the information from Enquesta this way,we will discuss alternate approaches to retrieving
the data.
Integration Development
The integration specifications developed during the Integration Planning phase will serve as the blueprint for this
development task.Woolpert and the City will each have similar tasks in the development of the end-to-end integrations
between Cityworks and enQuesta. In this document,only the Woolpert tasks will be described in detail.The City will
need to determine which tasks need to be undertaken by their team.
Woolpert will create a development environment on Woolpert's network with a copy of City's Cityworks and, if
necessary, GIS solutions. Woolpert will develop mock interfaces to represent the enQuesta software according to the
technical specifications defined for the interface in the SRS.Woolpert will develop and test the system integration
components that extract data from,or insert data into, either the Cityworks or GIS databases in this environment.When
the integration components are functional,Woolpert will demonstrate that the successfully extract data from and insert
data into the Cityworks and GIS databases.The City will develop integration components that extract data from and
insert data into the enQuesta database.The City may develop their integration components in an environment that
includes working Cityworks and GIS applications. Is so,they will not need to develop mock integration technologies.
When the City's integration components are functional,they will provide a demonstration of the working components
to the Woolpert team.
After component testing is complete,Woolpert will schedule time with the City to deploy the integrations within City's
test environment. Woolpert will assist the City's Integration Administrator during a remote session(via WebEx)as s/he
installs and configures the integrations in City's test environment.This remote session will serve as hands-on training for
the City's Integration Administrator so that s/he has the knowledge needed to manage the integrations.
Following the installation onto the City's test environment,the Woolpert developer and the City's Integration
Administrator,with support from Subject Matter Experts for each system,will perform Endpoint Communication Testing
(ECT)—that is,they will kick off actions that will demonstrate that data can successfully get from system A to system B.
The intent of this is simply to make sure that the two systems are communicating as expected and that the testing
environment stable and ready for more thorough testing.At this point,thorough Integration Acceptance Testing(IAT)
will begin.
Woolpert will provide a draft Integration Administrator's guide.This document will include a system architecture
overview; installation instructions;Cityworks configuration requirements; information on administering, managing,and
configuring the integration;and logging information. Certain portions of this guide,those related to the enQuesta
integration components,will need to be developed by the City's team
Integration Development
Woolpert and the City Integration Administrator will use the SRS as the basis for creating Integration Acceptance Test
(IAT)Scripts,which incorporate necessary business processes as needed.Woolpert will conduct a remote workshop
meeting to discuss the approach to developing the IAT Scripts according to the City's policies and Woolpert
recommendations, and to produce a sample testing script.A City Integration Testing Team consisting of a Subject Matter
Expert for each system (Cityworks, Esri and enQuesta)and the Integration Administrator will participate in the
workshop, and then will produce the necessary IAT scripts. Woolpert will review these and provide feedback within five
(5) business days.
When the Endpoint Communication Testing is complete and the IAT scripts are ready,the Integration Testing Team will
work together to conduct the test,and record successes and failures.The team will log any issues found.Woolpert will
address the issues and provide updates to the Integration Administrator.After the IAT is complete and each integration
has been verified to meet each requirement,Woolpert will make any necessary updates to the Integration
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Administrator's Guide and deliver a final document.Should the Woolert-developed integration components require
modification,Woolpert will make those changes on the Woolpert environment and supply them to the City's Integration
Administrator.The City's Integration Administrator will re-install the components in the same manner that they were
initially installed without Woolpert assistance.
Upon acceptance of the integration components,Woolpert
enQuesta to GIS Integration:One-way
This will be a one-way integration going from enQuesta into ArcSDE.The integration will monitor for Meter and ERT
records created or retired in enQuesta.This integration will run nightly due the fact that it will be a resource-intensive
process.
Assumptions:
• The integration will have access to a version of the target tables(Meters and ERTs) in ArcSDE.Although the
version may be dropped and recreated,the name will not change.
• Only Meters and ERTs will be handled via this integration.
• The City will develop the integration component(s)that provide the Meter and ERT information out of
enQuesta.
enQuesta-Cityworks Work Integration:Two-way
This will be a two-way integration linking enQuesta Service Order(SO) records and Cityworks work order records.
Information is expected to be shared across the systems at several trigger points:
• New SO created in enQuesta
• Existing SO in cancelled in enQuesta
• Work order updated,closed,or cancelled in Cityworks
A list of work order types that will be handled by the integration be identified during the creation of the Software
Requirements Specification (SRS). No unique functionality will be handled across the work order types;all similar
integration triggers will pass the same information. Information to be passed between the system may include:
• Work type
• ID numbers (SO/WO)
• Description
• Category(preventive,corrective, predictive)
• Status
• Priority
• Location description
• Address
• Comments
• Personnel who initiated/assigned/performed work
• Asset information (e.g., meter or AMR identifier)
• Initiated date
• Projected Start date
• Projected finish date
• Actual start date
• Actual finish date
• Comments
• Instructions
• Account
Page 24 Adigna
City of Augusta,Georgia 1 Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Assumptions:
• The integration will have access to a version of the Meter and ERT tables.Although the version may be dropped
and recreated,the name will not change.
• Only Meters and ERTs will be handled via this integration.
• The City will develop the integration component(s)that provides the Service Order information from, and inserts
the Work Order information into,enQuesta.
Deliverables
• Woolpert to develop a Cityworks/GIS environment on Woolpert infrastructure.
• Woolpert to develop the integration component for each of the following ten (10)endpoints:
o Endpoint 1:Service Order(poll picks up from enQuesta)
o Endpoint 2: New Work Order(sends to Cityworks API)
o Endpoint 3:Closed Work Order(6 main types-install, remove, replace,test, read, other)
o Endpoint 4: Closed Service Order(received in enQuesta)
o Endpoint 5: New Work Order(created in Cityworks)
o Endpoint 6: New Service Order(sent from Cityworks)
o Endpoint 7:Service Order cancelled (from enQuesta)
o Endpoint 8:Cancel Work Order in Cityworks(from enQuesta)
o Endpoint 9: Work Order Cancelled in Cityworks (sent from Cityworks)
o Endpoint 10:Cancel SO in Enquesta (from Cityworks)
• Woolpert to develop no more than two(2) nightly synchronizations between enQuesta and the GIS to
update the Meter and ERT records in the GIS with the necessary changes.
• Woolpert to demonstrate working integration components for each of the ten (10)endpoints.
• Woolpert to observe and provide feedback on the City-developed integration endpoints.
• Woolpert to develop installers/scripts to load the integration components into different environment.
• Woolpert to assist the city in the initial installation of the Woolpert-developed integration components
in the City's Test environment and facilitate Endpoint Communication Testing
• Woolpert to facilitate remote call to discuss how to develop integration testing scripts.
• Woolpert to review and provide feedback on the City-developed integration testing scripts.
• Woolpert to facilitate integration testing, make the necessary changes to the Woolpert-developed
integration components,and provide them to the City Integration Administrator for re-installation.
Assumptions
• Woolpert will use NService Bus as the middleware/messaging/error handling solution.
• Woolpert will develop integration components that extract data from,or insert data into,the Cityworks
and Esri GIS software solutions.
• City Technical Team will be responsible for developing, or contracting with a third-party for the
development of,the integration components that extract data from,or insert data into,software
systems other that Cityworks and the Esri GIS.
• All 3rd party software solutions (those other than Cityworks and Esri) have documented interface
capabilities (flat file, interface tables,or web APIs)that support the necessary data exchange.
• City Integration Team,d business unit staff,and contracted 3rd party developers familiar with the 3rd
party systems will be available and will attend each workshop;where City relies on external contractors
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
as subject matter experts City will ensure that these external experts attend,are prepared for and
actively participate in the workshops.
• The SRS document is complete and signed-off on by the City prior to commencement of any
development activities.
City Responsibilities
• City to develop a suitable environment for developing their integration components.
• City to develop the integration component for the endpoints that pass data to,or accept data from,the
Woolpert-developed endpoints.
• City to develop the enQuesta extracts that provide the necessary information to the two(2) nightly
synchronizations between enQuesta and the GIS to update the Meter and ERT records in the GIS.
• City to demonstrate working integration components for each of the endpoints.
• City to observe and provide feedback on the Woolpert-developed integration endpoints.
• City to develop a method,as appropriate,to load the integration components into different
environments.
• City to install the integration components in different environments, as necessary,for testing activities
and go-live.
• City to attend remote call to discuss how to develop integration testing scripts.
• City to develop integration testing scripts.
• City to update integration testing scripts per feedback provided by Woolpert.
• City to participate in integration testing, make the necessary changes to the City-developed integration
components, and re-install modified integration components for re-testing.
Task 3.2: Legacy Data Migrations
No legacy data migration is included in this scope of work.The only records that may require migration are the Meter
and ERT records from enQuesta to the GIS. If this migration is required,then the expectation is that the City team will
perform the migration.
Task 3.3: Custom Reports and Metrics
No custom report or metric development is included in this scope of work.The Utilities department has been using
Cityworks AMS for over 4 years.Their Cityworks administrator is an experienced report developer and will create any
custom reports or metrics required by the Meter Shop.
WBS Task 3.4: Phase 3 Quality Control
Woolpert will apply the Quality Management Process stated earlier in this scope document to Phase 3
tasks, activities and deliverables.
QUALITY V.NAGEMFNI
WBS Task 3.5: Phase 3 Acceptance and Close
This is the Phase exit document that City signs indicating Woolpert has delivered the Advanced Functionality Phase in
accordance with the Scope of Work and Project Plan.
Page 26 AdIEZ111
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Phase 4: System Deployment
Once the Cityworks AMS solution has been configured,along with any critical
Key Core System Deployment(Phase 4) related applications(inventory management,mobile,custom integrations),
Deliverables there are still a number of critical tasks that must be completed before the
• User Acceptance and Testing(UAT) Plan solution is placed into a production environment.Woolpert's implementa-
tion team will lead the City's technical team through a series of related de-
• Tester Training ployment tasks that will ensure a fully tested and accepted solution as well
• UAT Support as a City team of fully trained system administrators and end users ready to
• End User Training put the system to use on a daily basis.
• Go-Live Support Both the City and Woolpert understand that this project is largely an integra-
tion effort which will drive configuration changes. But since the Meter Shop
is not currently using Cityworks,there may be some non-integrated work-
flows identified during the configuration workshops.These deployment efforts come after the integration components are accepted
by the City so these efforts will focus on testing the non-integrated configurations and work processes.
Woolpert will assist the City system administrators in developing a thorough Testing and Acceptance Plan,designed to step the con-
figured solution through all of the technical and functional requirements that the system was configured to support. Following ac-
ceptance of the test plan,Woolpert will facilitate a series of Tester Training classes for the City's selected testing team. Immediately
upon completion of this training,the City's testing team will execute the User Acceptance Testing program in accordance with the
plan.While it is the City's responsibility to assemble a testing team and manage the testing procedures in-house,Woolpert staff will
be made available to provide the scoped onsite and ad-hoc remote assistance.
Once the system testing has been completed,and all of the resultant configuration updates have been made,Woolpert will deliver
the required end-user training.This training will be scheduled and delivered"just in time",immediately prior to the Go-Live activities
to ensure system administrators and end users are prepared to adopt and embrace the new technology solutions right out of the
gate.
The final deployment task is for Woolpert to assist the City system administrators in migrating the solution from the Development/
Testing environment to a live Production environment and provide on-site Go-Live support for the first several days that the new
system is being placed into productive use.
Task 4.1 : Develop Non-Integrated Configuration User Acceptance Testing
Plans
The focus of system testing efforts is to thoroughly test the newly installed/configured AM System solution's non-integrated config-
urations and work processes and ensure all delivered functionality(application workflows,templates, reports,interfaces)are
properly functioning.At this point in the project,all integration-related configurations and work flows should be tested and ac-
cepted by the city.
Woolpert will take the lead on developing a Testing and Acceptance Plan.The Plan will derive its focus from the previously prepared
AM System Configuration documents. Functional metrics that the AM System configuration must successfully achieve prior to being
promoted to the City's production environment will be defined.Additionally,test scenarios designed to step City Testers through the
User Acceptance Testing(UAT)process will be developed as part of this plan. Final plan contents will be per common agreement
between the City testing team and Woolpert and will serve as the"script"for testing and approving the system configuration.The
test plan will address the AM System functionality specified and configured per the Project Plan.
Deliverables
• Woolpert will prepare and deliver the draft Testing and Acceptance Plan to the City project manager.
• Woolpert will facilitate a remote review meeting with the City's testing team.
• Woolpert will update the testing and Acceptance Plan per the results of the review meeting and re-submit to the City's PM
Page 27 AMAMI
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Assumptions
• The Testing and Acceptance Plan will be developed per common agreement between the City and Woolpert.
• The Testing and Acceptance Plan will derive from the system configuration documents and project plan.
City Responsibilities
• The City's project manager and members of the testing team must thoroughly review and understand the Testing and Ac-
ceptance Plan.
Task 4.2: Facilitate User Acceptance Testing
It will be the responsibility of the City to select a number of end-users who will provide testing of the newly configured Cityworks
solution. In order to effectively test the system in accordance with the UAT Plan,training will be provided to these end-users,and
these end users will perform the testing with Woolpert on-site support.Woolpert will train the City testing team on how to execute
the test plan and record the results.Woolpert will act as a proctor in a testing room to support the testers and correct configuration
issues during the tester training week.Beyond the tester training week,the City testing team is expected to complete all system
testing and record their results on the Test Plan documents.Woolpert will provide remote support for the testers and correct all
issues at the conclusion of the testing period.Woolpert will support the City's retesting activities remotely via WebEx.
Deliverables
• Woolpert will deliver the necessary training materials to the City's project manager. Preparation and delivery of training
materials shall be within two(2)business days prior to the scheduled start of on-site training activities.Tester training will
not exceed one(1)day.
• Immediately following tester training,Woolpert will provide onsite testing support for up to two(2)days. During this time,
Woolpert will immediately correct issues so the City team can immediately retest and accept the corrections.
• Woolpert will provide up to twenty-four(24)hours of remote support after the onsite testing activities for the following:
o Support City testers as they complete testing activities that could not be completed in the time allotted for onsite
testing.
o Correct and facilitate the retesting of issues that could not be corrected and retested in the time allotted for onsite
testing.
• Woolpert will update the AMS configuration with modifications from the acceptance testing process.
• Woolpert will update the configuration documentation to reflect changes as a result of the acceptance testing.
Assumptions
• The City understands that failure to provide the City testing team with the appropriate training documents will impact
Woolpert's ability to properly train these users in the time allotted for classroom training.
• The City understands that failure to properly prepare the training site and ensuring adequate available training resources
will result in the Woolpert—City training team being unable to provide the required training to the City testers.
• The City understands that failure to properly prepare for and participate in the training sessions will significantly impact the
City testing team's ability to effectively make use of the configured AM System application.
City Responsibilities
• Distribute training materials to the City testing team prior to the scheduled training sessions.
• Ensure training room is prepared in advance.
• The City's project manager and testing team must thoroughly review and understand the training syllabus developed by
Woolpert.
• Secure an appropriate training facility suitable for participants,
• Schedule and accommodate the appropriate City testing team members such that they are available,without undue inter-
ruption,for the required number of days.
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
Task 4.3: Provide End-User Training
It is important that end-user training be timed to occur immediately prior to beginning live use of the system in the Production envi-
ronment.Since there is only one department(Meter Shop)who will begin using Cityworks at this time and the number of new users
will be small,Woolpert will conduct all end user training classes.Also,since the Utilities Department already has an experienced
Cityworks Administrator,Woolpert will not conduct Admin training.
Completion of the training efforts will result in Meter Shop end-users being provided the system knowledge and capabilities neces-
sary to and use the configured Cityworks AMS and integrated applications in an effective manner such that the City's over-arching
business objectives can be met through use of the newly configured system.
The two (2)training classes that will be provided are for processes work activities (Service Requests, Work Orders and Inspections)
and storeroom/material management activities. Each will include training system navigation,generating queries,using the map and
other functions that may be a normal part of the trainee's job function.
Deliverables
• Standard Cityworks training materials
• Woolpert will facilitate the following training courses over a period of four(4)days:
o Work Management Class 1 of 2 12 hours
o Work Management Class 2 of 2 12 hours
o Storeroom Management 8 hours
• Class sizes will be limited to no more than ten(10)if a single instructor is conducting the class with no assistance;class sizes
can increase to up to twenty(20)if a properly trained resource,City or Woolpert,assists the lead instructor
Assumptions
• The City has an adequate training facility that can accommodate the resultant number of staff to be trained; each ac-
cessing the AM system on their own workstation
• Class sizes will be appropriately limited
City Responsibilities
• Secure an appropriate training facility
• Coordinate and schedule training participants
• Training participants shall actively participate in training activities
Task 4.4: Go-Live & Support
As part of the go-live preparation activities(cutover),Woolpert will migrate the configured and approved Cityworks AMS configura-
tions from the Development environment to the Production environment and support the City's Integration Administrator in loading
the Woolpert-developed integration components to the Production environment.The City will be responsible for making and neces-
sary changes to the GIS and for loading the enquesta-related integration components to the Production environment.
Immediately following cutover,Woolpert will provide Go-Live assistance to Meter Shop Cityworks users during the first few days of
system usage in the Production environment.Woolpert will assist the City's end-users and system administrators with a combination
of onsite configuration issues and application usage and remote integration support.
Deliverables
• Woolpert will provide up to thirty-two(32)hours of onsite Configuration(user)support and up to thirty-two(32)hours
of remote integration support.
Assumptions
• The City's project manager will provide project sign-off within an agreed upon timeframe following Go-Live.
Page 29 ANZIO
V N
City of Augusta,Georgia I Utilities Meter Shop Cityworks Implementation and Integration with enQuesta CIS
City Responsibilities
• The City's project manager,Cityworks administrators,and IT support staff should equally assist in administering the Go-Live
tasks to make sure it is clear to the End-Users that the City is internally capable of supporting the newly deployed Cityworks
AMS solution.The City system administrators and IT support staff will benefit from learning basic AM System troubleshoot-
ing routines during this time.
Task 4.5: Phase 4 Quality Control
Woolpert technical resources, not regularly involved with this implementation will perform independent quality review of the work
processes and deliverable products in accordance with the Woolpert Total Quality Plan.
Task 4.6: Phase 4 Acceptance and Close
This is the Phase 4 exit document that the City signs indicating Woolpert has delivered the Phase 4 services in accordance with the
Scope of Work.After the phase 4 has been approved by the City,Woolpert will provide a project close document for signature by
the City,signifying that all items listed within this scope of work have been completed.
Page 30
AUGUSTA-RICHMOND COUNTY, GEORGIA
PURCHASE ORDER ROOM 606,PURCHASING DEPARTMENT PURCHASE ORDER
CITY-COUNCIL MUNICIPAL BUILDING(11)
AUGUSTA,GEORGIA 30001-4149 Page 1 of 1 P230073
DATE DEPARTMENT VENDORPHONE N REQUISITIONIQUOTE NO.
10/21/13 043490 R232390
VENDORS E-VERIFY# FLFcHr s[OIL .r u IE,E r,AL;) 'E
21607 11815 �51 „rFL f,
SHIFPILL_
PfAFEF, ,-4/L+PAL
VENDOR
WOOLPERT ATTN:
116' INVERNESS DRIVE EAST BID NUMBER: 12-221
ENGLEWOOD, CO 80112
CONTRACTS:
BUYER: NANCY
SHIP TO: BILL TO:
AUGUSTA UTILITIES ADMIN AUGUSTA-RICHMOND COUNTY,GEORGIA
360 BAY writs= ROOM 106,ACCOUNTING DEPARTMENT
CITY-COUNCIL MUNICIPAL BUILDING(11)
SUITE 180 AUGUSTA,GEORGIA 30901-4143
AUGUSTA, GA 30901 ALL INVOICES AND CORRESPONDENCE MUST BE SENT TO
ABOVE ADDRESS REGARDLESS OF SHIPPING DESTINATION.
ITEL1 QUANTITY 1J iIl PRODUCTIC) DEUCRIPlIOT1 UNIT PRICE= I A`.IOUNT
0001 1 EACH PROVIDE AND IMPLEMENT 627,355.0' 627,355.00
CITYWORRS SERVER ANS SOFTWARE
APPROVED BY COMMISSION
10/1/13, ITEM 814
507-04-3490/54-24120
•
CONDITIONS-READ CAREFULLY
1.The pumhltser Is warm*by statue tom portent of Federal.thele.end Municipal
sales,excise end other Iwo.
2. Mapping charges prepaid by vendor.
3. Payment WO bit mads on c lete s ipmentsonla unless otherwise requeeted. NET TOTAL 627,355.00
A DELIVERY TICKET MUST ACCOMMNY 000011.
5.No back cams.We wit reorder if rabbis
B. Please mals daiivules between 9 A.M.and 4 P.M. APPROVED FOR ISSUE
7.All pooh Waived with In oniopbpnoe O to,ped and ons. al Wnda s
expense t detective or not In ewrgtanes OM our apedtediona.
B. Indoor delivery If necessary
t.Payment Net 90 or accerding to contract.
REQUISITIONER PURCHASING AOENT SIGNATURE