4.07 4.7
AGREEMENTS\General Code—To Supercede 2016 Contract to Connect EnerGov to Laserfiche—8-6-18
RESOLUTION AUTHORIZING REPLACEMENT/SUPERSEDING OF
STATEMENT OF WORK/AGREEMENT WITH GENERAL CODE
REGARDING CONNECTION OF ENERGOV AND
LASERFICHE CONTENT MANAGEMENT SYSTEMS
RESOLUTION NO.: , 2018
INTRODUCED BY:
WHO MOVED ITS ADOPTION
SECONDED BY:
WHEREAS, by Resolution No.: 83,2016, the Queensbury Town Board authorized
engagement of the services of General Code to develop and implement an integration to connect
the Town's EnerGov system with its selected content management system, Laserfiche Content
Management System (Project), as set forth in General Code's Statement of Work/Agreement
dated 11/2/2015 for an amount not to exceed $23,530, and
WHEREAS, due to certain changes in the software capabilities, a change to the Project is
necessary, and
WHEREAS, General Code has accordingly provided a revised Statement of
Work/Agreement providing for such changes dated 7/13/2018 and presented at this meeting for a
total amount not to exceed $20,700 ($2,830 less than its 2015 proposal), of which $11,765 has
already been billed, leaving a balance of$8,935 to be billed, and
WHEREAS, the Town Board wishes to authorize such replacement/superseding of
General Code's original Statement of Work/Agreement dated 11/2/2015,
NOW, THEREFORE, BE IT
RESOLVED, that the Queensbury Town Board hereby authorizes General Code's
Statement of Work/Agreement dated 7/13/2018, to replace/supersede its previous Statement of
Work/Agreement dated 11/2/2015, for a total amount not to exceed $20,700 of which $11,765
has already been billed, leaving a balance of$8,935 to be billed, and
BE IT FURTHER,
RESOLVED, that payment for such services shall continue to be from Computer
Software Account No.: 204-1680-2032, and
BE IT FURTHER,
RESOLVED, that the Town Board further authorizes and directs the Town Budget
Officer to amend the Town Budget, make any adjustments, budget amendments, transfers or
prepare any documentation necessary to provide for such payment, and
BE IT FURTHER,
RESOLVED, that the Town Board further authorizes and directs the Town Supervisor to sign
the Statement of Work/Agreement substantially in the form presented at this meeting and any other
necessary Agreements or documentation and the Town Supervisor and/or Town Budget Officer take
any and all action necessary to effectuate all terms of this Resolution.
Duly adopted this 61h day of August, 2018, by the following vote:
AYES
NOES
ABSENT :
GENERAL
A Member of the iCC Family of Companies
General Code
Statement r
Version 2.0
7/13/2018
Presented by:
General Code
rep aces-:
GENERAL
of Me V:'Famn;zy of
Project Information
Town of Queensbury, NY
EnerGov\Laserfiche Integration
Statement Of Work/Project Overview
Introduction:
The Town of Queensbury is installing the EnerGov solution by Tyler Technologies, Inc.to support their
Building and Planning Department. EnerGov is a web-based software system supporting land use
planning and project review, regulatory management, inspections,code enforcement,citizen requests,
asset management,work order management and more.
EnerGov has established an API to enable it to integrate with external content management systems.
To-date Tyler Technologies, Inc. has built integration functions to connect EnerGov with the Tyler
Content Management system, but not with Laserfiche,the selected content management system for the
Town of Queensbury.
The Town of Queensbury would like General Code to implement the ECS integration solution to connect
the EnerGov system and Laserfiche Content Management system. The basic functionality would
leverage the API developed by EnerGov,but also include basic document routing,organization and
indexing within the Laserfiche system.
Basic EnerGov-Laserfiche Functionality will include:
• Interface to interpret EnerGov API calls for insertion,deletion,and updating documents within
Laserfiche.
• Interface to return designated information (ex. Document ID, URL or other)to EnerGov API
interface.
• Laserfiche Workflows to apply templates and update template information on documents
based on UpdateMeta data information
• Laserfiche Workflows to route documents to appropriate Parcel and Document type Subfolder,
or Document Type subfolder if not a Parcel-related document.
• Laserfiche Workflows to route Permit Renewals to related Permit document folders
• Laserfiche Workflows to Delete documents based on Document ID passed from EnerGov.
7/13/2018 Statement of Work Page 2
GENERAL
Laserfiche/EnerGov Integration Information (from ECS)
Product Name
Tyler EnerGov Integration by ECS Imaging
Product Summary
ECS's integration for Tyler EnerGov and Laserfiche seamlessly transfers documents and files uploaded to
the EnerGov as an attachment to Laserfiche.The documents in Laserfiche are automatically indexed
based on key-identifiers from Tyler.
Product Overview
The Tyler EnerGov Integration by ECS imaging offers organizations the ability to centralize long term and
archival storage of EnerGov documents and files in Laserfiche.
The integration automates the process for sending documents to Laserfiche in an intelligent way—
through dynamic routing-that stores incoming documents into an easy to browse folder structure in
Laserfiche.Additionally,the ECS integration utilizes existing index information extracted from EnerGov
to append fields in Laserfiche to make searching fast and efficient.
Once documents or files are stored in EnerGov,they are immediately transferred to Laserfiche.Only a
stub of the record(logical document) remains in EnerGov as the physical file is stored in Laserfiche.
When the logical document is accessed from within EnerGov the document is opened with any of the
Laserfiche web clients, e.g.WebLink or Web Access.
Compatibility
Tyler EnerGov Versions 9.8.2+and 2016.0+
Laserfiche Server Versions 9.0.0+and 10.0+
Features
• Ability to synchronize index information of a document
o If a document record's index information in EnerGov is updated,the integration will
automatically update the index information in Laserfiche.
• Ability to synchronize the deletion of a document
o If a document record in EnerGov is removed,the integration can also remove the
document from Laserfiche.
• Ability to access related documents in Laserfiche from Tyler EnerGov
• Direct integration using the EnerGov API and the Laserfiche API
o A direct integration reduces issues with compatibility and longterm stability upgrading
either EnerGov or Laserfiche systems.
Resources: http://ecsimaging.com/services/integration/
Product Version Number v2.0
Languages Supported: English
Requires Laserfiche Products:Laserfiche Key-Integration License,and Laserfiche Web Access or
Laserfiche Weblink
7/13/2018 Statement of Work Page 3
GENERAL
Assumptions:
• Queensbury would like documents within Laserfiche be stored in a logical organization
even though they will be primarily accessed via the EnerGov interface.
• Queensbury would like metadata for documents to be stored within Laserfiche as well
as within EnerGov for ease of searching and locating documents.
• All Documents to be accessed via EnerGov must be entered via the EnerGov interface.
There is no functionality by which EnerGov can identify new documents within
Laserfiche that did not get stored via EnerGov.
• Documents that do NOT need to be accessed via EnerGov may be entered directly into
the Laserfiche system, but will not be visible via the EnerGov interface.
• All Documents within Laserfiche from the EnerGov interface will be set as"Read-Only"
for all but the EnerGov LF User.
• All Metadata will be entered and modified via the EnerGov interface and will be made
"read-only"inside Laserfiche for all but the EnerGov LF User.
• Documents within Laserfiche may be moved by end users without affecting the
EnerGov interface as EnerGov requests documents based on Laserfiche's Document ID,
which is static for each document.
7/13/2018 Statement of Work Page 4
SERA
Em's
EnerGov Document Management AN
Description
EnerGov software exposes an API that allows it to integrate with any document management software.
Integration with Tyler Document Management(TCM) is provided out of the box, but an integration
plugin must be written for all other document management systems.
Infrastructure
Integration with document management is mostly performed by a background windows service that is
distributed as part of overall install or upgrade package and are located in
EnerGov.Integrations\lntegration.WindowsService folder. This service must be installed. There is one
change that must be made is to the web.config file.
• Correct connection string to the main EnerGov database must be provided in the
connectionStrings area for connection string with the name of EnerGovData Entities.
• Integration with document management system relies on plug in architecture. EnerGov expects
a .NET DLL plug in to exist in its binaries folders.
Integration Details
Inside this DLL it expects to find a class that implements its required interface: IService. The details of
the service are described in the accompanying help file (chm)file
EnerGov.Con tentManagement.Integration.chm. Developers that are familiar with the document
management system need to create this DLL by referencing
EnerGov.ContentManagement.Integration.dll DLL located in main application's binaries folder. Once
implementation is completed,only the new plug in DLL needs to be copied into binaries folder of each
EnerGov subsystem. This includes main application,all windows services and all web services that a
customer is using.
Then EnerGov itself needs to be setup in System Setup>District Setup>System Settings>System
Integration.You must check the'Enable Content Management Integration' box. All other settings,
including web service URL and user credentials,will be passed into (Service instance. Finale setting, DLL
name is simply the name of the plug in .NET DLL.
Content Management Integration Settings
Enable Content Management Integration
Content Management 8ase Service URL 1 http://Iocathost:8080/tylercm/services/
Content Management User Login I admin T
Content Management User Password •-•-s
Content Management DLL Flame �TylerContentManagement.Integration
IService
The integration service has the following main methods:
• DeleteDocument. Delete document previously uploaded to document management system
because a user chose to delete it from EnerGov.
7/13/2018 Statement of Work Page 5
x E N A L
_k
• GetDocument. Get a document with metadata and binary content based on document
management system internal identifier.
• GetDocumentUrl. EnerGov expects to get a URL that an EnerGov user can navigate to using a
browser. This method expects document management system internal identifier.
• InitializeService. Described previously. Called once when an instance of the service is created
by EnerGov.
• PutDocument. Create new document in document management system. EnerGov expects to
receive document management system's internal identifier for newly created document. This
document identifier will later be passed into GetDocument,GetDocumetnUrl, UpdateMetadata
and DeleteDocument methods.
• UpdateMetadata. Update EnerGov specific metadata fields inside document management
system.
It also give developers an ability to write informational and error messages by creating their own
WriteError and Writelnfo messages,although those are not communicated to EnerGov.
The implementation of this interface must be found on exactly once class inside the plug in DLL. Any
additional methods and classes can also exist in the same plug in dll.
Metadata
Metadata that is passed to document management system inside IDocument.Metadata is controlled
completely by EnerGov,thus should be read-only inside document management system. Type field
points to EnerGov specific entity,such as permit. It can be used inside document management system
to provide groupings. However,the word itself is controlled by EnerGov,thus document management
system should be setup to match it. Here are all available types
• EnerGovinspection
• EnerGovBusinessLicense
• EnerGovPermitRenewalCase
• EnerGovApplication
• EnerGovinvoice
• EnerGovExamSitting
• EnerGovPlan
• EnerGovExamRequest
• EnerGovRentalProperty
• EnerGovCitizen Request
• EnerGovPayment
• EnerGovPermit
• EnerGovindividualLicense
• EnerGovindividualTaxRemittanceAccount
• EnerGovinspectionCase
• EnerGovObjectCase
• EnerGovGlobalEntity
• EnerGovBusiness
• EnerGovlmpactCase
7/13/2018 Statement of Work Page 6
" "NERAL
r r
• EnerGovParcel
• EnerGovProject
• EnerGovLand Lord License
• EnerGovCodeCase
The number of actual metadata fields depend on document type. Here is the full metadata layout,
ordered by document type. Collection flagged metadata properties will be exported as collection,thus
need to be handled appropriately inside document management system. The actual fields from each
item in the collection will be in the metadata multiple times. They can be grouped together using
Instance property inside(Field implementation.
7/13/2018 Statement of Work Page 7
GENERAL
OEM
GC Streamline EnerGov Integration Description
_�y 00 xs. ���?sa
0-1
Pro ect:Mana ement
EnerGov-Laserfiche Project Managements Support
Project Management including Planning,Communication,Change $ 150 8 $ 1,200
Management Progress Reporting
TOTAL Project Management $ 1,200
Laserfiche`Configuration,
Existing Laserfiche Data Conditioning
Workflows to transfer data from existing to EnerGov templates(for $ 150 4 $ 600
searching across Laserfiche-includes data mapping and field splicing)
Workflows to enhance metadata based on existing database information $ 150 8 $ 1,200
on existing Building documents.(Add permit where available,standardize
Parcel IDs,add address information,etc.)
Workflows to update document organization folderstructure to work with $ 150 4 $ 600
EnerGov
TOTAL Laserfiche Configuration $ 2,400
Integration ConfI uration
ECS Laserfiche API Software 1 $ 8,500 1 $ 8,500
ECS Laserfiche API Services(Configuration and Training) 1 $ 3,600 1 $ 3,600
TOTAL Integration Configuration $ 12,100
Additional Software-;Annual=Subscri Pions/Su " ort
Keyed Integrator's License for EnerGov Integration with Laserfiche $ 3,000 1 $ 3,000
ECS-Laserfiche API Annual Maintenance 1 $ 2,0001 1 $ 2,000
TOTAL ADDITIONAL SOFTWARE SUPPORT COSTS $ 5,000
Year 1 Grand Total (includes 1st Year Annual Subscription/Support) $ 20,700
"Please Note:this replaces/supercedes the original Change Order/Statement of Work—Contract-
QU1252—3-2-16,which was for a total of$23,530.00,of which$11,765.00 has already been billed,
leaving a remaining$8,935.00 to be billed.
7/13/2018 Statement of Work Page 8
GENERAL
Change Management Process
All change requests must be made in writing and approved by all parties before any
work is done.
Acceptance and authorization
The terms and conditions of the Professional Services Agreement apply in full to the
services and products provided under this Statement of Work.
IN WITNESS WHEREOF, the parties hereto each acting with proper authority have
executed this Statement of Work, under seal.
Full name Full name
Title Title
Signature Signature
Date Date
7/13/2018 Statement of Work Page 9