Browse
Search
2020-150-E IT - Tyler Technologies EnerGov contract amendment
OrangeCountyNC
>
Board of County Commissioners
>
Contracts and Agreements
>
General Contracts and Agreements
>
2020's
>
2020
>
2020-150-E IT - Tyler Technologies EnerGov contract amendment
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/9/2020 8:42:54 AM
Creation date
3/27/2020 9:16:49 AM
Metadata
Fields
Template:
Contract
Date
2/16/2020
Contract Starting Date
2/16/2020
Contract Document Type
Agreement - Services
Amount
-$8,091.79
Document Relationships
R 2020-150 IT - Tyler Technologies EnerGov contract amendment
(Attachment)
Path:
\Board of County Commissioners\Contracts and Agreements\Contract Routing Sheets\Routing Sheets\2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
97
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
DocuSign Envelope ID:8D6BF819-7F7F-492F-B590-6156F7327668 <br /> Stage 2 -Assess&Define <br /> This stage involves onsite and offsite comprehensive business process,change management,and systems assessment and <br /> analysis.The goal is to examine the customer's current business process("assess")and translate those findings into a <br /> defined and documented future state process("define")to best automate the unique customer processes. With guidance and <br /> mapping assistance from Tyler,as set forth in Stage 1,County will also analyze and prepare data sources to be converted <br /> based on the structure of the DCT-DB,which will be an ongoing/iterative process up through the final conversion pass. For <br /> the avoidance of doubt, scope for converted data sources set forth in the table in Stage 4A is limited 5 iterative passes from <br /> the DCT-DB to the EnerGov master database.A data source load/population to the DCT-DB does not count against those 5 <br /> iterations. <br /> Objectives: <br /> o Comprehensive review and analysis of customer's business processes to be automated <br /> o Translate business understanding into the"to-be"documented EnerGov configuration definition <br /> documentation,which will serve as the basis for system configuration <br /> o Refinement of project plan,including identification of project risks or additional infrastructure <br /> requirements <br /> o Perform gap analysis between EnerGov standard reports,key performance indicators,and existing <br /> document output requirements so as to confirm that sufficient report development services are in scope <br /> and to build a master list of the reports to be specified and developed in subsequent stages. <br /> o Conduct prototype sessions <br /> o Determine integration strategy,including definition of system integrations and scope confirmation. <br /> o Determine data migration strategy. <br /> o Address any additional scope requirements through a mutually agreeable change order. A sample <br /> Change Order request form is provided at SOW Attachment B,a sample Custom Programming request <br /> form is provided at SOW Attachment E.and a Custom Report request form is provided at SOW <br /> Attachment F. <br /> Definition: <br /> As discussed above,during this stage the parties analyze the customer's business processes. As part of this <br /> process,the parties identify the"Business Case Transactions,"also known as workflows,which are the defined <br /> configuration of an automated business process in which documents and/or other information is passed from one <br /> participant to another(or others)for action according to a set of shared procedural rules. Where several <br /> transactions rely on the same set of procedural rules,a single configuration will apply to the otherwise unique <br /> workflows. Where one transaction depends on the automation of one or more distinct procedural rule(s),a new <br /> configuration will be required for that transaction. The configuration consists of the following components,where <br /> uniqueness of these components constitutes a new and unique business case transaction: <br /> o The to-be configured business process workflow,including output actions <br /> o Automation logic <br /> o Fee assessment and configuration definition <br /> o Custom fields and forms definition. <br /> The final business case transaction documents finalized during Assess&Define stage will serve as the baseline <br /> "scope"for the EnerGov system configuration within the subsequent Configuration stage. <br /> Tasks: <br /> Assess&Define <br /> Tasks Tyler Customer <br /> Identify Business Transactions/Case Types(i.e.Permit Advise Own <br /> —Types,Plan Types,Inspection Types,etc.) <br /> Scope and document EnerGov configuration design Own Participate <br /> document per business transaction/process <br /> . tyler <br /> 34 <br />
The URL can be used to link to this page
Your browser does not support the video tag.