Insert Agency Name

REQUEST FOR PROPOSAL:

ELECTRONIC PLAN REVIEW PLATFORMRFP# Insert RFP NumberPUBLISHED: Insert Date of Publication

PROPOSALS ARE REQUIRED BY: Insert due date and time

PROPOSALS ARE TO BE SUBMITTED TO: Insert address

Table of ContentsA) INTRODUCTION............................................................................................................................3

A1) AGENCY BACKGROUND...............................................................................................................3

A2) PURPOSE OF RFP..........................................................................................................................3

A3) SOLUTION OBJECTIVES................................................................................................................3

A4) SOLUTION REQUIREMENTS.........................................................................................................4

B) PROPOSAL FORMAT.....................................................................................................................5

B1) PROCUREMENT CONTACT...........................................................................................................5

B2) PRE-PROPOSAL MEETING............................................................................................................5

B3) RESPONDENT QUESTIONS...........................................................................................................5

B4) RFP TIMELINE...............................................................................................................................6

B5) GENERAL CONDITIONS................................................................................................................6

C) PROPOSAL FORMAT.....................................................................................................................6

C1) EXECUTIVE SUMMARY.................................................................................................................6

C2) PROPOSED SOLUTION..................................................................................................................6

D) CURRENT ENVIRONMENT.............................................................................................................8

D1) BUSINESS PROCESS......................................................................................................................8

D1.A) EXISTING SYSTEM ARCHITECTURE.......................................................................................9

D1.B) EXAMPLE DEPARTMENT OUTLINE: PLANNING....................................................................9

D1.C) RECORDS MANAGEMENT..................................................................................................10

D1.D) DEVELOPMENT COMMUNITY............................................................................................10

APPENDIX A: REQUIRMENTS MATRIX.................................................................................................11

A) INTRODUCTIONA1) AGENCY BACKGROUND

This section is used to provide background information on your agency. It should include location, population, purpose (both internally and externally). An example follows.

Anytown, USA is a bustling suburb of Megacity, USA. It boasts a population of 63,000 people, with an influx of an additional 10,000 people during fishing season, which occurs from May to August each year. Anytown serves its constituents by providing expertise and assistance on land use projects. Actives related to the review of plans, processing, and verification of permits, complaints, regulatory code enforcement, inspection requests and other related activities fall under the purview of Anytown’s Community Development offices.

A2) PURPOSE OF RFPThis section is used to describe the circumstances which led to the development of the RFP and the overall goals your organization hopes to achieve. An example follows.

Anytown, USA is requesting proposals for software and services to implement an Electronic Plan Review (EPR) solution. The objective is to identify and recommend a hosted or cloud based EPR solution that allows the upload of electronic copies of plans and supporting documents and payment of associated processing fees via a public facing web portal. All electronic plans submitted would then be processed electronically for required and suggested changes to meet engineering, technical, and code specifications. In addition, centralized tracking of permits and inspections should be included and available. Mobile and Remote access will be required.

Anytown will retain certain software systems to which interfaces must be established in conjunction with this procurement. The proposed solution must integrate with: Laserfiche for document archiving ESRI Geographic Information System for mapping and spatial functionality Bluebeam Revu for plan review and markup

This RFP outlines the relevant business processes that are currently used for EPR. The preferred proposal will provide software and services for the EPR solution implementation, integration and training.

A3) SOLUTION OBJECTIVESThis section should provide specific examples of the project objectives. An example follows.

Plan Review Objectives Reduce the storage space and time required to physically manage paper copies of

site/building plans Enhance communications between and amongst reviewers and developers who are in

different departments and/or locations Decrease processing cycle time and/or number of cycles to submit and review site/building

plans Establish a cost-effective process for maintaining and configuring the solution over the long

term as new and changing requirements emerge Create a virtual one-stop-shop for applicants to securely and electronically submit and

manage plans and associated files (photos, videos, GIS maps, CAD drawings, text documents, electronic forms, etc.) required for a plan review application

Allow applicants to pay online for plan review services Allow for on-site intake scanning/processing for smaller development businesses that may

not have the capabilities to submit plans electronically Implement a multi-format document viewer and comment toolset that provides

architectural drawing markup capabilities and revision tracking for audit trails of all review activity

Dashboard functionality to monitor the status of review tasks and track the completion against scheduled due dates

Enable the flexibility to define the document review workflow and notification process based upon the requirements for each project

Support mobile access (smartphone or tablet) to plan review documents and comments

Permitting Objectives Dashboard functionality to monitor the status of review tasks and track the completion

against scheduled due dates Enable the flexibility to define the permit creation and management workflow and

notification process based upon the requirements for each project Reduce the storage space and time required to physically manage paper copies of permits Enhance communications between and amongst reviewers and developers/inspectors who

are in different departments and/or locations

Inspection Objectives Dashboard functionality to monitor the status of inspections and track the completion

against scheduled due dates Enable the flexibility to easily reallocate resources based on defined parameters as needed Enhance communications between and amongst reviewers and developers/inspectors who

are in different departments and/or locations Create a virtual one-stop-shop for applicants to securely and electronically submit and

manage inspection requests and results

A4) SOLUTION REQUIREMENTSThis section should provide specific examples of the project requirements. An example follows.

The Electronic Plan Review solution will provide internal and external agencies access to land development and building plans for review and approval purposes.

The Electronic Plan Review solution will be a web server based solution with a web browser client application that allows an estimated 300 concurrent users (50 internal users and 250 external (Development Community) users) to initiate and complete the entire plan submission and review process online. This includes the payment of any plan review fees using a credit card and the associated required interface to the Anytown’s web payment reception solution. It will also track all review activity in detail and create a log for review by anyone with appropriate access rights.

The Electronic Plan Review proposal will include recommendations for virtual meeting functionality. The web- based virtual meeting solution will be capable of “sharing” the web browser application(s) included in the proposed solution. Please include hardware/software specifications required for City supplied computers to participate in real-time collaboration between a minimum of 10 concurrent users.

Any required software for the proposed solution will be available to external Development Community users free of charge. The proposed solution must not require the use of Adobe Flash Player.

The proposed solution will incorporate responsive web design techniques to allow all web pages to be accessed by both mobile and desktop browsers.

The proposal will include the implementation of business process management technology that will replace existing paper based processes with new electronic document based processes that are significantly more efficient.

See Appendix A for a list of specific requirements. Responses should include this list with their documentation.

B) PROPOSAL FORMATB1) PROCUREMENT CONTACT

Insert the name, title and email address of the procurement contact here.

B2) PRE-PROPOSAL MEETINGInsert information pertaining to any pre-proposal meetings planned. Note whether the meeting is optional or mandatory and whether it will be provided in person, by phone, or by web. If none are required, please remove this section.

B3) RESPONDENT QUESTIONSInsert information regarding when and how the agency will respond to questions from applicants. An example follows.

To ensure respondents understand the RFP requirements, Anytown will accept one round of questions via email at <insert email address to be used> by the dates and times listed in Section B4 of this document. Questions will be answered via addendum posted after the deadline for questions. No additional questions may be asked outside of this forum unless asked in conjunction with the pre-proposal meeting.

B4) RFP TIMELINEInsert specific dates that correspond with the proposed RFP schedule.

EVENT DATE

RELEASE RFP InsertROUND 1 QUESTIONS DUE Insert

OPTIONAL PRE-PROPOSAL MEETING InsertEMAIL QUESTIONS POSTED Insert

PRE-PROPOSAL MEETING ATTENDEE LIST AND QUESTIONS POSTED

Insert

ALL ANSWERS TO QUESTIONS POSTED InsertPROPOSALS DUE Insert

SHORT LIST NOTIFICATION InsertSCRIPTED DEMONSTRATIONS OF SHORT LIST

RESPONDENTSInsert

SHORT LIST RESPONDENT REFERENCE CHECK InsertCONTRACT AWARDED Insert

CONTRACT EXECUTION InsertPROJECT KICK OFF InsertPROJECT GO-LIVE Insert

B5) GENERAL CONDITIONSThis section should provide specific details regarding the RFP conditions as they relate to your agency.

C) PROPOSAL FORMATThis section should provide specific instructions regarding the expected format of response. An example follows.

Please keep responses as simple and economical as possible, providing a straightforward and concise description of the proposed solution to meet or exceed Anytown’s business requirements. Costs incurred preparing and submitting a response are the responsibility of the responder. One sealed copy and an electronic copy of the proposal is required.

C1) EXECUTIVE SUMMARYProvide a general overview of the RFP response with a component summary including summary level costs for the software and services for which you are proposing.

C2) PROPOSED SOLUTION1. Provide a description of the proposed solution with a focus on superior features or

documented benefits that distinguish the solution.

2. List in detail all software licenses and services for the solution(s) for which you are proposing and the fixed cost price for each. Please use the following example format to present the costs for the proposed solution:

FY FY FY FY FY

18/19 19/20 20/21 21/22 22/23 TOTALONE TIME PROJECT COSTS

SOFTWARE Insert Insert Insert Insert Insert InsertSERVICES Insert Insert Insert Insert Insert Insert

IMPLEMENTATION Insert Insert Insert Insert Insert InsertINTEGRATIONS Insert Insert Insert Insert Insert Insert

OTHER Insert Insert Insert Insert Insert InsertTOTAL ONE-TIME

PROJECT COSTSInsert Insert Insert Insert Insert Insert

ONGOING COSTSSOFTWARE MAINTENANCE Insert Insert Insert Insert Insert Insert

HOSTING/CLOUD Insert Insert Insert Insert Insert InsertSUPPORT SERVICES Insert Insert Insert Insert Insert Insert

TOTAL RECURRING COSTS (5 YEARS)

Insert Insert Insert Insert Insert Insert

TOTAL COSTS Insert Insert Insert Insert Insert Insert

3. Provide a summary project schedule or timeline (Gantt chart or otherwise) working from the kick-off date noted in Section B4 above.

4. List maintenance and support service levels and costs for each.

5. Provide a list of references that have implemented a similar solution. The reference list must include the following:

Name of client, address, telephone number, and point of contact Date work was performed Brief description of work performed

6. Statement that the proposed Electronic Plan Review solution is compatible with targeted software requiring integration and with the plan review business processes described in this document.

7. Describe the overall solution architecture including the number of on premise servers (if any) and software licensing requirements for which Anytown would be responsible. Also include which open standards technology or language the solution uses (i.e., .NET, Java, etc.).

8. List any third-party application software or services that are needed for the proposed solution to operate and define their function. Please include all applicable version numbers.

9. Please describe the solution’s capability to create and maintain workflows for the following activities: Plan submittal process (intake) including upload file approval Plan review and approval processes

Automated e-mail notification(s) of:o submittalo completed reviewso re-submittalso review status by subordinates of a supervisoro approval exceptionso modification of an approved plan (i.e., as built drawing)

Archiving of approved plans

10. Please describe the solution’s capability to create, edit, issue, and track permit documents.

11. Please describe the solution’s mobile inspections capabilities.

12. Describe the solution’s ability to meet ADA Compliance for all web pages.

13. Recommend a virtual meeting solution and provide hardware/software specifications to allow Anytown to equip conference rooms and/or PCs with audio/video conferencing and desktop application sharing capabilities.

14. Complete the requirements matrix listed in Appendix A.

15. Provide an example Scope of Work (SOW) for a similar implementation.

D) CURRENT ENVIRONMENTD1) BUSINESS PROCESS

This section should provide information pertaining to the existing environment in place. An example follows.

Anytown’s development review process is its system of discussions, applications, reviews, and approvals that are in place to ensure that all construction, reconstruction and land development proposals, plans and documents meet all required regulations and policies. A set of approvals are required before each of the following major events can occur: (1) any work on the site, (2) any buildings constructed, and (3) any of the development and its buildings can be occupied.

There are seven (7) departments or divisions that are instrumental in the plan review process. These are:

Planning Inspections/Building Codes Engineering Stormwater Utilities City Fire Codes Compliance Department of Transportation

In addition, the County Health and Fire Departments may also be included in the required plan review processes.

D1.A) EXISTING SYSTEM ARCHITECTUREUse the table below to outline the existing environment.

ITEM STANDARDDESKTOP HARDWARE Insert

DESKTOP OPERATING SYSTEM InsertINTERNET BROWSER Insert

EMAIL SYSTEM InsertSERVER HARDWARE Insert

SERVER OPERATING SYSTEM InsertNETWORK OPERATING SYSTEM Insert

CENTRALIZED DATABASES InsertMOBILE HARDWARE InsertCELLULAR PROVIDER Insert

VIRUS SOFTWARE InsertREMOTE ACCESS Insert

FIREWALL InsertWEB SERVER SOFTWARE Insert

FINANCIAL/RECEIPTING SOFTWARE InsertARCHIVING SOFTWARE Insert

SERVER VIRTUALIZATION InsertUSER AUTHENTICATION Insert

D1.B) EXAMPLE DEPARTMENT OUTLINE: PLANNINGThis section should provide information pertaining to the specific department noted in the heading. An example follows.

NOTE: For each department noted in Section D1, a similar description should be provided to give a high-level overview of the basic operations.

The Planning division oversees development requests that require discretionary approval from the: (1) Planning Board; (2) County Commissioners; or (3) City Council. Before formally submitting their request, an applicant has the option of attending a Sketch Plan Review meeting. This involves the applicant submitting fourteen (14) paper copies of their site plan to the Planning division by a Monday deadline. The following Tuesday morning the paper site plans are distributed to each member of the interdepartmental review team which is composed of the following departments/agencies:

Department of Transportation Inspections Engineering Stormwater Erosion Control Utilities Fire (City & County) Planning Sanitation Codes Compliance

The various reviewers then email their comments to the Planning division’s administrative assistant who compiles the comments into one master document. That document is then

printed and given to the applicant during the Sketch Plan Review meeting on the Friday of that week.

Once an applicant finalizes their request, an application package is submitted to Planning staff to begin the review process. Shortly after the application package has been accepted and logged in, paper copies of the site plan are distributed to members of the interdepartmental review team. Upon receiving the site plan, they generally have about two weeks to review the site plan for compliance with their respective code and provide any comments they may have. Those comments are emailed to the Planning division’s administrative assistant who compiles comments from each team member into one document. That document is provided to the applicant at the interdepartmental review meeting. After this meeting, the applicant has roughly one week to address the comments that were provided at the interdepartmental review meeting. The final revised site plan is submitted to Planning; at which time Planning staff verifies that all comments have been addressed. After the Planning Board makes a recommendation on the request, it is forwarded to the appropriate elected body for a final decision.

D1.C) RECORDS MANAGEMENTThis section should provide information pertaining to the existing record keeping methodology in place. An example follows.

All plans received are scanned and saved electronically and stored in RMS under the related file and number. All construction-related documents are scanned, saved, and attached to the related entry in RMS. This includes but is not limited to:

Records of completion Hydrostatic reports Letters/Documentation Alternates (must be approved by the fire marshal) Photographs

Site plans are scanned and saved electronically on the drive specified for plans review and saved in the appropriate file. Hard copies are also to be maintained. Construction documents of any type are not shared or made available to any other vendor, contractor, designer, engineer/architect, public, etc., without the written consent of the original designer/owner and or approval by the City Attorney’s Office.

D1.D) DEVELOPMENT COMMUNITYThis section should provide information pertaining to the user experience for members of the development community. An example follows.

Prior to making application, an applicant must first determine property zoning and current use (as classified) in GeoData. Geo-Data Explorer is an interactive GIS (geographic information systems) tool for searching tax records and displaying map information.

Once an applicant logs the required information, they are ready to apply for the building permit. Anytown requires nine (9) hard copies of sealed drawings and corresponding application materials for distribution to the various review team members. Fees are collected with the initial submittal.

Applicants will receive an automatic notice in 2-5 business days that the review is under way. All other updates are logged into InspectNet by individual reviewers. InspectNet is an online application that allows customers to perform certain functions associated with permits. There is no consolidated checkprint at this time.

Once all comments are received, the applicant must then address the comments. Resubmission of plans may be required – and a full set (quantity of copies TBD) must be provided. Usually this step is not clear. Any clarity that could be introduced at this point would be helpful.

Once plans are approved, applicants go to the Office of Inspections, provide a plan number, sign the affidavit of worker’s comp coverage, and sign the permit. A copy of the approved plan is provided to the applicant at this time and must be kept on the job site. Any remaining fees are paid in the Finance Office.

APPENDIX A: REQUIRMENTS MATRIXThe intent of the Requirements Matrix is to note all applicable requirements in the various categories shown. A response code provides an at-a-glance review of respondent’s offerings. An example follows:

Please respond to the following requirements with YES/NO if the functionality is included. If no, please estimate the cost to provide the requested functionality via a customization or integration, if possible. Add comments as appropriate.

REQUIREMENTS INCLUDED CUSTOM COST

COMMENTS

1.2. INCLUDE A WEB BASED PROCESS ALLOWING APPLICANTS TO UPLOAD PLANS

3.4. INTERFACE WITH SOFTWARE APPLICATIONS OUTLINED IN SECTION A2 OF THIS DOCUMENT.

3.4. DISTRIBUTE PLANS ELECTRONICALLY TO MULTIPLE REVIEWERS

5.6. ALLOW MARKUP CAPABILITIES

7.8. AUTOMATE THE INCLUSION OF PLAN COMMENTS INTO ELECTRONICALLY GENERATED FORM LETTERS, WHICH CAN BE SENT VIA EMAIL ATTACHMENTS

9.10. PROVIDE SUBMITTED AND REVISED PLAN VERSION COMPARISONS

11.12. PROVIDE A DETAILED AUDIT TRACKING CAPABILITY THAT INCLUDES EVERY STEP IN THE PROCESS (I.E., DATE AND TIME THAT PLANS WERE SUBMITTED AND WHEN THEY WERE ANNOTATED WITH COMMENTS AND MARKED UP FOR REVISIONS, WHEN THE RETURNED PLANS WERE RECEIVED BY THE APPLICANT, WHEN THE REVISED PLANS WERE REVIEWED BY THE REVIEWER, ETC.)

13.14. ALLOW ONLY AUTHORIZED REVIEWERS AND PROJECT TEAM MEMBERS TO SEE AND MODIFY PLANS

15.16. ALLOW THE CREATION OF SECURITY GROUPS OF INTERNAL REVIEWERS

REQUIREMENTS INCLUDED CUSTOM COST

COMMENTS

17.18. DISPLAY AND TRACK VERSIONS OF ALL PLAN SUBMISSIONS, RE-SUBMITTALS AND REVIEWS. VERSIONS AND MARK-UPS MUST BE CLEARLY IDENTIFIED THROUGHOUT THE PROCESS.

19.20. ALLOW CONCURRENT REVIEW BY MULTIPLE REVIEWERS AND IDENTIFY WHICH REVIEWER MADE THE COMMENT OR ADDED MARKUPS

21.22. PROVIDE PROFESSIONAL ENGINEERING LEVEL REVIEW TOOLS INCLUDING BUT NOT LIMITED TO: ACCURATE MEASUREMENT TOOLS, AND THE ABILITY TO ADD WRITTEN COMMENTS, ACCURATELY SCALE DRAWINGS, EASILY MANAGE MULTIPLE PAGES, COMPARE DIFFERENT DRAWING “VERSIONS” VIA OVERLAY OF PAGES OR OTHER TOOLS, ADD LINKS OF REDLINED AREAS TO PRE-DEVELOPED SPECIFICATIONS SHEETS AND ADD NOTES WITH HYPERLINKS TO REVIEWED PAGES.

23.24. PROVIDE AUTOMATIC NOTIFICATIONS FOR INTERNAL AND EXTERNAL USERS THAT ARE CONFIGURABLE AT IMPORTANT MILESTONES OR PREPARED AT THE REVIEWERS DISCRETION AND SENT VIA EMAIL

25. HAVE ROLE BASED SECURITY FOR CONFIGURING ACCESS OF DOCUMENTS

26. PROVIDE ONLINE TRAINING DOCUMENTATION FOR INTERNAL AND EXTERNAL USERS

27. LDAP (LIGHTWEIGHT DIRECTORY ACCESS PROTOCOL) COMPLIANT AND USE MICROSOFT ACTIVE DIRECTORY (AD) GROUP SECURITY TO ALLOW ACCESS FOR INTERNAL USERS

28. MONITOR THE PROGRESS OF A SET OF PLANS THROUGH THE REVIEW PROCESS AND PROVIDE A SUMMARY OF THE REVIEW STATUS IF REQUESTED BY INTERNAL OR EXTERNAL USERS

29. ACCOMMODATE THE USE OF STARTING DATES AND END DATES FOR THE VARIOUS MILESTONES IN THE PROCESS30. HAVE THE ABILITY TO RESTRICT MENU ITEMS AND ASSOCIATED FUNCTIONS BASED ON SECURITY LEVELS

31. HAVE THE ABILITY TO RESTRICT ACCESS TO REPORTS BASED ON SECURITY LEVELS

32. PROVIDE AN SSL COMPLIANT LOGIN WEB PAGE TO ALL APPLICATION USERS

33. PROVIDE CONSOLIDATED REPORTS OF PLAN SUBMISSION DATES AND APPROVAL DATES

34. HAVE THE CAPABILITY TO CREATE/CUSTOMIZE STANDARD, SUPPLIED REPORTS TO MEET THE CITY’S BUSINESS PROCESS SPECIFICATIONS

35. HAVE THE ABILITY TO ARCHIVE AUDIT LOGS

REQUIREMENTS INCLUDED CUSTOM COST

COMMENTS

36. INTEGRATE WITH SAP CRYSTAL REPORTS AND/OR MICROSOFT SQL SERVER REPORTING SERVICES

37. HAVE THE ABILITY TO CREATE AND SAVE AD-HOC REPORTS OR SEARCHES

38. PROVIDE BASIC WORKFLOW STATISTICS AND TIME TRACKING REPORTS INCLUDING:

A) AVERAGE TIME TO COMPLETE FIRST PLAN REVIEW IN A SUMMARY FORMAT AND BY REVIEWER

B) AVERAGE TIMEFRAME FROM COMPLETION OF FIRST REVIEW TO RE-SUBMITTALS RECEIVED

C) OVERALL TIMEFRAME FROM APPLICATION RECEIVED TO COMPLETION OF THE PLAN REVIEW PROCESS

D) REVIEW TIMEFRAMES FOR EACH DEPARTMENT AND/OR WORKGROUP COMPARED WITH THE TARGET REVIEW TIMEFRAMES

E) REVIEW TIMEFRAMES MEASURING CITY/COUNTY TIME TO COMPLETE REVIEW AND TIME SPENT BY CITY/COUNTY WAITING FOR MORE INFORMATION FROM APPLICANTS TO COMPLETE REVIEWS

F) AVERAGE NUMBER OF RE-SUBMITTALS REQUIRED PER PLAN REVIEWER

39. ALLOW REPORTS TO BE RUN SIMULTANEOUSLY BY SEVERAL USERS WITHOUT AFFECTING THE SYSTEM PERFORMANCE

40. ALLOW REPORTS TO BE EXPORTED TO CREATE PDF, MS WORD, CSV, TEXT (FLAT FILE) AND HTML OUTPUT41. WEB SERVICE API INTEGRATION CAPABILITIES

42. CAPABILITY TO EASILY MANAGE PLAN REVIEW ASSIGNMENTS INCLUDING THE ABILITY TO REASSIGN MULTIPLE REVIEW TASKS FROM ONE PLAN REVIEWER TO ANOTHER PLAN REVIEWER IN THE SAME WORKGROUP

43. CAPABILITY TO AUTOMATICALLY CREATE AND ASSIGN A FOLLOW UP PLAN REVIEW WHEN A MODIFIED PLAN IS SUBMITTED BY AN APPLICANT

44. CAPABILITY TO CREATE AN OVERALL INDEX SHEET WITH HYPERLINKS TO DRAWINGS AND DOCUMENTS

45. ALLOW THE USER TO SELECT REPORT OUTPUT DESTINATION, WHICH COULD BE E-MAIL, FILE, PRINTER OR WEB/PDF

46. ALLOW COMMENTS TO INCLUDE HYPERLINKS TO ICC (INTERNATIONAL CODE COUNCIL) WEB PAGES AND HYPERLINKS TO LOCAL DEVELOPMENT ORDINANCES PUBLISHED BY MUNICODE

47. PROVIDE BATCH STAMPING OF MULTIPLE PAGES OF A PLAN SET, FOR EXAMPLE “APPROVED”

REQUIREMENTS INCLUDED CUSTOM COST

COMMENTS

48. ABILITY TO RETRIEVE PLANS REMOTELY IN THE FIELD VIA A TABLET BROWSER

49. ABILITY TO VIEW THE STATUS OF PLAN REVIEWS USING A MOBILE BROWSER (IE.SMARTPHONE/TABLET TABLET)

50. USE RESPONSIVE WEB DESIGN TECHNIQUES TO ALLOW ALL WEB PAGES TO BE USED BY MOBILE AND DESKTOP BROWSERS51. DOES NOT INCLUDE THE USE OF ADOBE FLASH ON ANY WEB PAGE OR APPLICATION WITHIN THE PROPOSED SOLUTION

52. PROVIDE THE FOLLOWING FUNCTIONALITY FOR PLAN REVIEWERS:

A) A WAY TO VIEW DIAGRAMS USING LAYERING TECHNIQUES TO SHOW/HIDE VARIOUS ELEMENTS

B) AUTOMATED TOOLS FOR THE REVIEWER TO MARKUP DIAGRAMS (WORDS, PICTURES, SKETCHES, HIGHLIGHTS, ETC.) INCLUDING THE ABILITY TO ASSOCIATE COMMENTS, HYPERLINKS TO REFERENCES & CITY CODES AND SORT AND/OR RANK COMMENTS

C) ABILITY TO IDENTIFY CHANGES (DELTAS) FOR RESUBMITTED DESIGN PLANS WHEN SUBMITTED USING STANDARDIZED FORMATS SUCH AS PDF AND/OR COMPUTER AIDED DESIGN (CAD) FILES

D) ABILITY TO CALCULATE VOLUMES, MEASURE AREAS (INCLUDING ACREAGE), DISTANCES (VIA POLY- LINE OR PATH), ANGLES AND RADII

E) A COMMON, FREQUENTLY USED COMMENT LIBRARY TO INCLUDE IMAGES, TEXT, TECHNICAL SPECIFICATIONS, ETC., WHICH IS CONFIGURABLE BY EACH REVIEWER

F) A DEDICATED LAYER FOR EACH REVIEWER FOR IDENTIFICATION BY OTHER WORKFLOW PARTICIPANTS

G) LOCKING OF THE PLAN SET ONCE APPROVED TO PREVENT ADDITIONAL CHANGES EXCEPT BY APPROVED INTERNAL CITY/COUNTY STAFF

53. PROVIDE THE ABILITY TO EXPORT AN ENTIRE PLAN SET OR A RANGE OF PAGES TO ONE MULTI-PAGE PDF FILE

54. INTEGRATE WITH CITY’S ESRI ARCGIS SERVER (V10.2.2) TO ALLOW INTERNAL AND EXTERNAL USERS TO DISPLAY A MAP OF THE LOCATION ASSOCIATED WITH THE PLAN SET

REQUIREMENTS INCLUDED CUSTOM COST

COMMENTS

55. ABILITY TO OVERLAY A PLAN SHEET WITH ONE OR MORE ESRI ARCGIS (V10.2.2) LAYERS

56. ABILITY TO COLLABORATE VIA ON-LINE CHAT CAPABILITIES WITH INTERNAL OR EXTERNAL USERS AND SAVE THE CONVERSATION

57. PROVIDE AUTOMATIC CONVERSION OF PLAN SET FILES TO PDF FORMAT

58. PROVIDE A GRAPHICAL WORKFLOW DESIGNER TO CREATE AND MAINTAIN THE WORKFLOW FOR THE VARIOUS PLAN REVIEW PROCESSES

59. COMPATIBLE WITH A HOSTED OR CLOUD BASED VIRTUAL MEETING SOLUTION

60. UNLIMITED (OR FREE) USER LICENSES FOR ALL SOFTWARE REQUIRED FOR EXTERNAL USERS

61. CAPACITY TO SUPPORT 300 CONCURRENT USERS (50 INTERNAL AND 250 EXTERNAL)

62. ABILITY FOR WORKFLOW TO INCLUDE BOTH LINEAR AND CONCURRENT REVIEW PROCESSES

63. AUTOMATIC PERMIT CREATION AND TRACKING

64. ABILITY TO DESIGNATE A PERMIT OR OTHER CERTIFICATE TYPE DOCUMENT AS BEING A “PARENT” DOCUMENT, WITH TRACKING AND UPDATES TIED TO “CHILD” PERMITS/CERTIFICATES

65. AUTOMATED FEE CALCULATION WITH ABILITY TO EDIT

66. BONDS/FEES COLLECTION (REAL TIME)67. ESTABLISHED REFUND/VOID PROCESS

68. INVOICING THAT IS COMPLIANT WITH AUDITING STANDARDS FOR THE STATE OF <INSERT STATE>

69. MOBILE ACCESS FOR INSPECTORS WITHOUT USE OF APP, WIFI, OR INTERNET CONNECTION.

70. UNLIMITED SUPPORT FOR ALL USERS (ADMINISTRATORS, END USERS, APPLICANTS).