REF# GENERAL REQUIREMENTS RESPONSE COMMENTS GR01 GR02 GR03 GR04 GR05 GR06 GR07 GR08 GR09 GR10 GR11 GR12 GR13

Transcription

1 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# GENERAL REQUIREMENTS RESPONSE COMMENTS GR01 GR02 GR03 GR04 GR05 GR06 GR07 GR08 GR09 GR10 GR11 GR12 GR13 The vendor will have the system up and running within 6 months of notice to proceed. The vendor is able to commence work within 1 month after the notice to proceed is received. If a hosted solution is proposed, can the vendor meet measurable standards for system availability (SLA)? Proposer must provide an enterprise solution for licensing, permitting, planning/zoning/land use, CRM case management, inspections and enforcement. System must be a 100% web based solution proven and installed with customers. System must provide multiple, user-friendly options for reporting including, but not limited to, simple and complex queries, exports, form letters and detailed reports with access to any data field. Vendor must have an established Customer Help Desk and provide online resources for customers. System shall have the ability to print licenses, permits and notices. The system must provide support for the conversion of data from the Town s existing system into the new system so that historical information is accessible. Data conversion services must be included in proposers bid. Ability to brand customer-facing and Town-facing screens, standard reports, adhoc queries, etc. The system needs to support parcel based functionality. The system must have built-in and customizable process controls to ensure completeness and correctness. (ex. Ability to defined required fields, setup dropdown lists, check and option boxes, edit checks, word AutoCompIete and spell check where appropriate, etc...).

2 GR14 GR15 GR16 GR17 GR18 GR19 GR20 GR21 GR22 GR23 GR24 GR25 GR26 GR27 GR28 The system must allow for data exports in a variety of file formats (Word, Excel, Access, CSV, etc). The system must support access to custom reports that utilize ODBC Connectivity. Data dictionary must be provided to assist in developing custom reports. The system should provide traditional counter and call center services to the web providing easy and convenient online access to application and permitting information. For example, application status, permit and inspection status and information, apply online, inspection requests online, FAQ's, Town building codes, permit application processes and procedures, and links to other informational sites related to the Building Division and the permitting, inspection, & Code Enforcement processes. The system must provide workflow processing with the ability to send automatic notifications at different stages of the process. System provides ability to route work to the next person(s) in a workflow based on process outcomes. The system must provide the Town the ability to create new permit types and add fields to both existing and new permit types, with administrative tools that do not require changes to the source code or base technology. The system must support the ability to enter in "legacy permits" issued from prior years. The system must support the ability to enter in "Iegacy inspections" completed from prior years. The system must support the ability to "rollback" the issuance of a permit. This is to support situations where a permit was issued in error. The system needs to reset application and permit counters at the beginning of each year. The system supports user-defined protected and required fields. The system must manage the issuing, collecting or waiver of fees. The system will prevent permit from being issued if payment has not been received. The system will support the creation of sub-permits (i.e. Electrical and/or Plumbing) from an existing Building permit or application. Related fields from Building permit will be inherited to the sub-permit.

3 GR29 GR30 GR31 GR32 GR33 GR34 GR35 GR36 GR37 GR38 GR39 GR40 GR41 GR42 GR43 GR44 GR45 GR46 The system needs to support the printing of itemized receipts for fees collected. This may be done before and after permit issuance. The system needs to keep an audit of activity including, but not limited to; username, creation or modification date/time, action completed, and status changes made within the system. The system should support digital signature technology. The system must have mobile support for staff and citizens. The system must have online context sensitive help. The system must support multiple users, multiple connections by a user, remote, and distributed access. Modules must have a consistent "Iook & feel" in terms of navigation and use. The system must allow users to access multiple applications or functions simultaneously via tabs or other means. The system should support applications for properties with multiple owners, tenants, contacts, customers, contractors, etc. The system must be able to generate form letters (i.e. Expiration of Permit, Violation Notices, Public Notices, etc...) in an editable format. System shall provide the ability to tab between fields on input forms. System presents data to users such that navigation is intuitive. System must use a role based security model. Town staff has control over who has rights to configure fields, drop down lists, menus, screens, fields, reports, etc. Search functionalities must include: narrowing searches, Boolean searches, truncated searches, text based searches, wildcard functions. The system should support unlimited user-defined fields. Ability to insert hyperlinks throughout the system to access related documents (e.g. zoning regulations, code violations, etc.) System administrator tools accessible through web interface

4 GR47 GR48 GR49 GR50 GR51 GR52 GR53 GR54 GR55 Ability to save and store frequently used text/comments which can be applied when needed and included in letters, notices, etc. yet edited if desired. Ability to print screens throughout the system. System administrator can add to or edit the contents of code tables (i.e., drop down lists). Ability for authorized Town staff to revoke a permit and issue a stop work order and to track and report stop work orders. Ability for property ownership data to be updated with with the Douglas County Assessor's office. System supports Laserfiche integration. Spell Check capabilities. Ability for Town staff to flag/alert specific applicants/customers for special conditions. System has tracking capabilities for locations (coordinates, legal descriptions, etc.) in addition to or in place of property addresses or parcel numbers.

5 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# WEB PORTAL RESPONSE COMMENTS WP01 WP02 WP03 The web portal should support private and secured access to allow building inspectors, code enforcement officers, and other staff members to retrieve and enter permit data, inspections, and code violations from the field. In addition to scheduling inspections via the web, system should support canceling or rescheduling of inspections. The web portal should support private and secured access (i.e. login required) to contractors, developers, architects, and other professional services that would allow them to view all permit applications they have submitted, inspection requests that they have requested, and inspection results. The web portal portion of the system shall support the acceptance of online comments and complaints. WP04 Ability to display comments. WP05 The web portal needs to be ADA compliant. WP06 WP07 WP08 Searches for permit/application information available by street address, owner information, contractor license/name, and permit/application number. Customer online access to view status of applications, permits, code violations, CRM cases, etc. Real time accessibility to application data (i.e. inspection results available once posted). WP09 Ability to upload electronic files online. WP10 Ability to make payments online via credit card. WP11 Ability to view map data online. WP12 Online address lookup capabilities. WP13 Ability to set public users permissions when creating a record. WP14 Allow Town staff to specify how public users schedule inspections online.

6 WP15 Ability to define inspection parameters that determine when public users can reschedule or cancel inspections. WP16 Ability for public users to request or schedule multiple inspections. WP17 WP18 Ability to hide inspection times and force public users to schedule inspections within a specific period. Ability to notify a licensed professional that his license and/or insurance and/or business license has expired. WP19 Ability to control the display of fields on the online application-intake form. WP20 Ability to calculate certain field values and populate other fields based on the calculation. WP21 Ability to validate field values when submitting a page. WP22 Allow registered public users to organize and manage their associated records online. WP23 The ability to automatically send s when inspection status is changed. WP24 Provide the ability for public users to search for records by contact. WP25 WP26 Allow public users to group records or other items in one location and pay for all items at the conclusion of the session. Allow Town staff to manage which documents associated with a record are available for public user deletion. WP27 The ability for a public user to perform a global search across all modules. WP28 WP29 WP30 The ability for public user to export search results in comma separated value (CSV) format. Renewals entered by the licensee through the Web Interface can be configured to fully process automatically, without human intervention, or renewals entered by the licensee through the Web Interface can be configured to be sent to an internal worklist, awaiting final approval by a staff person. Web interface can process credit/debit card transactions and update the database as needed, for such processes as license verification, duplicate licenses, reactivations and disciplinary fines.

7 WP31 On-line application forms can be developed by staff that are both printable and interactive for the customer in that they can create a new record in the database, capture the entered data and populate the new database record automatically. WP32 Web pages and on-line forms can be edited locally by Town staff, as needed. WP33 System can be configured to accept electronic (digital and encrypted) signatures. WP34 WP35 WP36 WP37 Web-based application processes (such as applications for initial licensure) that are not completed within a configurable time frame, can be scheduled for automatic deletion. Access by the public, through the web interface, can be limited to records or portion of records designated as public. Does your software provide options for remote access for field staff to log in and work, and, if so, please describe. The general public can have open access to some data elements without a login ID and password, but other access for persons doing business with the Town should require a login ID and password. Please confirm that both types of access can be allowed and describe the processes involved in generating user IDs and passwords.

8 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# PLAN REVIEW RESPONSE COMMENTS PR01 PR02 PR03 PR04 PR05 PR06 PR07 PR08 PR09 PR10 PR11 PR12 PR13 The system has the ability to annotate, upload, store and convert plans electronically. The system will send notifications to the applicant of status changes. The system will automatically determine which departments/agencies need to review the permit applications based on permit type and GIS proximity checks. The system will allow staff to add or remove departments/agencies from list of required reviews. The system will automatically electronically "route" the application information to the required reviewers. The system must support both serial and parallel plan review. The system prevents the approval of an application until Town-defined review requirements are met. The system prevents the issuance of permits until all required plan review approvals are completed and fees paid. The system tracks and logs each time an application is submitted for plan review. That is, if an application is rejected, then later resubmitted for review, historical info of when it was last submitted and reasons for rejection is readily available. The system is able to produce a plan review/correction report that would document all the correction requirements for approval. This report could be generated for a single department/agency or as a consolidated report. Reviewers from each agency involved in plan review are able to view the status and comments related to plan review. The applicant is able to view online the status and comments of his/her application in the plan review process. The system supports code searches and the ability to copy excerpts of code information to be pasted in correction notices.

9 PR14 PR15 PR16 PR17 PR18 PR19 PR20 PR21 PR22 PR23 PR24 PR25 The system is able to generate plan review checklists based on data in application form. Ability to retrieve and display entire plan sets, individual drawings and/or selected portions of the drawing or image. Ability to transmit an electronic image of an annotated plan to the applicant. Ability to monitor scheduled time off and time in queue for internal/external staff and integrates with MS Outlook. Allow manual workflow overrides by authorized Town staff (add new steps, remove steps, reorder steps). Rules-based workflow with triggers (date threshold, event, variance, etc.), alerts, alerts and actions (generate a letter, send an , etc.). Must use automatic warnings to manage workflow activities such as holds on permits and other processes. Must use status of reviews to determine next step(s) in permit, plan review, inspection, etc. processes. When all active parallel tasks are complete, the next task in a plan review workflow becomes active. The system shall provide the ability for customers to submit and request plan reviews, and to track the status of submitted plans. The system shall provide consistent plan review functionality for all participating agencies; plan review processes may vary by agency. The system is able to track/log/summarize Town staff's time spent on projects related to plan review and inspection.

10 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# APPLICATION PROCESS RESPONSE COMMENTS AP01 AP02 AP03 AP04 AP05 AP06 AP07 AP08 AP09 AP10 AP11 AP12 AP13 Create unlimited permit categories (Building, Fire, Planning, Code Enforcement, Public Works, Community Events, etc.). Create unlimited permit types (Building, Mechanical, Combination, Electrical, Grading, Plumbing, Sprinkler, Fire, Land Use, etc.). Unlimited user-defined permit conditions. Ability to add multiple standard conditions to a record in one submit process. The system needs to assist in tracking the physical location of applications and plans. The system will automatically calculate an issued permit's expiration date based on a user-defined formula. The expiration date would automatically be adjusted based on inspection requests and status updates. Trigger alert when permit is going to expire. The system will allow authorized user to update expiration date. The system is able to send out an automatic to the applicant or permit owner advising that the application/permit will be expiring. The system will retain property owner and contractor changes for all open applications and permits (i.e. final inspection not completed). The system will allow staff to place a "hoid" on an application or contractor. This would prevent permit(s) from being issued and inspections from being requested for the associated permit/applications and/or contractors/customers. Staff creating the "hoid" will need to include a reason for the hold. The system will allow a temporary override on holds and will require staff to enter a reason for the override. The system should have an internal "professional services database" that would hold license #'s, expiration dates, and general contact information (ie. business name, address, phone number, insurance certificates, licenses, etc...).

11 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP23 AP24 AP25 AP26 AP27 AP28 Automatically populate contact information for contractor, architect, etc. from master list. The system will generate an alert message when there are outstanding permit or reinspectlon fees or code violations associated with an application, permit, or an applicant. System supports the ability to copy permit applications from existing applications or permits by allowing user to specify which fields should be copied. System supports the ability to create a temporary application template that could be used to create multiple permit applications (which could be used for subdivision projects). Initiate multiple permits simultaneously from a single parcel. Users and customers can initiate a permit application from parcel selection on a GIS map. Mobile staff can initiate a permit application from the field. Mobile staff can initiate multiple permits from parcel selection on a GIS map. Ability to group permits under a single umbrella project. Track complex projects (e.g. multiple permits, multiple parcels, split parcels, roads, commercial and residential, multiple addresses, etc.) including pre-plan submission, plan reviews, permits, inspections, fees, payments, project team and assignments, etc. Ability to have the same license number assigned to multiple license types, such as electrical, mechanical, and plumbing licenses. Visibility across departments of where the permit is in the workflow routing, status, and who is working on each action. Must provide a function to allow staff to record communications between staff and the applicant specific to a project. Ability for Town personnel to complete a single application for a range of addresses (i.e. plumbing permits for all units in a condominium building). Ability for authorized staff to reinstate expired permits and determine and bill any applicable reinstatement fees.

12 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# FEES & PAYMENTS RESPONSE COMMENTS FP01 FP02 FP03 FP04 FP05 FP06 FP07 FP08 FP09 FP10 FP11 FP12 FP13 FP14 FP15 FP16 Ability to calculate, assess, and invoice fees. Ability to store unlimited fee schedules. The system shall utilize fee schedules consisting of fee codes with effective and expiration dates. Fee schedules may contain unlimited fee items. Supervisors have ability to override fees. Track bond/assurance amounts and reduce and release funds as milestones are met. Ability to allow online payment of fees. Ability to refund payments, void payments and manage invoices. The system shall retain historical fee schedules. The system should support flat fees (e.g. permit type and re-inspection). The system should support unit fees (e.g. plumbing and electrical fees that are based on fixtures and circuits). The system should support valuation fees (flat fee + variable fee based on valuation range and increments). The system shall support the collection of cash, check, credit/debit card, and mixed payment types. Payments should be recorded and stored for auditing purposes. The system shall provide the ability to support fee waivers. The system shall provide the ability to support additional fees. The system shall provide the ability to support penalties.

13 FP17 FP18 FP19 FP20 FP21 FP22 FP23 FP24 FP25 FP26 FP27 The system shall automatically calculate fees and be able to recalculate fees if changes are made to application/permit. The system shall support the manual entry of fees such as special inspections, reinspections, and penalty fees when appropriate. The system shall support the collection of miscellaneous fees that may not be associated with a parcel or application/permit number. (e.g. service charge for photo copies). The system shall provide ability to query and obtain listing of previously made payments by application number or other user-defined parameters. The system shall provide the ability to reprint receipts. The system shall maintain audit history of who collected the payment, when the payment was made, and who actually made the payment. Ability to calculate multiple special fees (e.g. surcharge fees) by line item. Allow for additional manual fee adjustments by Town staff. Allow for a "received" field that displays on all payment forms and lists which type (such as in-person, mail, phone, web) was used. Describe payment option for credit cards and electronic checks; what method is used for the processing? Integrates plan review/inspection (i.e. staff) time to generate invoices for customers.

14 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# INSPECTIONS RESPONSE COMMENTS I01 I02 I03 I04 I05 I06 I07 I08 I09 I10 I11 I12 I13 I14 The system shall support the entry of inspection requests, cancellations, scheduling, and rescheduling. The system shall assist in assigning inspection requests based on permit type. The system shall assist in creating a daily inspection schedule for each inspector. The system shall provide the ability to manually reassign inspection requests to another inspector. The system shall provide the ability to support remote access for inspectors from the field. The system should allow the inspector to enter his/her inspection results from field and to contractors/customers. The system shall provide the ability to record violations from a list of standard violation codes. The system shall provide the ability to link images (including scanned images and photos) and files to an inspection record. The system shall automatically update the permit status to "completed" once final inspection is completed. The system shall allow for final and expired to be unlocked and reset to active by inspection supervisor if a final inspection was completed in error. System would require a reason be recorded for auditing purposes. The system shall allow for unlimited comments on an inspection record. The system shall prevent the scheduling of inspections until inspection and/or reinspection fees have been paid. System will have an override option to this rule. For commercial electrical and plumbing inspection requests, the system should only accept requests generated by the electrical/plumbing contractor. The system supports electronic requests for certificate of occupancy from contractor and/or property owner.

15 I15 I16 I17 I18 I19 I20 I21 I22 I23 I24 I25 I26 I27 I28 I29 I30 The system should only allow the issuing of a certificate of occupancy when all inspections are finalized and all required agencies have signed off. The system should utilize GIS maps and aerial imagery in assisting inspectors planned inspections for the day. The system should generate driving directions for an inspector based on the inspections scheduled for a given day according to the order sequence they were scheduled to be completed. (Both a visual map representation as well as detailed driving directions of route). The system should have the ability to save an inspector's schedule along with the driving route for easy viewing and updating. Mobile unit should support quick access to all contact details (owner, applicant, contractor, complainant). Mobile unit should support quick access to permit info and other resources that would assist in completing field inspections. Inspection results from mobile units should update system in real-time. Mobile units need to support wireless and offline synchronization. The system should support automatic notifications to contractors of inspection results and status. When requesting inspections, customers should have the ability to display available inspection times and select a preferred time. Customer must have the ability to track the status of individual inspections related to a permit, address and project. Customers must have the ability to request re-inspection following correction notice. Ability to add a billable check box that allows agency users to indicate whether time spent conducting an inspection can be billed. Ability to carry over any failed items to all inspections that are scheduled. Ability to determine if a requested inspection is valid based on permit status. Abilities to produce paper copies of inspection documents.

16 I31 I32 I33 I34 I35 I36 Allow inspection results to initiate subsequent work flow processes. Ability to produce, display and print a list of inspections (past, current and scheduled) by permit number, address, applicant, contractor, or inspector. Multiple user-definable task checklists (e.g. inspection punch list) by permit/inspection type. Print correction notices in the field. The system allows for MS Outlook integration for scheduling. Ability to generate reports (for time periods) that summarize project/permit/enforcement activities.

17 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# COMPLAINTS, CODE ENFORCEMENT RESPONSE COMMENTS CE01 CE02 CE03 CE04 CE05 CE06 CE07 CE08 CE09 Ability to brand customer facing and Town facing screens, standard reports, adhoc queries, etc. System has a complaint and violation manager. System supports user pre-defined code violation description library. System supports the ability to attach photos and correspondence ( s, scanned letters, etc...) to complaint/violation records. System maintains a call log of calls made to contacts regarding complaint/violation case. History of case is retained and available for printout. System supports to contacts. System able to generate editable chronic violation and form letters using data from complaint/violation record. Code enforcement officer able to set due dates and schedule reminders of upcoming events and/or required actions (e.g. inspection Dates, Court Dates, Appeal Dates). CE10 CE11 CE12 CE13 CE14 System stores information regarding field inspections related to complaints/violations. System tracks and displays the number of days a violation is active. Code enforcement officer is able to "flag" parcel and/or property owner that would generate alerts in other modules of system (e.g, when property owner applies for a permit). Support unlimited number of complaint and/or violation types. Manage complaints, cases, history of violators, type of violation, related actions, remedies, etc. Track numbers for each.

18 CE15 CE16 Does the proposed system have the ability to submit complaints online through the CRM module with the option of remaining anonymous. Ability to view the status of a complaint investigation.

19 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# GIS RESPONSE COMMENTS G01 Integration with ESRI 10.1 GIS based products. G02 Support ESRI ArcGIS Server Standard G03 G04 G05 G06 G07 G08 G09 G10 G11 G12 G13 G14 G15 G16 Ability to map call center records and integrate with GIS. Integration of GIS with permit and inspection records. Ability to automatically generate the necessary notices (i.e. notices to the public) and determine the geographic requirements for these notices (i.e. radius, number of feet, etc.). System-wide search results are mappable. Able to view GIS maps within the software. Able to customize the maps for each individual software module (permitting, code enforcement, building, etc.). Able to fully customize symbology of map features (e.g., schools, electrical permits). Able to add any layers to the maps. GIS maps must include a table of contents that allows layers to be shown or hidden. Map tools available within the software must include: zoom, pan, identify, find, measuring, annotations. Properties can be geocoded in three ways: importing X and Y coordinates, matching attributes to shape features, and clicking on location in map. Able to import geodata into the property form. Able to open software forms directly from the maps. Inspections are mappable, and can be filtered by inspector, scheduled date, and permit or project.

20 G17 G18 G19 G20 G21 G22 G23 G24 G25 G26 G27 G28 G29 G30 G31 Able to generate and print customizable form letters to all property owners within any radius of a project, zoning permit, and code case. Can the system customize the GIS functionalities of the proposed software to appropriate inspectors. Can the system provide an administration site to configure map integration environments. Can agency users manage records directly from a map and submit new records, including work orders, inspections, asset condition assessments, and service requests. Support overlay or lookup of GIS data during the development process (zoning, proximity, sensitive ecology,etc.). Provide for integration between the planning/zoning/land use/public Works/CRM modules and the Town s GIS system. The system should be capable of importing parcel information from base system. Can the system show graphical parcel information in GIS. Can the system create a buffer zone in GIS. Describe in detail if the proposed system provides the ability to schedule inspection staff activities and optimize inspection schedule and travel routes. Describe in detail if the proposed system is capable of providing import routines and auto-populate functions that rely upon Town GIS data sources. Describe in detail if the proposed system is capable of providing bi-directional data display/exchange functions. Can the system show permit data for that parcel would be displayed and, conversely, once a parcel is identified new permit data can be captured through the GIS interface? Can the system provide a graphic alert to appropriate staff when a permit or inspection is determined to occur in another jurisdiction? Describe in detail if the proposed system is capable of providing different development special conditions once a GPS coordinate is captured and incorporated into the dataset for the potential or existing permit.

21 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# MOBILE DEVICES RESPONSE COMMENTS MD01 The system supports/provides a version of the software that can be deployed on a mobile device. MD02 The proposed wireless module must support ESRI ArcGIS Server Standard MD03 The proposed wireless module must provide a list of most recently viewed items. MD04 The proposed solution must have a job list that brings together all of the user s upcoming inspections or work orders. MD05 Online help and users guides. MD06 The proposed wireless module must be able to display the records on a map, automatically finding the most efficient route between locations and displaying the route on the map. MD07 The proposed wireless module must have touch screen capabilities. MD08 MD09 MD10 MD11 MD12 MD13 This proposed wireless module must have the capability to allow inspectors to input the information continuously into their wireless device (such as a laptop PC, etc.). The proposed system will store the information and automatically resume the upload of information to the proposed centralized application once the wireless connection is available and/or re-established. Describe in detail if the proposed wireless system provides access to permit, license, case, asset, and inspection-related data for inspectors. Describe in detail if the proposed wireless system provides access to record inspection results and update permit and inspection information. Describe in detail if the proposed wireless system provides immediate and automated notification of inspection results to the applicant. Describe in detail whether the proposed wireless system provides electronic document upload and download in the field.

22 MD14 MD15 MD16 MD17 MD18 MD19 MD20 MD21 Describe in detail if the proposed wireless system provides the ability to create new cases or permits in the field. Describe in detail whether the proposed wireless system provides GPS capture functions tied to permit locations. Describe in detail the inspector/role-based configuration tools available in the wireless client. Describe in detail the functions available in the Field Inspector interface that would provide for automated population of commonly used code violations and inspection comments. Describe in detail all wireless security measures/policies including wireless transmission protocols, encryption methods, and all other methods to assure data integrity between the wireless device and the central application. The mobile software shall be capable of printing notices, reports, violations, licenses, etc. from a field location (using a mobile printer). The system supports both synchronization and wireless connectivity communication for the mobile device. The mobile version should allow inspectors to enter inspection notes and report any code violations that may be identified during an inspection. MD22 The mobile version should allow inspectors to schedule follow-up appointments. MD23 MD24 The mobile version should allow the inspectors full access to all relevant information for their assigned case, inspection. The mobile version of the system should provide work management tools for the inspectors and their managers to review work status and all correspondence activities (phone calls, s, faxes, etc.) for each assignment.

23 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# REPORTING RESPONSE COMMENTS R01 R02 R03 R04 R05 R06 R07 R08 R09 R10 R11 R12 R13 R14 The application should provide the facilities to export report data to or integrate with Microsoft Office products. Ability for any report to be output as a PDF document. Financial reports should be defined by license/permit/inspection type or enforcement type. Fee reports can be created by date ranges, by license types and by specific licensees. The system should allow managers to view all of their direct reports work schedules and assigned activities. The system should have a robust ad-hoc reporting capability. The system should provide management dashboards for Town performance tracking (key result measures, Town goals and business and trend reporting/analysis). Ability to brand Town custom reports. Ability to report on any stored data element not restricted due to security. Ability for contractors to display and print authorized reports. Ability for the Town to display and print a set of requested transactions for a specified date and time range. Fields either exist or can be added for staff to enter unique, free-form text notes into a record; these can be marked as either public or internal across the multiple agencies. Staff can set up a schedule for periodic data extraction and automatic transmission. Form letters are fully configurable for the Town.

24 R15 R16 R17 R18 R19 R20 System can track and display previous versions of a form letters and will indicate what version was sent out to public. System can generate aging reports to identify requests (such as applications or complaints) that are overdue for a response. Users can access workflow lists of pending items that pertain specifically to their job responsibilities. Describe the internal mechanism or external software to be used to extract data sets. Describe the internal mechanism or software to be used to write form letters. Describe the mechanism used to spell-check letters and forms.

25 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# TECHNICAL RESPONSE COMMENTS TE01 TE02 TE03 TE04 TE05 TE06 TE07 TE08 TE09 TE10 TE11 TE12 TE13 TE14 Is the database MS SQL or Oracle? Windows 7 compatible. System will operate within the existing network/communications environment. System supports industry standard network protocols. System will provide ability to maintain multiple operating environments for development, test, training, and production. System is capable of restarting and recovering after system failure with no loss of data or software components. System shall provide full, incremental and differential backups and restorations of the database, core and customized software, software and configuration options, user preferences and permissions, etc... System Administration Tools - Specify any tools being proposed to support or supplement the application solution being proposed as well as for support of any third-party software. System provides timely notifications and reports of data entry problems. System error messages to users should show the exact status of the transaction, the options for on-line help, and the option to a pre-formatted problem report to Town support personnel. System shall provide customizable online documentation and training materials for technical and functional queries, with context-sensitive help and search capabilities. Permissions set at user and group level. Full control and management of permissions is done by the Town. User able to change their own password.

26 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# TRAINING RESPONSE COMMENTS TR01 TR02 TR03 TR04 TR05 TR06 TR07 TR08 TR09 TR10 TR11 TR12 TR13 Vendor can provide all training necessary to operate, use and maintain the system by all users. Vendor shall utilize a variety of training methodologies to maximize effectiveness of the training, including, but not limited to demonstrations, classroom presentations, hands-on experience and written materials. Several specific types of training will be conducted, including kickoff sessions, system administrator training and program staff training. Vendor shall be responsible for providing written training materials to assist users in learning the new system and provide reference materials for Town staff. Written training materials include user manuals. Written training materials include context-sensitive help screens within the program. Written training materials include quick reference system instructions. Vendor will provide the Town with reproducible copies of all training materials. Vendor will provide the Town with electronic copies of all training materials, in a format the Town can revise as future training requirements change. Training is considered an essential element of this project. On-site training will be required by the approved vendor for employees and staff that will utilize the technologies. Describe what type of training and the number of people to be trained that is included as part of the initial installation. Describe how you will schedule and provide for training of end users, technical staff, and system administrators including initial training, consultation, and follow-up training. Describe what types of additional training may be available through your company.

27 Response: Y, N, C, M, T, F Y - Yes or Meets; N - No or Does Not Meet; C - Configuration Needed; M - Modification Needed; T - Third Party Solution Needed; F - Future Release REF# MAINTENANCE RESPONSE COMMENTS M01 M02 M03 M04 M05 The vendor shall include the first year's maintenance contract as part of the proposal. Software support services are normally covered under maintenance agreements and provide support for issues encountered with the software. The vendor is required to provide a formal support issue priority mechanism and associated service levels for software support issues raised. All software upgrades (changes to versions, releases, or modifications) must be included in the maintenance agreement. During system rollout, vendor is responsible for providing initial on-site support for each program to ensure the system provides all functionality, deliverables and processing to fully support the system. All other system problems reported are responded to within a time-period agreed to by the Town. State whether software upgrade services used to implement the new version of the software are included in the software maintenance program.