The URL can be used to link to this page

Home My WebLink About26 - Instructions - Permits, Licenses, & Code Enforcement (PLCE) Software and Implementation Services (5)Bozeman, MT PLCE Interfaces Please use the descriptions below to complete columns L - R on the subsequent tab. If the Respondent recommends additional interfaces, please add them in the table at the bottom of the interfaces tab and include them in the fixed fee price. Column A B C D E F G H I J K L M N O P Q R Response Key - Column L (Respondent Interface Plan) Available Response Keep Temporary Go-Away Not Accommodate Response Key - Column M (Direction_R) Available Response Inbound Outbound Bi-directional Response Key - Column O (Method_R) Available Response API File N/A Response Key - Column P (Experience) Available Response Yes No Response Key - Column Q (Type of Solution) Available Response Configurable Customized Indicates input cell for Respondent to supply information Header Application Application Description Interface Description Comments Direction Frequency Method City Interface Plan Direction_FS Frequency_FS Method_FS Respondent Interface Plan Direction_R Frequency_R Method_R Experience Type of Solution Comments_R Description A permanent interface with the ERP solution The interface that is only required during implementation The interface that is no longer required as a result of the new ERP solution Respondent will not accommodate this interface Description Respondent proposes an inbound data transfer to the ERP Respondent proposes an outbound data transfer from the ERP Respondent proposes a bi-directional data transfer to and from the ERP Description Respondent proposes an API to transfer data Respondent proposes use of a file to transfer data Type of connection is not applicable or unknown Description Respondent has developed an interface with the third-party solution Respondent HAS NOT developed an interface with the third-party solution Description Existing interface that will need to be configured Interface will require custom development Description Current City application Description of application Description of the interface needs with the application and future ERP City's comment on the interface for additional context Current data flow direction of interface Current frequency of interface Current method for interface The City's intention for the interface plan City's envisioned data flow direction of interface City's envisioned frequency of interface City's envisioned method for interface Respondent's proposed interface plan Respondent's proposed data flow direction Respondent's proposed frequency of interface Respondent's proposed method for interface Indicate if Respondent has experience developing interfaces with the third-party solution or provider Respondent should indicate if the solution is configurable or will require customed development Respondent should include any comments or assumptions relevant to the answers above Attachment 3.2 - PLCE Interface Application ActiveDirectory Atlas Selectron CityWorks Deckard First Due Future ERP System GIS (ESRI) Laserfiche Naviline ProjectDox (Avolve) Webhost Public Safety Suite Professional (Zuercher) Gallatin County If Respondent recommends additional interfaces not included in this, please add them here and include in Price Proposal Application Description Add additional rows as necessary Application Description Single Sign On Building permit inspection software Work order management and asset tracking Short Term Rental permits Commercial building inspections (Fire) TBD ERP System Infrastructure asset location tracking; Property file information Document storage Current ERP system that also provides Permits and Licenses functionality and takes payments for Permitting system Plan / application review software City website Police records Property Tax Records Interface Description Needs Interface Description Needs 1. Employee ActiveDirectory data 1. Permit data 2. Inspection results / comments 3. Correction notices 4. Inspection Assignments 1. Work Order management 1. Payment information 1. Licensing workflows and inspections 1. Employee data 2. Chart of Accounts / GL Mapping 3. Cash receipts / deposit advice 4. Summary revenue data by account code 5. Accounts receivable summary 6. Payments, refunds & voids 1. Parcel data (including address, intersection and other property identifiers) 2. Customer data (including owner, contractor, etc.) 3. Permit data 4. License data 5. Code Enforcement data TBD 1. Chart of Accounts / GL Mapping 2. Summary revenue data 3. Addressing 1. Automatic project creation in ProjectDox 2. Ability for ProjectDox to read permit, contact and fee details to display in eForm from the permitting system 3. Ability for ProjectDox to read default plan review groups, update, and add/activate and delete/deactivate reviews, including due dates, in the permitting system 4. Ability for ProjectDox to update permit/case status and/or tasks in permitting system 5. Ability for ProjectDox to push the approved final plans to permitting system for documentat retention once approval (and any revisions, as applicable) are complete 6. Ability for an API to be called from Avolve OAS to create a permit/case in the permitting system from application data gathered and submitted in OAS (Online Applicant Services) 1. Permit applications 2. Permit data 3. License data 4. Code Enforcement data 1. Code Enforcement case management 1. Property and Ownership information Comments Comments Currently Selectron is used for building permit inspections. An interface will be needed with the new PLCE if the proposed solution does not meet the City's needs. PLCE investigations can result in creation of work orders List Permitting providers for which Respondent has a pre-existing integration GIS is the source of truth for geospatial data Possible need to link PLCE transactions to documents stored in Laserfiche Envision needing a temporary integration for revenue data until new Permitting system goes live. Depending on ERP/UB/PLCE project sequencing, addressing may still reside in Naviline. Currently serves as portal for permit applications. If remains in future state, would like to know if payments made by applicant are completed in ERP, PLCE or ProjectDox Applications and permits/license/code enforcement information to be published on the City website when meeting specified steps in processing System for police records and misdemeanor code enforcement cases Direction Direction None Bi-Directional None None Inbound None Bi-Directional None None Bi-Directional None Frequency Current State Frequency N/A Real time N/A N/A On Demand N/A Daily N/A N/A Auto - On Demand N/A Method Method N/A Auto N/A N/A Manual Entry N/A Auto (programmatic) Procedures N/A N/A Auto Procedures N/A City Interface Plan City Interface Plan Keep TBD Keep Keep Keep New Keep Keep Temporary TBD Keep Direction_FS Direction_FS Bi-directional Inbound Bi-directional Inbound Bi-directional Bi-directional Bi-directional Bi-directional Inbound Bi-directional Outbound Outbound Frequency_FS BZN Envisioned Future State Frequency_FS Real time Real time Hourly Daily Hourly Real time Real time Ad-hoc Daily Real time Daily Daily Method_FS Method_FS API API API File API API API API File API API File Respondent Interface Plan Respondent Interface Plan Direction_R Direction_R Frequency_R Respondent Proposed Future State Frequency_R Method_R Method_R Experience Experience Type of Solution Type of Solution Comments_R Comments_R