The vendor will be completing work in digital form, primarily the Esri Geodatabase format. Most, if not all, data will be delivered in this format. Exactly how the GIS data is best transferred should be proposed based on experience working with other counties for this type of project. Interested vendors will have an opportunity to ask questions to clarify deliverables and/or any other part of this document. The following notes on Brown County’s GIS setup may help guide the approach:: • The Brown County v5 geodatabase, which as noted has already been designed to match the NENA NG911 schema, is a versioned Enterprise Geodatabase (Esri) version 11.2 upgraded for ArcGIS Pro 3.3. The database is based on SQL Server 2019. A copy of the database can be downloaded using the link in the project overview section of this document (this copy is provided for purposes of helping vendors define the scope of work for this project and view the database layout). • Once the project commences, perhaps the most ideal way to exchange data is to use Esri’s Distributed Database tools. In this workflow, Brown County would provide the vendor with a replica dataset, the vendor would complete work on attributes, boundary changes, and other necessary tasks, and then check in or synchronize edits back to Brown County’s enterprise geodatabase. o Brown County will continue to work on various aspects of this database while the vendor also does work on the replica. Esri’s enterprise geodatabase Versioning tools will be used to ensure that data is tracked and properly reconciled without loss of integrity. o If additional schema changes are needed, the vendor would work with the Brown County GIS Coordinator to make those design changes on the enterprise geodatabase on the county side, and provide the vendor with new replicas with the changed schema. o All changes to the data will be automatically logged using the Editor Tracking that is already set up in the database (created user, created data, last edited user, and last edited date). The vendor must ensure that editor tracking is turned on and always maintained, and that key fields such as GlobalID are also adequately maintained.
