Laserfiche WebLink
<br /> Page 1 <br /> <br />EXHIBIT A <br /> <br />STATEMENT OF WORK <br /> <br />1. Pilot Scope. During the Pilot Term, Govstream shall configure and deploy the Services detailed on <br />the SaaS Services Order Form. <br /> <br />2. Integrations. During the Pilot Term, Govstream shall configure the following data connections to <br />ground the Services in the City’s operational data. Govstream shall be responsible for all engineering and ongoing <br />maintenance of each connection. The City shall be responsible for providing Govstream with the access credentials, <br />sandbox environments, and advance notice of any system changes necessary to enable and maintain the connections <br />described below. The following integrations are required for the Pilot Term: (i) ingestion of City municipal code and <br />relevant website content into the Services knowledge base; (ii) GIS property and zoning data, using public endpoints; <br />and (iii) submission rules for each permit type in scope, configured as structured workflows within the Services. <br />Govstream shall also endeavor to configure an integration with the City ’s permitting system during the Pilot Term to <br />enable real-time permit status lookups and application data sync. This integration is subject to the availability of a <br />usable API. If no usable API is available, Govstream shall develop an alternative approach, which may extend the <br />integration timeline. Upon Pilot Conversion, Govstream shall additionally configure an integration with the City ’s <br />historical permit document repository to enable staff search of past perm it files and decisions, and an <br />Exchange/Outlook integration to support email-based inquiry management. <br /> <br />3. City Responsibilities. The City shall provide the following resources during the Pilot Term: <br /> <br />Role What They Do Estimated Time <br />Project Manager / Internal <br />Champion <br />Primary point of contacts from Permit <br />Services and IT. Coordinates access, <br />schedules staff sessions, tracks progress, <br />removes blockers. <br />~[45] hours total for the Pilot <br />Term <br />Subject Matter Experts <br />(planning, building, fire, <br />civil, permit techs) <br />Validate system accuracy, flag edge <br />cases, review scenarios, confirm the <br />system reflects how each discipline <br />actually works. <br />~1.5 hours/week max per <br />discipline <br />IT Support Security audit, integration enablement <br />(API access, credentials, sandbox <br />environments, firewall rules). <br />20–30 hours total <br />Executive Sponsor Steering, go/no-go decisions, escalation <br />path, alignment with broader City <br />priorities. <br />~2 hours/month <br /> <br />These estimates are based on our experience with similar deployments. Govstream will work with the project manager <br />to schedule all staff interactions with minimal disruption to day -to-day operations. <br /> <br />4. Delivery Plan. The Pilot Term shall not exceed twelve (12) weeks from the Effective Date, with a <br />target completion of eight (8) weeks. Govstream shall perform the following activities during each phase: <br /> <br />Phase 1: Discovery and Configuration (Weeks 1–3) <br />• Joint kickoff workshop with permitting staff. Align on scope, priority permit types, <br />success criteria, and points of contact. <br />• Security review and data-sharing agreement executed. <br />• Govstream ingests City’s municipal code, zoning maps, GIS layers, critical area data, <br />and permit submission requirements. Iterative validation with staff.