CITY COUNCIL AGENDA
November 7, 2023
REGULAR SESSION - 6;00 P.M,
CLOSED SESSION FOLLOWING
ANDERSON CITY HALL
1887 Howard Street
PARTICIPATION BY PUBLIC IN MEETING
Please review the Agenda to determine if the subject you wish to discuss is scheduled for Council consideration. If it is on the Agenda, you will have an opportunity when that matter comes up for discussion to briefly address the Council.
If the subject is not on tonight's Agenda, please complete an Agenda Request Form (on Clerk's table) and present it to the City Council Clerk. You will have the opportunity to speak on the subject under Item 5.2. However, if the item is not on the Agenda, each speaker will be limited to one three (3) minute opportunity to speak. unless the City Council makes an exception due to special circumstances.
The Brown Act prohibits the Council from taking action on any item not placed on the printed Agenda in most cases.
The Brown Act requires any non-confidential documents or writings distributed to a majority of the City Council less than 72 hours before a regular meeting will be made available to members of the public at the same time they are distributed.
City Council meetings are televised and can be seen live on Cable Public Access Channel 181 (previously Channel 11) and on tape delay the following morning at 10:00 a.m. City Council meetings may also be viewed on the City's website at www.ci.anderson.ca.us by clicking on the TV icon on the Home Page.
In compliance with the Americans with Disabilities Act, the City of Anderson will make available to members of the public any special assistance necessary to participate in this meeting. The public should contact the City Clerk's office (378-6646) to make such a request. Notification 72 hours prior to the meeting will enable the City to make reasonable arrangements to ensure accessibility to this meeting.
This is an Equal Opportunity Program. Discrimination is prohibited by Federal Law.
Complaints of discrimination may be filed with the Secretary of Agriculture, Washington, D.C. 20250.
City Council Meeting
November 7, 2023
REGULAR SESSION - 6:00 P.M.
1.0 ROLL CALL - COUNCIL:
2.0 3.0
4.1 Councilmember Hunt
Councilmember Gallier
Councilmember Baugh
Vice-Mayor Neutze
Mayor Gallagher
INVOCATION - Anderson Police Department Chaplin Mary Little will give the invocation.
PLEDGE OF ALLEGIANCE - Mayor Mike Gallagher.
INTRODUCTIONS -
a. Acting Police Chief Nathan Rameriz will introduce new K9 Rip and his handler Officer Folden.
b. Acting Police Chief Nathan Rameriz will introduce new Cadet Hayden Ashley.
4.3 PRESENTATIONS - Shasta Mosquito Vector Control District Manager Peter Bonkrude will present their Annual Report.
5.2 PUBLIC COMMENT ON ITEMS NOT ON THE AGENDA - This is the time to address public comments by any member of the public to the Council regarding an item not on the agenda. Each comment must be limited to 3 minutes or less and on an item within the City's subject matter jurisdiction. The Brown Act does not permit any action or discussion on items not listed on the agenda. Are there any public comments?
CONSENT AGENDA
6.0 CONSENT AGENDA - Consent Agenda items are expected to be routine and noncontroversial. They will be acted upon by the Council at one time without discussion. Any member of the public, staff or City Council may request that an item be removed from the Consent Agenda for separate discussion. Are there any requests to remove any items from the Consent A9enda?
6.1 MINUTES - Approve the minutes of the regular meeting of October 17, 2023.
6.2 WARRANTS • Receive and file warrant 30164 to 30226 in the amount of $456,630.89; Receive and file warrant 30227 to 30273 in the amount of $130,651.57. Receive and file warrant 30274 to 30323 in the amount of $179,518.13. Receive and file ACH in the amount of $61,991.72.
City Council Meeting
November 7, 2023
Page3
6.3 CITY ATTORNEY - Approve the Amended Integrated Public Safety Memorandum of Understanding (MOU) between the City of Redding, the City of Anderson, the County of Shasta, and SHASCOM.
6.8 DEVELOPMENT SERVICES - Enact Ordinance No. 857 (second reading) General Plan Amendment 23-01 and Rezone 23-02 - Shady Ln -APN 052-340-067, Anderson Seventh Day Adventist Church as introduced on October 17, 2023 (first reading).
END OF CONSENT CALENDAR
6.11 ITEMS (IF AN)'.) REMOVED FROM THE CONSENT CALENDAR - Items removed from the Consent Agenda for discussion will be treated as Regular Agenda items and any member of the public may request to address the Council on any such item as it comes up for discussion. Please provide your name and limit your remarks to 3 minutes or less.
REGULAR AGENDA
8.0 REGULAR AGENDA - Regular Agenda Items will be discussed individually and in order.
Any member of the public may request to address the Council on an item as it comes up for discussion. Please provide your name and limit your remarks to 3 minutes or less.
FINANCE DIRECTOR
8.5 IMPLEMENTATION OF A NEW PAYROLL PROCESSING AND TIMEKEEPING SYSTEM RECOMMENDED ACTION:
Approve the implementation of ADP, Inc. payroll and timekeeping system to streamline all payroll-related processes and increase payroll accuracy and manpower within the Finance Department. Additionally, this will allow for the reduction of paper used and stored at City Hall.
DEVELOPMENT SERVICES
8.7 IMPLEMENTATION OF A DIFFERENT PERMIT PROCESSING SYSTEM WITH SOLAR APP+, CODE ENFORCEMENT & ONLINE PAYMENT PROCESSING RECOMMENDED ACTION:
Consider the approval of implementing Cloudpermit, building software that meets the requirements set forth by Senate Bill 379 and the Code Enforcement Software.
City Council Meeting
November 7, 2023
Page4
PUBLIC WORKS
8.9a AGREEMENTS PERTAINING TO DECLARED DISASTER 4308-DR RECOMMENDED ACTION;
Consider adoption of the attached Resolution authorizing the City Manager to execute for the City of Anderson an application and to file it with the California Governor's Office of Emergency Services to obtain certain federal financial assistance under Public Law 93-288 as amended by the Robert T. Stafford Disaster Relief and Emergency Assistance Act of 1988, and/or state financial assistance under the California Disaster Assistance Act.
8.9b ALLOW SHASTA COUNTY TO APPLY FOR THE SB 1383 LOCAL ASSISTANCE GRANT
PROGRAM ON BEHALF OF THE CITY OF ANDERSON
RECOMMENDED ACTION:
Consider allowing the Interim City Manager to sign the Letter of Authorization to allow Shasta County to apply for the SB 1383 Local Assistance Program on behalf of the City of Anderson.
8.9c ACCEPTANCE OF A PUBLIC SERVICE EASEMENT ON PARCEL MAP 22-02 FOR
MCMURRY DRIVE
RECOMMENDED ACTION;
Adopt a Resolution accepting the dedication of the offered five-foot-wide (5') public service easement based on the Planning Commission Resolution approval of the Tentative Parcel Map.
11.0 COUNCIL REPORTS/COMMENTS - City Councilmembers will report on attendance at conferences/meetin9s reimbursed at City expense (Requirement of Assembly Bi/11234.)
12.0 Public Comment on Closed Session Item(s): Anyone in the audience who wants to address the City Council on a subject which is listed under the Closed Session a9enda is now invited to come to the podium. Please provide your name and the subject you wish to discuss. Please limit your remarks to 3 minutes or Jess.
The Cit)' Council will convene to Closed Session.
CLOSED SESSION
City Council Meeting
November 7, 2023
C.S.1 PUBLIC EMPLOYEE PERFORMANCE EVALUTION
(Gov't. Code Section 54957)
Title: City Manager
C.S.2 CONFERENCE WITH REAL PROPERTY NEGOTIATIONS(§ 54956,8) - Property: APN: 201-620-077
- Agency Negotiation: City Attorney Collin Bogener
- Negotiating Parties: Ron Arndt
- Under Negotiation: Appraisal of Property
C.S.3 CONFERENCE WITH REAL PROPERTY NEGOTIATIONS(§ 54956,8) - Property: APN 201-920-019
- Agency Negotiation: Interim City Manager and City Attorney - Negotiating Parties: Listing Agent Ken Miller
- Under Negotiation: Appraisal of Property
C.S.4 CONFERENCE WITH LEGAL COUNSEL - ANTICIPATED LITIGATION - Initiation of litigation pursuant to§ 54956.9(c): (One Case) The City council will reconvene to CJ.pen Session.
13.0 CLOSED SESSION ANNOUNCEMENT: The Mayor will announce the results of the Closed Session.
14.0 ADJOURN - The City Council will adjourn to November 21. 2023.
ANDERSON CITY COUNCIL MINUTES
Regular Meeting
October 17, 2023
REGULAR SESSION
The regular session was called to order at 6:00 p.m.
ROLL CALL
Councilmembers present: Councilmember Hunt
Councilmember Gallier
Councilmember Baugh
Vice-Mayor Neutze
Mayor Gallagher
DRAFT
Also present: Acting City Manager /Police Chief Jon Poletski, City Attorney Collin Bogener, and City Clerk Christy White.
INVOCATION
Amarjit Singh of the Sikh Center gave the invocation.
PLEDGE OF ALLEGIANCE
Vice Mayor Stan Neutze led the Pledge of Allegiance.
PRESENTATION
Jared Tolman, Shasta Public Libraries Director, gave a presentation on the Library's new strategic Plan.
Community Services Director Joey Forseth-Deshais gave a recap of summer programs.
PUBLIC COMMENT ON ITEMS NOT ON THE AGENDA
Chris Martinez, Northern California Carpenters Union, spoke regarding health care, apprentice program and local hiring.
Ann Rogers spoke regarding a cat problem in her neighborhood and is asking for Haven Humane Society's help.
Mr. Amarjit Singh from the Sikh Center reminded Council of the Beyond Borders event on October 21, 2023 and invited them to attend.
ITEM 6.1 11/7/2023
City Council Meeting
November 7, 2023
CONSENT AGENDA
By motion made, second (Hunt/Baugh) and carried by a 5-0 vote, Council took the following action.
Approved the minutes of the regular meeting of regular meeting of October 3, 2023 and special meetings of October 5, October 9, and October 12, 2023.
Received and filed warrant 30031 to 30089 in the amount of $390,278.62; Received and filed warrant 30090 to 30163 in the amount of $361,376.02. Received and filed ACH in the amount of $62,038.49.
Approved the Side Letter Amendment to the Memorandum of Understanding between the City of Anderson and the Anderson Police Management Association regarding Patrol Sergeant Scheduling.
AYES:
NOES:
ABSTAIN:
ABSENT:
Councilmembers Hunt, Baugh, Gallier, Neutze and Mayor Gallagher.
None.
None.
None.
ALL NOTICES WERE GIVEN ACCORDING TO THE LAW
PUBLIC HEARINGS
GENERAL PLAN AMENDMENT 23-01 AND REZONE 23-02 - SHADY LN -APN 052-340- 067 ANDERSON SEVENTH DAY ADVENTIST CHURCH
Jennifer McDaniel, Director of Operations and Administration, gave a staff report and answered questions from Council.
6:49p.m. Public Hearing was opened. No comments were received, public hearing was closed.
By motion made, seconded (Baugh/Hunt) and carried by a 3-2 vote Council voted to adopt the CEQA determination, adopt a Resolution for General Plan Amendment 23-01 and approve an Ordinance for Rezone 23-02 (first reading) and set for adoption ( second reading) on November 7, 2023.
AYES:
NOES:
ABSTAIN:
ABSENT:
Councilmembers Baugh, Hunt, and Gallier.
Neutze and Gallagher.
None.
None.
City Council Meeting
November 7, 2023
REGULAR AGENDA
CITY ATTORNEY
APPROVAL OF INTERIM CITY MANAGER
City Attorney Collin Bogener gave a staff report and answered questions from Council.
By motion made, seconded (Neutze/Baugh) and carried by a 5-0 vote Council voted to approve Police Chief Jon Poletski as Interim City Manager.
AYES:
NOES:
ABSTAIN:
ABSENT:
Councilmembers Neutze, Baugh, Gallier, Hunt and Mayor Gallagher.
None.
None.
None.
DIRECTOR OF COMMUNITY SERVICES
ROAD CLOSURES ASSOCIATED WITH VARIOUS EVENTS RELATED TO CHRISTMAS IN ANDERSON 2023
Joey Forseth, Director of Community Services gave a staff report and answered questions from Council.
By motion made, seconded (Neutze/Hunt) and carried by a 5-0 vote Council voted to adopt Resolution 23-47 approving the city road closures linked to various activities connected to this year's Christmas in Anderson events.
AYES:
NOES:
ABSTAIN:
ABSENT:
Councilmembers Neutze, Hunt, Gallier, Baugh and Mayor Gallagher.
None.
None.
None.
AWARD BID FOR THE RIVER SPLASH SHADE STRUCTURE INSTALLATION PROJECT Joey Forseth, Director of Community Services gave a staff report and answered questions from Council.
By motion made, seconded (Gallier/Baugh) and carried by a 5-0 vote Council voted to award the contract for the River Splash Shade Structure Installation Project to GameTime in the amount of $103,641.91, authorize the City Manager to execute the contract upon receipt of the required insurance certificate and bonds, and authorize the Public Works Director to approve change orders not to exceed 15% of the bid amount.
City Council Meeting
November 7, 2023
AYES:
NOES:
Councilmembers Gallier, Baugh, Hunt, Neutze and Mayor Gallagher.
None.
ABSTAIN: None.
ABSENT: None.
COUNCIL REPORTS/COMMENTS
Councilmembers used this time to report on meetings and activities they participated in and to announce upcoming events.
Public Comment on Closed Session Items - None.
7:02 p.m.: The City Council convened to Closed Session.
CLOSED SESSION
8:11 p.m.: The City Council reconvened to Ogen Session.
CLOSED SESSION ANNOUNCEMENT
C.S.1 CONFERENCE WITH REAL PROPERTY NEGOTIATIONS (§ 54956.8) - Property: APN: 201-620-077 - Agency Negotiation: City Attorney Collin Bogener
- Negotiating Parties: Ron Arndt
- Under Negotiation: Appraisal of Property
C.S.2 CONFERENCE WITH REAL PROPERTY NEGOTIATIONS(§ 54956.8) - Property: Anderson River Park
- Agency Negotiation: City Attorney Collin Bogener
- Negotiating Parties: California Fish & Wildlife
- Under Negotiation: Transfer of Portions of the Park
Mayor Gallagher announced that the Council sat in Closed Session with no reportable action giving direction to staff on items C.S.1 and C.S.2.
C.S.3 CONFERENCE WITH REAL PROPERTY NEGOTIATIONS (SECTION 54956.8) - Property: 2800 Douglas Street, Anderson, CA 96007 Agency Negotiation: City Attorney Collin Bogener
Negotiating Parties: Michael and Judy Hubert
Under Negotiation: Value of Property
C.S.4 PUBLIC EMPLOYEE PERFORMANCE EVALUTION
(Gov't. Code Section 54957)
Title: City Manager
City Council Meeting
November 7, 2023
Mayor Gallagher announced that the Council sat in Closed Session giving direction to staff on items C.S.3 and C.S.4.
ADJOURNMENT
8:11 p.m.: The City Council adjourned to November 7. 2023.
Mike Gallaghe·r, Mayor
ATTEST:
Christy White, City Clerk
AGENDA ITEM
!November 7, 2023 City Council Meeting I
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From: Cindy Wheeler, Acting Finance Director /Treasurer Date: November 7, 2023
lsueJECT
Receive and File Weekly Warrant Registers.
I RECOMMENDATION
Receive and file warrant 30164 to 30226 in the amount of $456,630.89; Receive and file warrant 30227 to 30273 in the amount of $130,651.57. Receive and file warrant 30274 to 30323 in the amount of $179,518.13. Receive and file ACH in the amount of$61,991.72. !ATTACHMENT
Warrant Registers.
ITEM 6.2 PAGE1 11/07/2023
CHECK REGISTER
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
1 ROTT A, ST ACY
US REFUND 10/13/2023 030164 20.78
1 ENSSLIN, KATHY & BOB
US REFUND 10/13/2023 030165 20.78
1 HARRIS, CIERRA
US REFUND 10/13/2023 030166 19.68
1 WOLFMAN, CRAIG
US REFUND 10/13/2023 030167 6.56
1 CARRILLO, TAMMY
US REFUND 10/13/2023 030168 20.78
1 KELLY, DEBORAH
US REFUND 10/13/2023 030169 78.89
1 RHODE-LARSON, LISA &
US REFUND 10/13/2023 030170 36.21
00040 ANDERSON FIRE PROTECTION DIST.
INSPECTION/IMPACT FEES 10/13/2023 030171 15,838.30
00049 ANTHEM BLUE CROSS LIFE AND HEA
HEALTH INS. PREMIUM-HUNT 10/13/2023 030172 1,436.00
00051 APPLIED INDUSTRIAL TECH.
SUPPLIES 10/13/2023 030173 426.26
00061 AT&T CALNET
PHONE CHARGES 10/13/2023 030174 130.00
00175 CALIFORNIA SAFETY CO.
PROFESSIONAL SERVICES 10/13/2023 030175 28.00
00188 CARREL'S OFFICE MACHINES
MONTHLY LEASE 10/13/2023 030176 356.09
00195 CBSC
CBSC FEES 10/13/2023 030177 189.90
00204 CHARTER COMMUNICATIONS
INTERNET SERVICES 10/13/2023 030178 1,611.96
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
00210 CHIP
WATER OVERCHARGE REFUND 10/13/2023 030179 803.42
00215 CITY OF ANDERSON
UTILITIES 10/13/2023 030180 2,773.12
00239 CONSOLIDATED ELECTRICAL DIST.
SUPPLIES 10/13/2023 030181 58.56
00256 CRAFCO, INC.
SUPPLIES 10/13/2023 030182 167.02
00296 DEPT OF CONSERVATION
STRONG MOTION FEES 10/13/2023 030183 548.46
01181 DEWBERRY ARCHITECTS, INC.
PROFESSIONAL SERVICES 10/13/2023 030184 10,125.00
00306 DIV. OF THE STATE ARCHITECT
SB 1186 FEE BUSINESS LICENSES 10/13/2023 030185 358.40
00345 ENTERPRISE FM TRUST
VEHICLE LEASES 10/13/2023 030186 19,974.38
00359 FASTENERS INC.
SUPPLIES 10/13/2023 030187 1,583.87
00361 FERGUSON ENTERPRISES, INC.
SUPPLIES 10/13/2023 030188 3,262.76
00420 GOODYEAR COMMERCIAL TIRE
PROFESSIONAL SVCS & PARTS 10/13/2023 030189 1,397.87
00459 HAVEN HUMANE SOCIETY
PROFESSIONAL SERVICES 10/13/2023 030190 1,045.00
00516 J & T CONSULTING, INC.
PROFESSIONAL SVCS & SUPPLIES 10/13/2023 030191 1,486.00 00525 JENNIFER JIMERSON
PER DIEM-MEETING 10/13/2023 030192 15.00
00544 K & S STAFFING SOLUTIONS, INCJ
PROFESSIONAL SERVICES 10/13/2023 030193 216.27
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
00549 MARSHA KELLEY
CLEANING DEPOSIT REFUND 10/13/2023 030194 350.00
00602 LIDDELL CONST. SUPPLY INC.
SUPPLIES 10/13/2023 030195 184.47
00615 LOUCKS LANDSCAPE SUPPLY
MATERIALS 10/13/2023 030196 198.41
00616 LOWE'S
SUPPLIES 10/13/2023 030197 611.08
00690 MITEL CLOUD SERVICES
PHONE CHARGES 10/13/2023 030198 1,744.83
00705 MT. SHASTA SPRING WATER
DRINKING WATER 10/13/2023 030199 207.62
00707 MUNICIPAL MTNC. EQUIPMENT
SUPPLIES 10/13/2023 030200 1,306.34
00734 NORCAL RENTALS & SALES
EQUIPMENT RENTAL 10/13/2023 030201 962.63
00739 NORTHERN CALIF. GLOVES
SUPPLIES 10/13/2023 030202 52.19
00747 O'REILLY AUTO PARTS
PARTS 10/13/2023 030203 11.84
00747 OBSIDIAN IT
PROFESSIONAL SERVICES 10/13/2023 030204 287.50
00761 PACE ANALYTICAL SVCS., LLC
PROFESSIONAL SERVICES 10/13/2023 030205 209.88
00763 PACIFIC GAS & ELECTRIC
UTILITIES 10/13/2023 030206 7,286.82
00780 PEOPLE FACTS, LLC
PROFESSIONAL SERVICES 10/13/2023 030207 15.74
00796 PLATT
SUPPLIES 10/13/2023 030208 181.32
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
00805 POWERDMS, INC.
SUBSCRIPTION RENEWAL-POWERTIME 10/13/2023 030209 2,627.20 00806 PRAIRIE SQUARES
PROFESSIONAL SERVICES 10/13/2023 030210 92.40
00812 PROFORCE LAW ENFORCEMENT
SUPPLIES 10/13/2023 030211 22.57
00812 PROMOTIONAL IMAGES
SUPPLIES 10/13/2023 030212 45.66
00818 QUADIENT LEASING, INC.
QUARTERLY LEASE 10/13/2023 030213 1,509.85
00849 RENTAL GUYS REDDING
EQUIPMENT RENTAL & SUPPLIES 10/13/2023 030214 1,234.94
00866 RIVER CITY COMPLIANCE
PROFESSIONAL SERVICES 10/13/2023 030215 180.00
01021 SW MAINTENANCE CORP.
MONTHLY UST TESTING 10/13/2023 030216 65.00
01023 SWRCB/DWOCP
WATER DISTRIB. EXAM FEE-MATA 10/13/2023 030217 65.00
01057 TRANSUNION RISK AND ALTERNATIV
PROFESSIONAL SERVICES 10/13/2023 030218 75.00
01066 TYLER TECHNOLOGIES, INC.
PROFESSIONAL SERVICES 10/13/2023 030219 4,325.00
01074 US BANK CORP PYMT SYSTEMS
SUPPLIES, EQUIPMENT, TRAINING 10/13/2023 030220 21,993.70 VOID CHECK 10/13/2023 030221
VOID CHECK 10/13/2023 030222
01075 USA BLUEBOOK
SUPPLIES 10/13/2023 030223 191.85
01085 VCA GATEWAY ANIMAL HOSPITAL
PROFESSIONAL SERVICES 10/13/2023 030224 502.70
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
01094 VSS INTERNATIONAL, INC.
PROFESSIONAL SERVICES 10/13/2023 030225 345,696.58
01167 WELLS FARGO VENDOR FINANCIALS
MONTHLY LEASE 10/13/2023 030226 357.45
456,630.89
CHECK REGISTER
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
000026 A & A MACHINE AND WELDING
PROFESSIONAL SVCS & SUPPLIES 10/20/2023 030227 333.51
000243 ALL CAR & TRUCK TOWING, LLC
PROFESSIONAL SERVICES 10/20/2023 030228 1,645.00
000323 AMERICAN FfDELITY ASSURANCE CO
CAFETERIA 125 PE 10/13/23 10/20/2023 030229 282.68
000349 AMERICAN TOWER CORPORATION
MONTHLY TOWER RENT 10/20/2023 030230 975.00
000609 AT&T
PHONE CHARGES 10/20/2023 030231 95.25
001082 ENDICOTT TRUCKING, INC.
PROFESSIONAL SERVICES 10/20/2023 030232 2,880.00
001133 BIG VALLEY SANITATION
EQUIPMENT RENTAL 10/20/2023 030233 575.00
001757 CALL CENTER SALES PRO
PROFESSIONAL SERVICES 10/20/2023 030234 28.10
002047 CHARTER COMMUNICATIONS
INTERNET SERVICES 10/20/2023 030235 1,371.03
002142 CINTAS FIRST AID & SAFETY
SUPPLIES 10/20/2023 030236 3,303.62
002165 CITY OF REDDING
RENT SHASCOM FAC SUBL 10/20/2023 030237 7,054.35
002973 DEPT OF JUSTICE
FINGERPRINT APPLICATION 10/20/2023 030238 32.00
003590 FASTENERS INC.
SUPPLIES 10/20/2023 030239 841.88
003727 FLOCK SAFETY
ANNUAL EQUIPMENT FEE I 10/20/2023 030240 26,250.00
003927 MIKE GALLAGHER
HEALTH INS. REIMBURSEMENT 10/20/2023 030241 514.00
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
004040 GENERAL TEAMSTERS #137
DUES FOR MONTH OF OCT-23 10/20/2023 030242 2,719.00
004811 HILLYARD, INC.
SUPPLIES 10/20/2023 030243 403.65
005076 IBM CORPORATION
PROFESSIONAL SERVICES 10/20/2023 030244 99.00
005982 LEHR AUTO
SUPPLIES 10/20/2023 030245 715.15
006153 LOUCKS LANDSCAPE SUPPLY
MATERIALS 10/20/2023 030246 193.05
006723 DARREN MENDOZA
PER DIEM-TRAINING 10/20/2023 030247 375.00
006958 MOORE & BOGENER
PROFESSIONAL SERVICE 10/20/2023 030248 9,556.15
007075 MUNICIPAL M TNC. EQUIPMENT
PROFESSIONAL SERVICES 10/20/2023 030249 2,384.78
007394 NORTHERN CALIF. GLOVES
SUPPLIES 10/20/2023 030250 99.18
007477 OBSIDIAN IT
PROFESSIONAL SERVICES 10/20/2023 030251 3,658.17
007493 ODP BUSINESS SOLUTIONS, LLC
OFFICE SUPPLIES 10/20/2023 030252 885.88
007616 PACE ANALYTICAL SVCS., LLC
PROFESSIONAL SERVICES 10/20/2023 030253 263.80
007617 PACE ENGINEERING, INC.
PROFESSIONAL SERVICES 10/20/2023 030254 47,770.25
007669 PAPE MACHINERY
PARTS 10/20/2023 030255 809.05
I 007967 PLATT
SUPPLIES 10/20/2023 030256 132.98
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
008194 QUALITY SAW & MOWER
SUPPLIES 10/20/2023 030257 95.22
008407 REDDING RECORD SEARCHLIGHT
ADVERTISING 10/20/2023 030258 436.50
009045 SAFEGUARD FIRE PROTECTION
PROFESSIONAL SERVICES 10/20/2023 030259 3,036.10
009321 HOPE SETH
PROFESSIONAL SERVICES 10/20/2023 030260 2,100.00
009432 SHASTA COUNTY DEPT OF
PROFESSIONAL SERVICES 10/20/2023 030261 105.00
009551 SHIELD REGIONAL TRAINING
TRAINING FEES 10/20/2023 030262 90.00
009988 STATE OF CALIFORNIA
ASSIGN OF WAGES PE 10/13/23 10/20/2023 030263 30.00
010004 STATEWIDE TRAFFIC SAFETY & SIG
SUPPLIES 10/20/2023 030264 9.90
010732 UPS
SHIPPING FEES 10/20/2023 030265 105.64
010756 USA BLUEBOOK
SUPPLIES 10/20/2023 030266 553.85
011064 WASTE MANAGEMENT
DUMP FEES 10/20/2023 030267 706.02
011764 ALEC WHITE
PER DIEM-TRAINING 10/20/2023 030268 434.50
011792 M ISSIONSQUARE-302204
PLAN #302204 PE 10/13/23 10/20/2023 030269 4,335.00
011822 JEFF MAZE
PER DIEM-TRAINING 10/20/2023 030270 434.50
011929 ACME ANALYTICAL SOLUTIONS, INC
SUPPLIES 10/20/2023 030271 1,283.10
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
011999 PROSOURCE SPECIALTIES, LLC
SUPPLIES 10/20/2023 030272 612.23
012000 LUREE WEST
PARK RENTAL REFUND 10/20/2023 030273 37.50
130,651.57
10/25/23 ACH PERS 61,991.72
For Payroll Ending 10/13/23
Page4
CHECK REGISTER
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
011929 ACME ANALYTICAL SOLUTIONS, INC
SUPPLIES 10/27/2023 030274 41.18
000201 AL'S SAW SHOP
SUPPLIES 10/27/2023 030275 40.70
000406 ANDERSON FIRE PROTECTION DIST.
PROFESSIONAL SERVICES 10/27/2023 030276 800.00
000700 BADGER METER, INC.
EQUIPMENT 10/27/2023 030277 7,221.66
001750 CALIFORNIA SAFETY CO.
PROFESSIONAL SERVICES 10/27/2023 030278 28.00
001754 CALIFORNIA VISION SERVICE
INSURANCE PREMIUM 10/27/2023 030279 119.50
012005 COMPASSION PATHWAY BEHAVIORAL
BUS LICENSE OVRPYMT REFUND 10/27/2023 030280 189.00
002392 CONSOLIDATED ELECTRICAL DIST.
SUPPLIES 10/27/2023 030281 1,198.71
002592 CRESCO EQUIPMENT RENTALS
SUPPLIES 10/27/2023 030282 520.96
012001 AMBER DEPTUCH
CLEANING DEPOSIT REFUND 10/27/2023 030283 350.00
012003 LINDSEY DOMREIS
CLEANING DEPOSIT REFUND 10/27/2023 030284 350.00
011982 ED STAUB & SONS PETROLEUM
FUEL CHARGES 10/27/2023 030285 15,390.47
003396 EMERGENCY VEHICLE OUTFITTING C
PROFESSIONAL SVCS & EQUIPMENT 10/27/2023 030286 12,375.34 003423 ENERPOWER
UTILITIES 10/27/2023 030287 5,183.00
003534 EWING
SUPPLIES 10/27/2023 030288 646.29
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
003590 FASTENERS INC.
SUPPLIES 10/27/2023 030289 1,113.39
003618 FERGUSON ENTERPRISES, INC.
SUPPLIES 10/27/2023 030290 3,083.52
004067 GHD, INC.
PROFESSIONAL SERVICES 10/27/2023 030291 1,443.50
012004 JEFF GLEASON
FIELD DEPOSIT REFUND 10/27/2023 030292 100.00
011968 AMY GONZALEZ
CLEANING DEPOSIT REFUND 10/27/2023 030293 350.00
012002 JAMES GOOD
PARK RENTAL REFUND 10/27/2023 030294 75.00
004387 DANIEL HAAS
REIMBURSEMENT-DOT CERTIFICATIO 10/27/2023 030295 166.40 004596 HAWES RANCH & FARM SUPPLY
SUPPLIES 10/27/2023 030296 163.80
004811 HILLYARD, INC.
SUPPLIES 10/27/2023 030297 80.04
005172 J.F. SHEA CONSTRUCTION, INC.
MATERIALS 10/27/2023 030298 766.84
005525 KENNEDY-JENKS CONSULTANTS
PROFESSIONAL SERVICES 10/27/2023 030299 3,770.84
005855 LARRY'S LIGHTING & ELECTRIC
PERMIT FEES REFUND 10/27/2023 030300 55.50
005889 LAUNDRY WORLD
PROFESSIONAL SERVICES 10/27/2023 030301 3,165.82
006153 LOUCKS LANDSCAPE SUPPLY
MATERIALS 10/27/2023 030302 423.64
006229 LYRO PRINTING
PROFESSIONAL SERVICES 10/27/2023 030303 433.23
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
006643 MCMASTER-CARR SUPPLY CO.
SUPPLIES 10/27/2023 030304 939.99
007089 SUSAN MURDOCH
CLEANING DEPOSIT REFUND 10/27/2023 030305 350.00
007110 KITT MURRISON, PH.D.
PROFESSIONAL SERVICES 10/27/2023 030306 450.00
007394 NORTHERN CALIF. GLOVES
SUPPLIES 10/27/2023 030307 1,819.19
007493 ODP BUSINESS SOLUTIONS, LLC
OFFICE SUPPLIES 10/27/2023 030308 234.40
007617 PACE ENGINEERING, INC.
PROFESSIONAL SERVICES 10/27/2023 030309 420.00
007618 PACE SUPPLY CORP.
SUPPLIES 10/27/2023 030310 934.81
007630 PACIFIC GAS & ELECTRIC
UTILITIES 10/27/2023 030311 97,587.11
008498 RENTAL GUYS REDDING
EQUIPMENT RENTAL 10/27/2023 030312 531.57
009045 SAFEGUARD FIRE PROTECTION
PROFESSIONAL SERVICES 10/27/2023 030313 645.96
009618 SIGNARAMA
PROFESSIONAL SERVICES 10/27/2023 030314 209.70
009971 DAVID STARKEY
PER DIEM-TRAVEL 10/27/2023 030315 320.00
010030 STEPHENS ELECTRICAL INC.
PROFESSIONAL SERVICES 10/27/2023 030316 9,699.80
010237 SWRCB/DWOCP
02 CERT. RENEWAL-JONES 10/27/2023 030317 60.00
010237 SWRCB/DWOCP
Dl CERT. RENEWAL-MCCABE 10/27/2023 030318 70.00
NAME CHECK CHECK CHECK
VENDOR DESCRIPTION DATE NUMBER AMOUNT
010255 T ANDS DVBE, INC.
SUPPLIES 10/27/2023 030319 117.89
011866 UBEO WEST
MONTHLY LEASE 10/27/2023 030320 259.67
010756 USA BLUEBOOK
SUPPLIES 10/27/2023 030321 1,470.00
010874 VERIZON WIRELESS
PHONE CHARGES 10/27/2023 030322 3,565.69
011260 CHRISTY WHITE
REIMB. FOR MILEAGE-MEETING 10/27/2023 030323 186.02
179,518.13
AGENDA ITEM
!November 7, 2023 City Council Meetin~
To Be Presented By:
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From: Collin Bogener, City Attorney
Date: November 7, 2023
lsuBJECT
Approve the Amended Integrated Public Safety Memorandum of Understanding (MOU) between the City of Redding, the City of Anderson, the County of Shasta, and
SHASCOM
I RECOMMENDATION
The City Attorney recommends that the City Council:
Approve the Amended Integrated Public Safety Memorandum of Understanding (MOU) between the City of Redding, the City of Anderson, and the County of Shasta.
I FISCAL IMPACT
There will be no new impact to the General Fund from this MOU. The funding arrangement in this MOU is the same as in prior agreements as follows: City of Redding and Shasta County at 45 percent each and City of Anderson at 10 percent. SHASCOM contributes a share of the maintenance cost for the records management system.
ITEM 6.3 PAGE1 11/7/2023
I DISCUSSION and BACKGROUND
In 1991 the City Council approved entering into an agreement with the City of Redding and Shasta County to create Integrated Public Safety (JPS). The agreement was undertaken to consolidate the various records systems and other automated programs which each of the public safety agencies were using in effort to maximize the usefulness of the information, reduce redundancy, and make the best use of the agencies' personnel resources.
The entities have been operating under the IPS MOU since that time, with updates in 1997, 2002, 2004, 2010, and 2012. In 2017, a new MOU was executed to manage the replacement of the Records Management systems that outlined the management of the project as well as additional funding sources for the project. On August 16, 2022, the Anderson City Council approved a new IPS MOU, which contained a 5-year term.
Last month, Shasta County requested that the MOU be amended to provide a clarification to establish that the principal parties to the agreement are Anderson Police Department, Shasta County Sheriff, and the Redding Police Department. Any other city or county department that needs to access to IPS resources is considered a subscribing agency.
This has been the practice of the IPS Board for many years, but the County simply wanted clarification of this practice in the MOU.
The MOU was approved by the IPS Board at its October 2023 meeting. It has been approved by the Shasta County Board of Supervisors and is now going to the Redding City Council meeting, along with the Anderson City Council.
I ATTACHMENTS
Amended IPS MOU
ITEM 6.3 PAGE2 11/7/2023
OocuSign Envelope ID: E8999DFD-9737-4F9C-AAE7-F10CEA7E37F4 SEND FULLY EXECUTED ORIGINAL JO:
SHASTA CO. CLERK OF THE BOARD
1450 Court Street, Suite 3088
Redding, CA 96001
FIRST AMENDMENT TO THE MEMORANDUM OF UNDERSTAND~l:::::N~G~ -----....,,,
FOR OPERATION OF INTEGRATED PUBLIC SAFETY
This First Amendment is entered into between the County of Shasta ("County"), a political subdivision of the State of California, the City of Redding, a municipal corporation (REDDING), the City of Anderson, a municipal corporation (ANDERSON), and the Shasta Area Safety Communications Agency, a joint-powers agency (SHASCOM) hereinafter referred to as the Parties.
RECITALS
WHEREAS, the Parties have previously entered into a Memorandum of Understanding on October 5, 2022 to provide shared computerized law enforcement information and data to each of their agencies ("Original Agreement"); and
WHEREAS, the Parties desire to amend the Agreement to define and clarify Parties, responsibilities, apportionment of costs, and add electronic signature provisions; and WHEREAS, the Original Agreement and the First Amendment are collectively referred to as the "Agreement."
NOW, THEREFORE, the Agreement is amended as follows:
I. Section 3. DEFINITION of the Agreement is amended as of the effective date of the Agreement in its entirety to read as follows:
Section 3. DEFINITION:
3.1 IPS is the Integrated Public Safety System which shall operate as a multi-agency information technology task force, governed by the IPS Principal Participants, whose primary mission shall be to provide the Shasta County area law enforcement community with a centralized system for consolidated records management, mobile data delivery systems and a dedicated, secure technology infrastructure and to ensure the System is providing timely access to tactical and administrative investigative information relevant to the needs of law enforcement.
3.2 IPS Principal Participants:
3.2. l The Shasta County Sheriffs Office, an entity of Shasta County (COUNTY).
3.2.2 The Redding Police Department, an entity of the City of Redding, a municipal corporation (REDDING).
3.2.3 The Anderson Police Department, an entity of the City of Anderson, a municipal corporation (ANDERSON).
3.3 IPS Subscribing Agencies are any agency or city or county department not defined as an IPS Principal Participant, excluding the Shasta Area Safety Communications
FIRST AMENDMENT TO THE MOU FOR OPERATION OF IPS
C4 2756
DocuSign Envelope ID: E8999DFD-9737-4F9C-ME7-F10CEA7E37F4 Agency (SHASCOM), requiring access to the IPS and, if applicable, access the California Law Enforcement Telecommunications System (CLETS) and the National Crime Infonnation Center (NCIC). All IPS Subscribing Agencies shall execute a Memorandum of Understanding, Subscribing Agency Agreement, the subscriber agreements will be substantively in the form as Exhibit A attached hereto and remit annual Subscriber Agency fees to IPS.
II. Section 5. GOVERNING of the Agreement is amended as of the effective date of the Agreement in its entirety to read as follows:
Section 5. GOVERNING
5.1. The Parties agree IPS shall be governed by a three-member board consisting of the Redding Chief of Police, the Anderson Chief of Police, and the Sheriff of Shasta County, (IPS Directors) herein after referred to collectively as the IPS Board and individually as Law Enforcement Agency (LEA). SHASCOM is not a voting member of the IPS Board.
5.2. Each IPS Director may appoint an alternate who shall have the right to exercise the authority of said Director in their absence.
5.3. The IPS Directors, or their designees, shall meet at least twice per calendar year.
5.4. At the first meeting of every fiscal year, the IPS Directors may appoint a chairperson.
The chairmanship shall rotate annually among the members of the IPS Directors.
5.5. The IPS Directors shall be responsible for reporting back to their respective agencies.
5.6. Each Party to this agreement shall identify its management representatives who shall be responsible to coordinate the tasks and responsibilities outlined in this MOU on a daily basis with all other Parties. Each Party shall also provide the names and contact information of those management representatives to the IPS Project Supervisor.
5.7. IPS staff assigned to IPS functions shall meet as requested with the management representatives to share reports and infonnation with each other and report directly to the IPS Directors on all matters.
5.8. The IPS Directors are authorized on behalf of their respective governing authority to execute Memorandum of Understandings with Subscribing Agencies in the format consist of Exhibit A. The Memorandum of Understanding with Subscribing Agencies may be updated by the IPS Directors as needed to reflect current operational needs.
5.9. The IPS Directors are authorized on behalf of their respective governing authority to amend the IPS organizational structure as it pertains to IPS Personnel (Exhibit B) to meet the needs of the IPS task force within the limits afforded by their respective governing authority.
5.10. The IPS Directors are authorized on behalf of their respective governing authority to
FIRST AMENDMENT TO THE MOU FOR OPERATION OF IPS
C-2756
DocuSign Envelope ID. E8999DFD-9737-4F9C-AAE7-F10CEA7E37F4 approve any contract or agreement that directly relates to the operation of the system and falls within the scope of the approved IPS budget and its related amendments.
Any approval of said contracts or agreements must comply with REDDING's purchasing procedures.
5.11. All decisions to be made by the IPS Directors shall require a vote of the majority. m. Subsection 6.10 of Section 6. OPERATIONAL ROLES AND RESPONSIBILITES of the Agreement is added as of the effective date of the Agreement in its entirety to read as follows:
6.10 The City of Redding Chief Infonnation Officer, the Chief lnfonnation Officer for the County of Shasta, and the SHASCOM Director shall assist the IPS Principal Participants in a consulting capacity, as needed.
IV. Section 9. SUBSCRIBING AGENCIES of the Agreement is amended as of the effective date of the Agreement, in its entirety to read as follows:
Section 9. SUBSCRIBING AGENCIES
Representatives from Subscribing Agencies as defined in Subsection 3.3 of Section 3.
DEFINITIONS may be invited to attend the IPS Directors meetings. Subscribing Agencies shall not be voting members.
V. Section 11. APPORTIONMENT OF COSTS of the Agreement is amended as of the effective date of the Agreement, in its entirety to read as follows:
Section 11. APPORTIONMENT OF COSTS
11.1 SHASCOM shall be billed a portion of the maintenance and hardware costs as part of the annual IPS budget. SHASCOM shall contribute no less than $175,000 per year for the system maintenance costs. The annual contribution by SHASCOM is subject to adjustment and increase approved by the IPS Board. Any such increase shall be in accordance with cost increases incurred for the System and it's ancillary components and shall not exceed 10% of the current SHASCOM contribution to the IPS IT budget, the specifics of this contribution is defined in the annual fiscal !PS budget agreement.
11.2 The Parties Principal Participant, in the following proportions, shall share the annual fiscal year payment of IPS operating costs jointly offset by SHASCOM portion as defined in Section 11.1
11.2.1 COUNTY's share of the annual on-going costs for its Principal Participant, the Shasta County Sheriffs Office, shall be equal to forty-five percent (45%).
11.2.2 REDDING's share of the annual on-going costs for its Principal Participant, the Redding Police Department, shall be equal to forty- five percent (45%).
11.2.3 ANDERSON's share of the annual on-going costs for its Principal Participant, shall be equal to ten percent (10%).
FIRST AMENDMENT TO THE MOU FOR OPERATION OF IPS
C-2756
DocuSign Envelope ID; E8999DFD-9737-4F9C-AAE7-F10CEA7E37F4
11.3 The Parties apportioned shares shall be adjusted to compensate each Party according to their annual and actual budgeted personnel costs.
11.4 The individual agencies shall be responsible for budgeting their portion of the IPS expense in their respective agencies' budgets as approved by their governing boards.
VI. Section 13. USER FEES of the Agreement is amended as of the effective date of the Agreement in its entirety to read as follows:
Section 13. USER FEES
In addition to the Apportionment of Costs described in Section 11 of this MOU, Subscribing Agencies/Departments shall pay annual User Fees.
13.1 The IPS Directors shall collect a cost recovery user fee and/or project cost from the Subscribing Agencies.
13.2 User fees imposed on Subscribing Agencies shall include administrative costs as well as a negotiated percentage of operational costs and shall not exceed the actual expenses as approved in the budget.
13.3 User fees shall be presented to the IPS Directors at the annual budget meeting and require a majority vote for approval.
VII. Section 22. COUNTERPARTS/ELECTRONIC, FACSIMILE, AND PDF SIGNATURES of the Agreement is added as of the effective date of the Agreement in its entirety to read as follows:
SECTION 22. COUNTERPARTS/ELECTRONIC, FACSIMILE, AND PDF SIGNATURES This agreement may be executed in any number of counterparts, each of which will be an original, but all of which together will constitute one instrument. Each Party of this agreement agrees to the use of electronic signatures, such as digital signatures that meet the requirements of the California Uniform Electronic Transactions Act (("CUETA") Cal. Civ. Code §§ 1633.1 to 1633.17), for executing this agreement. The Parties further agree that the electronic signatures of the Parties included in this agreement are intended to authenticate this writing and to have the same force and effect as manual signatures. Electronic signature means an electronic sound, symbol, or process attached to or logically associated with an electronic record and executed or adopted by a person with the intent to sign the electronic record pursuant to the CUET A as amended from time to time.
The CUET A authorizes use of an electronic signature for transactions and contracts among Parties in California, including a government agency. Digital signature means an electronic identifier, created by computer, intended by the party using it to have the same force and effect as the use of a manual signature, and shall be reasonably relied upon by the Parties. For purposes of this section, a digital signature is a type of "electronic signature" as defined in subdivision (h) of Section 1633.2 of the Civil Code. Facsimile signatures or signatures transmitted via pdf document shall be treated as originals for all purposes.
VIII. REAFFIRMATION
FIRST AMENDMENT TO THE MOU FOR OPERATION OF IPS
C-2756
DocuSign Envelope ID: E8999OFD-9737-4F9C-AAE7-F10CEA7E37F4 In all other respects, the Agreement, as amended, and any attachments, remains in full force and effect.
IX. ENTIRE AGREEMENT
The Agreement, as amended, and any attachments, constitute the entire understanding between Parties.
X. EFFECTIVE DATE
Unless otherwise provided, this First Amendment shall be deemed effective as of the last date it is signed by both Parties.
IN WITNESS WHEREOF, the Parties to this MOU through their duly authorized representatives have executed this MOU on the days and dates set out below and certify that they have read, understood, and agreed to the tenns and conditions of this MOU as set forth herein.
ATTEST: CITY OF REDDING
By: ___________ _ By: ___________ _
Sharlene Tipton, City Clerk Date: Michael Dacquisto, Mayor Date:
APPROVED AS TO FORM:
Barry De Walt
City Attorney
By: __________ _
Barry E. DeWalt, City Attorney Date:
ATTEST: CITY OF ANDERSON
By: _ _ ___________ _
Christy White, Deputy City Clerk Date:
APPROVED AS TO FORM:
Collin Bogener
City Attorney
By:. ____________ _
Collin Bogener, City Attorney Date:
By: _____________ _
Mike Gallagher, Mayor Date:
CONTINUED ON NEXT PAGE
FIRST AMENDMENT TO THE MOU FOR OPERATION OF IPS
C-2756
DocuSign Envelope ID: EB999DFD-9737-4F9C-AAE7-F10CEA7E37F4 ATTEST:
DAVID J. RICKERT
of Supervisors
APPROVED AS TO FORM:
Gretchen Stuhr
Interim County Counsel Risk Management
C DocuSJoned by-
~;;~~ l 0/23/2023 [ 9:05 AM PDT ~ :~l•;~St,I,\, 10/19/2023 I 5: l l PM PDT Date: Jame,.~11t1 Tci:r. 01i!ft'itm,;m1t""" n11-••-----D-a-te-: - Interim County Counsel Risk Management Analyst III
SHASTA AREA SAFETY COMMUNICATIONS AGENCY
By: Date:
Chris -------------- Smymos, SHASCOM Director ------------ FIRST AMENDMENT TO THE MOU FOR OPERA TrON OF IPS
C-2756
DocuSign Envelope ID: E8999DFD-9737-4F9C-ME7-F10CEA7E37F4 Exhibit A
MEMORANDUM OF UNDERSTANDING
Subscribing Agency Agreement
This Memorandum of Understanding (MOU) is made and entered into this ____ d.ay of ____ , ____ .., by and between the Redding Police Department, the Anderson Police Department, and the Shasta County Sheriff's Office, collectively known as "IPS" (Integrated Public Safety) and ____________ _, hereinafter referred to as Subscribing Agency. IPS and Subscribing Agency are herein after referred to as the Parties to this MOU. IPS maintains a centralized computer data system relevant to the needs of law and justice agencies in the Shasta County region hereinafter referred to as the IPSS (Integrated Public Safety Systems). The JPS Directors consist of the Redding and Anderson Police Chiefs and the Shasta County Sheriff. Subscribing Agency wishes to access the !PSS.
l. PURPOSE
The purpose of this MOU is to establish the terms, conditions, and responsibilities of JPS and Subscribing Agency, thereby authorizing Subscribing Agency to access the IPSS, and if applicable, access the California Law Enforcement Telecommunications System (CLETS), and the National Crime Information Center (NCIC). Additionally, this MOU shall define responsibility for control of information accessed through the IPSS.
2. SHARED INFORMATION
Not all information maintained within IPSS shall be available to all employees of the Parties.
Sensitive information contained within IPSS shall be restricted on a "need to know" basis as detennined by the originating agency, to perform assigned duties.
Subscribing Agencies do not have the authority to disseminate shared data stored in IPSS. Data obtained from IPSS shall only be disseminated by the Agency of Record. All information requests, including but not limited to; total calls for service, case information, copies ofrecords,jail activity, etc. shall be sent directly from the requesting party to the Agency of Record. The Agency of Record is the agency that created the relevant data through its normal business practices and procedures.
No Subscribing Agency shall give out information for another Subscribing Agency without the written consent from that Agency. This includes Public Records Requests or involved and/or associated cases unless otherwise required by law.
Abuse of access of information within the IPSS could result in termination of user access and/or subscribing agency access to IPSS and will be reviewed and decided by a majority vote of the IPS Directors.
3. MANAGEMENT CONTROLS
Subscribing Agency shall assume responsibility of its employees who are granted access to the IPSS. Each Subscribing Agency shall maintain physical and operational control of any equipment and/or software used to gain access to the IPSS.
Each Subscribing Agency shall ensure that all employees of Subscribing Agency who are granted access to the IPSS continue to meet the requirements of Penal Code sections 11105 and 13300, which identify persons allowed to access criminal history infonnation and the purposes for said access.
Each Subscribing Agency shall maintain information and/or access security such that it is compliant with all security controls required by the most recent version of the Criminal Justice Page I
DocuSign Envelope ID: E8999DFD-9737-4F9C-AAE7•F10CEA7E37F4 lnfonnation Services (CHS) Security Policy and the CLETS Policies, Practices, and Procedures (PP&P).
4, SECURITY CLEARANCE
Subscribing Agency agrees to maintain accurate records of those employees who have been granted access to the IPSS. Those records shall include a copy of the Security Clearance notice signed by each employee who is granted access to the IPSS.
Within six months of employment or assignment of any staff accessing the IPSS, the Subscribing Agency shall have staff pass a proficiency test for CLETS/NCIC policies and Regulations by completing the required training and the appropriate CLETS/NCIC Telecommunications Proficiency Examination published by the CA Department of Justice (DOJ). Proficiency retesting shall be required biannually thereafter as required by CLETS PP&P. Copies of Signed agreements and/or proficiency tests shall be made available for inspection and review by IPS within three business days of a written request to Subscribing Agency,
5. RESPONSIBILITIES
Subscribing Agency is responsible for their own computer hardware and related peripheral accessories and is responsible for ensuring their hardware meets IPS requirements for access to the IPSS. Subscribing Agency is responsible for maintaining their own network infrastructure and for ensuring their network can communicate with the IPSS network for system access.
JPS is responsible for providing customer and technical support for the IPSS software applications and databases that are being accessed by Subscribing Agency.
6. SYSTEM ADMINISTRATION
Subscribing Agency authorizing an employee to gain access to the IPSS shall submit a written and signed request from its respective Agency Head or designee. Submission of such a request shall not occur until the employee has executed the Security Clearance notice. Once an employee has been provided access to the IPSS, the Subscribing Agency shall be responsible for enforcing the rules and regulations governing the use of information obtained through the IPSS. Should an employee's status change, either through re-assignment or termination, it shall be the Subscribing Agency's responsibility to immediately notify IPSS in writing to prevent the employee from having further access to the IPSS.
7. COMPENSATION SCHEDULE
Each year IPS shall establish a fee schedule (User Fees) for the access, support, and security of the IPSS.
The User Fees will be divided into three tiers of access:
Tier I - CLETS/NCIC Only Access
Access to CLETS/NCIC via the IPS provided interface. No access to Computer Aided Dispatch (CAD), mobile CAD, Records Management System (RMS), or jail data.
Tier 2 - Read Only Access
Access to CLETS/NCIC via the IPS provided interface. Read-only access to CAD, mobile CAD, Page2
DocuSign Envelope ID: E8999DFD-9737 -4F9C-ME7-F1 0CEA7E37F4 RMS, and jail data for research and operational purposes as needed based on the job functions of the subscribing agency.
Tier 3 - Full Access
Access to CLETS/NCIC via the IPS provided interface. Full read and write access to the CAD, mobile CAD, RMS, and jail modules as needed based on the job functions of the subscribing agency.
IPS shall prepare and submit to each Subscribing Agency the Board approved User Fees prior to the start of the fiscal year. In accordance with the established fee schedule, invoicing shall be done bi-annually, based upon actual number of users the Subscribing Agency had accessing the IPSS each month. The total users for each Subscribing Agency will be audited monthly by IPS to be used for billing purposes. The Subscribing Agency can request a copy of that audit at any given time, by submitting a request in writing to JPS. No amendment to this MOU is necessary to update the annual fee schedule.
The Subscribing Agency shall remit to IPS, upon receipt of invoice, applicable fees according to the approved annual fee schedule. The establishment and implementation of a cost-recovery fee schedule does not imply all costs incurred by JPS, on the behalf of Subscribing Agency, are included in the current Fee Schedule calculation. All invoices are payable within 30 days ofreceipt.
The fee schedule shall establish a 'per-user' fee based on level of access requested and specific and identifiable costs incurred by lPS in order to provide and maintain access and security for the system. System Users are defined as individual employees of the Parties who have been granted access to the IPSS. Identified costs, which directly benefit all System Users shall be divided by the total number of System Users to detennine the 'per-user' fee. The fee schedule may include a one-time network connection and setup fee for access to IPS and may include an annual fee to maintain ongoing connectivity to the system. The fee schedule may include hourly rate(s) for any non-standard support services contracted with JPS and performed for the sole benefit of the Subscribing Agency by JPS personnel.
Requests from a Subscribing Agency for programming and/or other non-standard support is subject to a review process and final approval by the IPS Directors.
IPS shall bill Subscribing Agency for network connection, programming and/or non-standard support services within 30 days of connection or service. Subscribing Agency shall remit payment upon receipt of the invoice, not to exceed 30 days.
Shasta Area Safety Communications Agency {SHASCOM), and Shasta lnteragency Narcotics Task Force (SINTF) are exempt from the 'per-user' fee requirement.
8. VIOLATION OF MOU
In the event a Subscribing Agency fails to exercise Management Controls as outlined in Section 3 or Security Clearance as outlined in Section 4, IPS may deny the Subscribing Agency further access to the IPSS. In the event Subscribing Agency fails to remit the invoiced amount to JPS, JPS may deny the Subscribing Agency further access to the IPSS. This action shall occur only after a meeting of the JPS Directors, and the Subscribing Agency has been conducted and a majority vote by the IPS Directors affinning tennination of the Subscribing Agency access.
9. TERM OF MOU
DocuSlgn Envelope ID: E8999DFD-9737-4F9C-AAE7-F10CEA7E37F4 This Memorandum of Understanding shall become effective as of the date of the last signatory and shall remain in full force and effect until it is terminated by written notice. In the event an individual Subscribing Agency no longer desires access to the IPSS, that Subscribing Agency shall provide a written notice to IPS. Upon such notice, employees of the withdrawing agency will no longer be allowed access to the IPSS three (3) business days after written notice is received by the JPS Project Supervisor and the withdrawing agency shall cease to be a part of the IPSS.
In the event the Subscribing Agency signatory authority and/or the IPS Board of Directors signatory Authority changes during the term of this agreement, this MOU shall remain active, and all authority and agreement shall be inherited by the successor.
10. INDEMNIFICATION
It is agreed that each of the Parties shall, for its sole negligence, or sole willful conduct, mutually save and hold each of the other parties and each of the other parties' appointed and elected officials, its agents, representatives, volunteers, and employees harmless from all costs, expenses, losses, and damages, including death or damages to property caused by any act or neglect of such party, its agents, representatives, volunteers, officials, or employees in the performance of this agreement.
(SIGNATURE PAGE FOLLOWSI
Page4
OocuSign Envelope ID: E8999DFD-9737-4F9C·AAE7•F10CEA7E37F4 Subscribing Agency:
Tier l Number of Users:
Tier 2 Number of Users;
Tier 3 Number of Users:
Effective Date:
(Signatory), (Title} Date
IPS BOARD OF DIRECTORS:
Chief of Police Date
Redding Police Department
Chief of Police Date
Anderson Police Department
Sheriff-Coroner Date
Shasta County Sheriff's Office
Page S
AGENDA ITEM
!November 7, 2023 City Council Meetin~
Jenni ......__,_~-aniel, Director of Operations and
Administration
To: Honorable Mayor and Members of the Anderson City Council From: Jon Poletski, Interim City Manager
Through: Jennifer McDaniel, Director of Operations and Administration Date: November 7, 2023
I SUBJECT
Approval of Ordinance No. 857 (second reading) General Plan Amendment 23-01 and Rezone 23-02 - Shady Ln - APN 052-340-067, Anderson Seventh Day Adventist Church as introduced on October 17, 2023 (first reading).
I RECOMMENDATION
Enact Ordinance No. 857 (second reading) General Plan Amendment 23-01 and Rezone 23-02 - Shady Ln • APN 052-340-067, Anderson Seventh Day Adventist Church as introduced on October 17, 2023 (first reading).
I ENVIRONMENTAL DETERMINATION
The proposed project, a General Plan Amendment and Rezone have been determined to be exempt from the California Environmental Quality Act (CEQA) pursuant to the General Rule CEQA Guidelines Section 15061(b)(3) where it can be seen with certainty that there is no possibility that the proposed rezone may have a significant effect on the environment.
ITEM 6.8 PAGE1 11/7/2023
I CURRENT GENERAL PLAN & ZONING
The project site is currently zoned Medium Density Residential (R2), and the existing General Plan land use designation is Medium Density Residential (MOR). The site is surrounded by a variety of uses including high density residences (apartments), medium density residential, and single-family residences and commercial businesses.
Surrounding land uses and zoning are as follows:
North: Public Uses; PSP (Public/Semi-Public) zoning district.
South: Apartments; Medium Density Residential (R2) zoning district.
East: Single-family Residential (Rl) zoning district.
West: Commercial; C-1 (General Commercial) zoning district.
I SITE PLAN
The project site is a 2.35-acre undeveloped parcel, created as a result of a recently approved
two-parcel land division processed at the request of the Anderson Seventh Day Adventist Church (Book 39 record maps, page 99). The project site is resultant parcel 2 and the existing Seventh Day Adventist Church is located on Parcel 1. This project is proposed to support future high-density residential development in support of General Plan Housing Element Goal HE.2: Provide adequate sites to meet future housing needs and Anderson's share of regional housing needs.
! PROPOSED GENERAL PLAN AMENDMENT 23-01 & REZONE 23-02
General Plan:
From Section 2.4.6 of the Anderson General Plan, the High Density Residential Land Use Designation allows for 20 to 40 dwelling units per gross acre. The types of units intended for this category are apartments, townhouses or other multiple-unit structures. The use of the buildings and land shall be primarily residential with accessory uses permitted, such as recreational facilities. Flexibility and innovation and Mixed Use should be encouraged for projects of this type. High Density Residential includes housing types such as duplexes, triplexes, four-plexes, townhouses, and similar multiple-unit residential development. Section 2.5 of the General Plan Land Use Element addresses "Land Use Element Objective, Policies, and Implementation Programs" policies relevant to this project include:
GP-1 Sufficient areas will provide for each type of land use to permit full development needed to meet the demands of population growth and economic advancement.
GP-8 Infill development of the vacant areas within the City Limits shall be encouraged in order for the City to provide services to its residents more efficiently.
ITEM 6.8 PAGE2 11/7/2023
RP-4 In areas where different land uses abut one another, promote land use compatibility by using buffering techniques, landscaping, setbacks, screening and sound walls.
RP-5The community should encourage compact, well-defined living areas and discourage residential sprawl
Zone District:
Anderson Municipal Code Section 17.12.040 and Section 17.12.050 provide the City's building site requirements in the R3 (High Density Residential) zoning district. The minimum lot area in the R3 zoning district is 6,000 square feet for interior lots, and 7,000 square feet for corner lots. The maximum height of dwellings is forty feet, and twenty feet for accessory buildings. All proposed development project for this site will be required to meet density, height, yard, requirements as well as other applicable Anderson Municipal Code requirements pertaining to multi-family residential construction, including approval by the Design Review Committee.
I AGENCY COMMENTS AND PUBLIC NOTICE
Comments on the subject General Plan Amendment and Rezone were received from the City of Anderson Public Works Department as an advisory notice indicating the location of sewer services and preference that future sewer services to the project site be provided from Shady Lane. The notice has been provided to the applicant and the current owner of the property.
A 10-day public hearing notice of the subject project was published in the RecordSearchlight and mailed notices were posted in accordance with noticing requirements provided in AMC Section 17.54.040 - Zoning Amendments. No public comments on the project have been received by the Planning Department at the time of this report.
I FINDINGS
General Plan Amendment:
The proposed General Plan Amendment from Medium Density Residential (MOR) to High Density Residential (HDR) will not be detrimental or injurious to the general welfare of the city as it is consistent with the variety of residential development adjacent to and in the general vicinity of the project site. City utilities are available to serve the high-density development and no potential traffic impacts have been identified as a result of this amendment.
Rezone:
The proposed Rezone from Medium Density Residential (R2) to High Density Residential (R3) will not be detrimental or injurious to the general welfare of the city as the proposed (R3) zone district will not create a conflict with adjacent existing commercial or multi-family residential uses. Other (R3) zoned parcels are located in ITEM 6.8 PAGE3 11/7/2023
the near vicinity of the project site and the proposed use of the parcel will not conflict with the surrounding uses.
Environmental Determination:
Rezone has been determined to be categorically exempt from the California Environmental Quality Act (CEQA) pursuant to CEQA Guidelines Section pursuant to CEQA Guidelines Section the General Rule CEQA Guidelines Section 15061(b)(3) where it can be seen with certainty that there is no possibility that the proposed rezone may have a significant effect on the environment.
I ATTACHMENTS
A) Ordinance No 857 (RZ 23-02)
ITEM 6.8 PAGE4 11/7/2023
DRAFT ORDINANCE NO. 857
AN ORDINANCE OF THE CITY COUNCIL OF THE CITY OF ANDERSON TO AMEND
THE ZONING ORDINANCE OF THE CITY OF ANDERSON, A PORTION OF THE ZONING PLAN MAP (REZONE 23-02)
The City Council of The City of Anderson Does Ordain as Follows:
SECTION 1. The following described real property is hereby rezoned from the Medium Density Residential (R2) zone district to the High Density Residential (R3) zone district (as shown on Exhibit A, attached hereto, and incorporated herein).
Assessor's Parcel Number 052-340-067-000 The proposed project area totals 2.35 acres of undeveloped land located adjacent to the west side of Shady Lane and approximately 300-feet south of the intersection of Balls Ferry Road and Shady Lane.
SECTION 2. The City of Anderson finds that this Ordinance is not a "project" according to the definition set forth in the California Environmental Quality Act ("CEQA"), and, pursuant to CEQA Guidelines sections 15061(b)(3) (there is no possibility the activity in question may have a significant effect on the environment), the adoption of this ordinance is therefore not subject to the provisions requiring environmental review.
SECTION 3. The City Clerk shall certify the adoption of this ordinance and shall cause it to be posted and/or published in accordance with the law.
The foregoing ordinance was introduced at a regular meeting of the City Council of the City of Anderson held on October 17, 2023 (first reading), and second reading at a regular meeting of the City Council of the City of Anderson held on November 7, 2023, by the following vote
AYES:
NOES:
ABSENT:
ABSTAIN:
MIKE GALLAGHER, Mayor
ATTEST:
CHRISTY WHITE, City Clerk
EXHIBIT A to ORDINANCE NO. 857
Assessor's Parcel Number 052-340-067-000
AGENDA ITEM
November 7, 2023, City Council Meeting
To Be Presented By:
heeler, Acting Finance Director
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
Prom: Cindy Wheeler, Acting Finance Director
Date: November 7, 2023
I SUBJECT
Implementation of a new payroll processing and timekeeping system.
I RECOMMENDATION
The Acting Finance Director recommends that the City Council:
Approve the implementation of ADP, Inc. payroll and timekeeping system to streamline all payroll-related processes and increase payroll accuracy and manpower within the Finance Department. Additionally, this will allow for the reduction of paper used and stored at City Hall.
!FISCAL IMPACT
The fiscal impact would be $12,984.00.
I DISCUSSION and BACKGROUND
Currently the payroll process begins with each employee filling out a paper timecard which is turned in to the Finance Department where payroll is manually entered into our current financial software by one Account Clerk; taking an average of 5 hours to complete. The remainder of the process after calculation reports are printed, verified, and approved, checks & direct deposit stubs are printed and manually stuffed into envelopes for distribution. The entire procedure from the point of receiving all timecards in the Finance ITEM 8.5 PAGE1 11/7/2023
Department takes roughly 6 hours. The cost at this point between personnel time and materials is $384.36/pay period for a total of $10,060.54 annually.
The other benefit the city would be receiving through the ADP service is the quarterly payroll tax reporting and processing of W-2s. This task is completed by the same Account Clerk, totaling 8 additional hours for each reporting period. This portion of the payroll process of personnel time plus materials cost comes to $2,562.40 annually.
The total for the entire in-house payroll procedure currently costs the city $12,622.94 per year. Investing in the recommended ADP payroll service has an annual cost of $12,984.00, with promotional savings of $3,872.00 resulting in the first two years costing only $9,112.00.
Although the Finance Department is currently short-staffed, even when fully staffed the 196 hours that could be redirected to more of the day-to-day operations is even more valuable than the cost of the ADP payroll service. In addition, this would reduce the need for overtime in the department.
What will change for City employees not working at the Anderson Police Department is that they will track their time by filling in an electronic timecard within the ADP system using a unique password-protected log-in as well as time-off requests. Supervisors will have visibility to his or her team's time logs and can approve or deny timecards and time off requests.
Anderson Police Department employees will continue using the scheduling and timekeeping software they are currently using, and once all department timecards have been verified and approved, the Administrative Services Manager will export a CSV file from the program and send it to the key payroll contact in the Finance Department.
A management employee of the Finance department will upload the CSV file sent from the Administrative Services Manager at the Police department as well as verify all remaining city employee payrolls have been approved. Once all is believed to be true and correct, ADP will take over the remainder of the payroll process. Employees receiving paychecks via direct deposit will continue to do so, and those who do not will have the option to receive a printed check mailed to the Finance office, a pay card loaded each payday, or switch to direct deposit. The pay card is an optional feature for all employees.
Once approved, the implementation process will begin immediately to allow for data imports of current information as well as unlimited payroll simulations to be performed, ensuring complete accuracy by the go-live date.
A demonstration was given by two other payroll service providers: ABC Workforce & Tyler Technologies/ExecuTime. The choice to go with ADP was based not only on need and efficiency but also on cost. ABC Workforce came in with a higher quote and more manual processing than ADP. ExecuTime, although less expensive annually, could not provide the payroll services sought out by the city.
ITEM 8.5 PAGE2 11/7/2023
I ATTACHMENTS
1. Investment Summary /Sales quote
ITEM 8.5 PAGE3 11/7/2023
Investment Summary
Quote Number 02-2023-491964 1
Company Information
City of Anderson
1887 Howard St
Anderson. CA 96007-3340
United States
.L
80 Total
Employees
ADP Sales Associate
Austin Siege
District Manager
[email protected]
(610) 486-5675
$0.00
lmplemenlalion
Costs
Expiration
10/29/2023
Executive Contact
Cindy Wheeler
[email protected]
(530) 378-6626
$12,984.00 ($3,872.00)
Total Annual
lnvestmen1
Total Annual Savings during
promotional penocl. See Terms
** The Implementation Costs and Total Annual Investment listed out on this Investment Summary are estimates based on the services. frequencies. recurring rates and pay counts outlined on the sales order and are shown for illustrative purposes only.
These numbers are not binding amounts and shall not become incorporated into or made a part of any sales order or services agreement governing the services contemplated therein.
Data Privacy Appendix
This Data Privacy Appendix is a data processing agreement under Applicable Law and supplements the Agreement, including Sections 4 (Confidentiality), 9.3 (Data Security) and 10.1 (Data Security Breach/Notification), between ADP, Inc. and Client. Capitalize .. d .. le.rm. s lhro .. u. .. g h. out. thi.s D .. at·a·. P .. riv .. acy .. Appendix .n ... ot. d .. efined in the Agreement are defined in the ADP Privacy Glossary at www.adp.com/-/media/adp/grivacy/pdf/glossary en.pdf.
PART I • GENERAL
1. Client Obligations. Client shall only provide ADP
with Client Personal Data that: (a) is required to perform the Services; (b) has been collected in accordance with Applicable Law; and (c) Client has authority to provide under Applicable Law.
2. ADP Obligations. ADP. as a Data Processor (or
equivalent term under Applicable Law), will comply with Applicable Law for Processing Client Personal Data
pursuant to the Agreement. ADP will not: (a) •sell" or
"share" Client Personal Data; (b) retain, use, disclose or otherwise Process Client Personal Data outside of its
direct business relationship with Client or for any
commercial or other purpose other than the business
purposes specified in the agreement(s) between Client
and ADP, except as permitted by Applicable Law; or {c)
combine Client Personal Data with personal data that
ADP receives from, or on behalf of, other persons, or
collects from its own interaction with a consumer, except as permitted under Applicable Law. ADP shall have the
right to Process Client Personal Data in order to comply with its legal obligations (e.g., compliance with sanctlon laws) or in order to prevent, detect or investigate fraud.
ADP employees and contingent workers are authorized
to Process Client Personal Data to the extent necessary to provide Services and as permitted under the
Agreement and by Applicable Law.
3. De-identification and Aggregation. In addition to
any rights granted to ADP in Section 4 of the Agreement to use aggregated and anonymized data, ADP will not
attempt to, and will not, re-identify any Client Personal Data.
4. Transfers to Subprocessors. ADP may transfer
Client Personal Data to ADP Subprocessors and Third
Party Subprocessors located outside of the country in
which Client Personal Data was collected. Third Party
Subprocessors are bound by written contracts with
ADP that impose data protection terms that are not less protective than those imposed by this Data Privacy
Appendix.
An up-to-date list of ADP Subprocessors and Third Party Subprocessors, including locations, is accessible at
https:1/thebridge.adp.com/workforce-now/gdpr(m/media/
634. Such list may be updated from time to time.
20221202
PROPRIETARY AND CONFIDENTIAL TO ADP, INC.
5. Compliance Obligations. ADP will notify Client if
ADP makes a determination that it can no longer meet its Processing obligations under Applicable Law.
Client may, upon providing written notice to ADP, take
reasonable steps to stop and remediate unauthorized
Processing of Client Personal Data.
6. Client Instructions. When receiving a Client
instruction regarding the Processing of Personal Data,
ADP will notify Client if ADP considers such instruction violates Applicable Law; however, ADP is not obliged to and will not perform a legal examination with respect to a Client instruction.
7. Assistance. ADP wilt assist Client with its data
privacy obligations where required under Applicable Law, including assisttng Client in responding to and
addressing Client Employee individual rights requests
and complaints and providing Client with relevant
information for conducting data protection impact or risk assessments. ADP reserves the right to charge for such
assistance rendered. If ADP receives an individual rights request or complaint directly from a Client Employee,
ADP shall promptly forward the Client Employee request
to Client.
8. Client Audit, ADP will answer questions asked by
Client regarding the Processing of Client Personal Data by ADP. In the event Client reasonably considers that the answers provided by ADP justify further analysis, ADP
will, in agreement with Client, either:
(a) provide security materials known as ADP's trust
package {which includes security policy and standards
overview, password summary, resiliency program
summary, disaster recovery program overview, data
center and hosting service summary and a third party
risk management executive summary), that details ADP's
business processes and procedures for the Processing of Client Personal Data; or,
(b) make the facilities it uses to Process Client Personal Data available for an audit by a qualified independent
third-party assessor reasonably acceptable to ADP,
bound by confidentiality obligations satisfactory to ADP and engaged by Client. Client will provide a copy of the audit report to ADP's Global Chief Privacy Officer which will be ADP Confidential
Page2
Information. Audits shall be conducted no more than
once per year during the term of the Agreement during
regular business hours and will be subject to (i) a written request submitted to ADP at least 45 days in advance of the proposed audit date; (ii) a detailed written audit plan reviewed and approved in advance by ADP's security
organization; and (iii) ADP's on-site security policies.
Such audits will take place only in the presence of a
representative of ADP's global security office, ADP's
global data privacy & governance team, or such person
designated by the appropriate ADP representative. The
audits shall not be permitted to disrupt ADP's Processing activities or compromise the security and confidentiality of Personal Data pertaining to other ADP Clients. ADP
will charge Client a reasonable fee for such audit.
PART II - GDPR
9. Scope. This Part II applies solely with respect to Client Personal Data subject to Regulation (EU) 2016/679 on
the protection of natural persons with regard to the
processing of Personal Data and on the free movement
of such data ("General Data Protection Regulations~ or
"GDPR"). With respect to ADP's processing of Client
Personal Data subject to GDPR, the ADP Privacy Code,
located at https:l/www.adp.com/-Jmedia/adp/privacyJpdf/ bcrpc en.pdL governs. ADP has obtained EU
authorization of its ADP Privacy Code.
10. International Transfers. For transfers outside of the EEA, Switzerland and United Kingdom, the ADP Privacy
Code serves as the legal basis for the data transfer to an ADP Group Company or between ADP and an ADP
Subprocessor, which Client acknowledges and accepts.
ADP shall enter into appropriate contractual agreements, such as standard contractual
20221202
PROPRIETARY AND CONFIDENTIAL TO ADP, INC.
clauses, or rely upon any other lawful transfer
mechanism prior to transferring Client Personal Data to a Third Party Subprocessor or to an ADP company when
the ADP Privacy Code does not apply.
11. Additional Subprocessor Obligations. Within 30 days of a written update (including electronic notice) by ADP to Client adding a new Subprocessor, Client may object to
such new Subprocessor by providing written notice to
ADP alleging objective justifiable grounds that such
Subprocessor is unable to protect Client Personal Data. If the parties cannot reach a mutually acceptable solution, ADP shall, at its option, either: (a) not allow the
Subprocessor to access Client Personal Data; or (b)
allow Client to terminate the relevant Services in
accordance with the terms of the Agreement.
12. ADP Privacy Code EU Authorization. ADP will make
commercially reasonable efforts to maintain the EU
authorization of its ADP Privacy Code for the duration of the Agreement and will promptly notify Client of any
subsequent material changes in the EU authorization of
its ADP Privacy Code.
PART Ill • Miscellaneous
13. Order of Precedence. In the event of a conflict
between the Agreement, this Data Privacy Appendix, the
ADP Privacy Code and Applicable Law, then the conflict
will be resolved by giving effect to such in the following order of precedence: (a) Applicable Law; (b) the ADP
Privacy Code; (c) this Data Privacy Appendix; and (d) the Agreement.
14. Scope. This Data Privacy Appendix provides no
additional rights to a Client Employee that are not already provided under the Applicable Law to which the Client
Employee is subject.
Page3
Sales Order
Quote Number 02-2023-491964 1
Company Information
City of Anderson
1887 Howard St
Anderson. CA 96007-3340
United States
Recurring Fees and Considerations
Number of Employees: 80 on City of Anderson
@ Per Processing
Workforce Now Payroll Solutions
• Enhanced Payroll
• Essential Time
Employment and Income Verification
• Employment Verification
Additional Jurisdiction (if applicable)
Courier Delivery (if applicable)
~ Annual Processing
Year End Forms. W2s or 1099s
@ Total Annual Investment
Workforce Now Services
~ Other Cons1derat1ons
-..,. Implementation
@ Total Other Considerations
Implementation and Setup
Implementation Discount Value
Estimated Total Net Implementation
Count
80 80
Count
80 Mjn
2+
Min
Executive Contact
Cindy Wheeler
cwheeler@ci .anderson. ca. us
(530) 378-6626
Base
$100.00
Base
Rate
$4.80
Bi-Weekly
$484.00
$0.00
An:nual
$12,584.00
$0.00
$11 .00/month
$20.00 per delivery
Rale
$5.00
Annual
$400.00
Total Annual
$12,984.00
Setup
Total Setup
$4,000.00
($4,000.00)
$0.00
Page4
Sales Order
Quote Number 02-2023-491964 1
Important Project and Billing Information
Billing for Payroll Processing Services. HCM and any module bundled into the single per employee per processing fee for payroll, is billed immediately following the client's first payroll processing. The billing count is based on the number of pays submitted during each processing period. therefore total bilhng may fluctuate.
Unemployment Claims in excess of the 10% claims cap will be billed at $36.00 per claim. The fee for optional hearing representation is $155.00 per appearance. Attorney representation required in certain states and is subject to change (currently: AZ, DE, KY, MO, NC. SC. SD. and WV). Representation fee not to exceed actual attorney fees. Optional service available through non-ADP affiliated attorneys. Attorneys will be retained on behalf of client for limited purpose of representing Client at the hearing. No referral fee applies. No attorney-client relationship exists or will be formed between ADP and Client.
Client intends to use Direct Deposit and Paycard and be fully paperless for Employee Pay Statements using ADP Self Service and/or ADP Mobile App to view all Pay and W2 information. By doing so. ADP will not charge a delivery fee unless something is in fact delivered.
Promotion
Client will receive 8 months free spread over 2 years, applying to months 7-10 and 19-22 from each product/controls billing start date (also referred to as the Promotional Period). Items specifically excluded: implementation, tax and banking (including reverse wire), jurisdiction. year-end. maintenance and professional Services fees. Actual promotional value may vary based on a number of reasons, including but not limited to: start date, number of processings and employees paid during the promotional month(s). Services added after the date hereof are not eligible for the Promo. As noted in Section 12.4 of MSA, Client is subject to an Early Termination Fee in the event Client terminates ADP services prior to the expiration of the Initial Term.
Other
ADP's Fees for Service will be debited directly out of client's bank account of their choosing seven (7) days from invoice date. ADP will send all invoices to cwheeler ci.anderson.ca.us
Summary
Estimated Annual Net Investment: $12,984.00 Total Net Implementation: $0.00 Estimated Annual Net Investment
during promotional period:
$9.112.00
The ADP Services Listed on this Sales Order are provided at the prices set forth herein and in accordance with the ADP Master Services Agreement (or other similar agreement governing ADP's services). which shall include any appendix. exhibit. addendum, schedule or other similar document attached thereto or accompanying this Sales Order. By signing below you are acknowledging and agreeing to such terms and conditlons and to the listed prices.
ADP, Inc. Client: City of Anderson
Signature: Signature:
Name: Name:
Title: Title:
Date: Date:
Sales Order
Quote Number 02-2023-491964 1
Workforce Now Included Services
Enhanced Payroll
• Tax Filing Service
• Payment Services
• Reports Library and Custom Report Writer
• Wage Garnishment Processing
• New Hire Reporting
• General Ledger Solution
• Intelligent Employee Case Resolution
• Online Reports and Pay Statements
• Wisely Pay Card Services
Essential Time
• Time Collection
• PTO Management & Reporting
• Request & Approval Workflows
Employment Verification
• Commercial Employment and Income
Verifications
• Social Services Verifications
• Workers Compensat1on Verifications
• Employee and Manager Self Service
• Paid Time Off Accruals
• ADP Portal with Customized Content
• Access to Mobile Apps
• Employee Discount Program
• Group Term Life Auto Calculation
• Conversational Virtual Assistant
• Rule Based Calculations
• Scheduling
• Mobile Access
• Client access to Electronic Reports and Tools
• Immigration Verifications
Thank you for your consideration
Page6
AGENDA ITEM
November 7, 2023, City Council Meeting
To Be Presented By:
Jenni~ Mc niel, Director
& Administration
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From:
Date:
Jennifer McDaniel, Director of Operations & Administration November 7, 2023
I SUBJECT
Implementation of a different permit processing system with Solar App +, Code Enforcement & online payment processing
I RECOMMENDATION
The Director of Operations and Administration recommends that the City Council:
Consider the approval of implementing Cloudpermit, building software that meets the requirements set forth by Senate Bill 379 and the Code Enforcement Software. !FISCAL IMPACT
The fiscal impact for the program for year 1 would be $32,038. This would be funded in full by the recently awarded CalApp grant obtained by the Development Services Department.
Year 2 & 3 fiscal impact would be $15,038 per year.
I DISCUSSION and BACKGROUND
The Development Services Department has been awarded the CalApp grant in the amount of $40,000. This funding is to be used to comply with Senate Bill 379, a state-automated solar permitting system.
ITEM 8.7 PAGE1 11/7/2023
By September 30, 2024, jurisdictions must integrate their permit software with the States Solar App+; which will instantly review and grant approval for residential roof mount solar submittals, up to 38.4 Kw, and requires the ability to accept payments online.
The State of California saw a need to streamline solar processing, due to many jurisdictions taking several weeks to review and issue residential roof mount solar permits. Even with the popularity of solar, this action is completed by our staff within 72 business hours. Not only will Cloudpermit streamline our solar permit processing, it will also streamline all building permit applications and the code enforcement piece.
Our current permit program, iWorQ, does not integrate seamlessly with the state's automated solar permitting system. If we continue to keep iWorQ, it's expected to take staff much more time to issue permits. Presently, iWorQ's ineffective software leaves staff on the phone with customer service for several hours a month trying to resolve issues within the program. This software is restrictive and adds unnecessary processing time.
In order to bring our current program, iWorQ, into compliance with state regulations, our new contract would be $12,800. This program is extremely limited to the file size of plans, the number of permit documents (letters) you can have in the program, and no ability to review or approve the plan effectively. Nothing in iWorQ is customizable, you must call in and have your requests updated through many departments in iWorQ, which can take weeks to complete.
After extensive research by staff, Cloudpermit was found to be the best option, not only for integrating with the newly imposed state regulations but also for processing all building permits and code enforcement cases.
Cloudpermit accepts all file sizes, an unlimited amount of permit documents (Letters), and the entire program is customizable to our needs.
A huge advantage of Cloud permit is in the efficiency of how fewer actions are needed from staff on processing permits. Currently, for most over-the-counter permits (like Re-Roofs), iWorQ system requires staff to touch the permit an average of 10 times, whereas Cloud permit would reduce this to just 3 times.
Cloudpermit will also streamline the process for building applications from the customer's perspective. This system will populate the required forms for each specific project as the applicant answers questions in the Building Permit Application. iWorQ does not have this as an option, and this is where much staff time is spent gathering information from applicants. Applicants will be able to go to www.cLanderson.ca.us to apply for building permits as they are currently doing with our current program.
I ATTACHMENTS
1. Cloudpermit Contract
ITEM 8.7 PAGE2 11/7/2023
Cloud permit
11911 Freedom Drive, Ste. 720
Reston, Virginia 20190
United States
Ship To
Jennifer McDaniel
Anderson
1887 Howard Street
Anderson, California 96007
United States
530-378-6626
[email protected]
Subscription
Product
Building Annual Total
Code Enforcement Annual Total
Subscription Total:
Year1
Order Form
Order#: Q-01766-4
Customer#: CUST-0022532
Date: 10/25/2023
Sales Person:
Sales Person Email:
Jake Wolff
[email protected]
Delivery Method: E-Mail
BIii To
Anderson
1887 Howard Street
Anderson, California 96007
United States
Year2
USO 12,384 USO 12,384
USD 2,654 USD 2,654
USO 15,038 USD 15,038
Year3
USD 12,384
USO 2,654
USO 15,038
Subscription start date will be the contract signature date unless otherwise stated in the Terms & Condition section.
Service
Description Annual Total
Data Import USO 7,000
Implementation Fee USD 10,000
Service Total: USD 17,000
Customer Total First Year: l._ ______ u_s_D_32_,_o_38_,I
ORDER FORM for Anderson/ Order#Q-01766-4
Terms and Conditions
Term: 3 years, billable annually
Invoicing: Subscription invoice to be sent after contract is signed and then annually.
First invoice (50%) for implementation fee is due upon implementation start (M1) and the second invoice {50%) for implementation fee to be sent after Go Live Milestone {M2) is approved.
Payment Term: Net 30 days from Invoice Date
Subscription Start Date: Date of contract signature
All stated prices are exclusive of any taxes.
Customer Name:
Signature:
Printed Name of Person Signing:
Title:
Date:
Accounts Payable Email:
By signing here, the Customer agrees to this Order Form, the Software Service Agreement and any other appendices and documentation expressly referenced in this Order Form, the Software Service Agreement and/or any amendments (together the "Agreemenr).
The individual signing this Agreement represents and warrants that he or she has the right and authority to bind the Customer.
Cloudpermit
Signature:
Jarkko Turtiainen
Printed Name of Person Signing:
SVP North America
Title:
Date:
Cloudpermit Software
Service Agreement
CONFIDENTIAL
THIS AGREEMENT is made by and between the "Customer" as identified in the Order Form and Cloudpermit, Inc. a Delaware corporation with its office at 11911 Freedom Drive, Suite 720, Reston, VA, 20190 ("Cloudpermit").
1. DEFINITIONS
1.1 Unless the context otherwise requires, the following words and expressions have the following meanings:
"Affiliate" means any entity that directly or indirectly controls, is controlled by, or is under common control with the subject entity. Such control, for purposes of this definition, means direct or indirect ownership or control by agreement or otherwise of more than 50% of the voting interests of the subject entity. "Agreement" means the Order Form, this Software Service Agreement and all appendices and other documents expressly referenced in the Order Form, this Software Service Agreement and/or any amendments.
"Business Day" means any day other than a Saturday, Sunday or federal holiday in the USA.
"Cloudpermit Software" means the Cloudpermit platform, software applications and any third-party software applications that Cloudpermit will provide access to for the Customer and End Users.
"Confidential Information" means any information made available by one Party to the other, in any form or medium, that is proprietary or confidential to a Party or its affiliates, or their respective customers, suppliers, or other business partners, including, without limitation, all documentation, products, tools, materials, inventions, discoveries, works of authorship, programs, derivative works, information, designs, know-how, trade secrets, configurations, technical information, data, ideas, methods, processes, schematics and business plans, whether or not specifically identified as confidential.
"Customer Data" means information, data and other content that is provided by the Customer to Cloudpermit, but does not include any content that is publicly available, currently or in the future.
"Customer Systems" means the Customer's information technology infrastructure including computers, software, databases, database management systems, other electronic systems and networks, whether operated directly by the Customer or through the use of third-party services that enable the Customer and/or End Users to access the Cloudpermit Software.
SA v6 - Aug 2023 1
CONFIDENTIAL
"End User" means any individual that Customer has designated or authorized to use the Cloudpermit Software. End Users may include, for example, residents, employees, consultants, contractors of Customer, and representatives of any other third parties with which Customer transacts business.
"End User Data" means the information, data and other content that is provided by an End User to Cloudpermit but does not include any content that is publicly available, currently or in the future.
"Fees" means the annual subscription fees, implementation fees and any other fees stated in the Order Form, any Appendix or otherwise agreed to in writing by the Parties.
"Force Majeure Event" means any event or occurrence which is outside the reasonable control of a Party and which is not attributable to any act or failure to take commercially reasonable preventative action by that Party, including war, act of foreign enemies, hostilities (regardless of whether war is declared), terrorist activities, strikes, lockouts, pandemics, interruption or failure of electricity, and Acts of God (including fire, flood, earthquake, hurricane, or other natural disaster), but not including insolvency or Jack of funds.
"General Communications Network" means communication networks owned, and/or leased, and operated by internet service providers which allow individuals to access the internet and access the Cloudpermit Software via the internet. "Identifier" means a user name and password that associates an End User with the End User's account or user ID in the Cloudpermit Software. "Implementation" means the initial configuration and implementation of the Cloudpermit Software for the Customer.
"Party" and "Parties" mean Cloudpermit and its affiliates and/or the Customer.
2. CLOUDPERMIT'S RESPONSIBILITIES
2.1 Cloudpermit will make the Cloudpermit Software available to the Customer pursuant to this Agreement and the additional terms and conditions for use of the Cloudpermit Software by End Users available at www.cloudpermit.com as may be amended from time to time.
2.2 Cloudpermit will use all commercially reasonable efforts to keep the Cloudpermit Software available for use except for downtime or degradation for maintenance, installation, change, data security risk, requirements of law, regulation by government authorities, a Force Majeure Event, or any other circumstances beyond Cloudpermit's reasonable control.
3. CUSTOMER'S RESPONSIBILITES
3.1 The Customer and each End User is required to maintain an internet connection at its own cost to access the Cloudpermit Software.
3.2 The Cloudpermit Software may be used by the Customer and End Users only in accordance with this Agreement and the additional terms and conditions for use by End Users available at www.cloudpermit.com as may be amended from time to time.
SA v6 - Aug 2023 2
CONFIDENTIAL
3.3 The Customer will at all times maintain and operate in good repair the Customer Systems and take all actions necessary to secure Customer Data, End User Data and access credentials, including Identifiers. Cloudpermit is not liable or responsible for any delay or performance failure caused by the Customer or Customer Systems.
3.4 If the Customer becomes aware of any actual or threatened harmful activity with respect to Customer Data, End User Data, Identifiers, unauthorized access to the Cloudpermit Software, unauthorized access to or acquisition of Customer Data or End User Data, or any other breach related to the Cloudpermit Software in any way, the Customer will immediately notify Cloudpermit and the Parties will each mitigate any negative effects of such harmful activity or breach.
3.5 The Customer will promptly, upon request by Cloudpermit, provide all necessary information and guidelines to Cloudpermit for providing the Cloudpermit Software to the Customer and its End Users. The Customer ensures that the information and guidelines it provides are correct.
3.6 The Customer shall not, and shall not authorize any other person to, access or use the Cloudpermit Software except as expressly permitted by this Agreement and the Customer shall not: (a) copy, modify or create derivative works or improvements to the Cloudpermit Software; (b) rent, lease, lend, sell, sublicense, assign, distribute, publish, transfer or otherwise make available the Cloudpermit Software to any person, including on or in connection with any time-sharing, service bureau, software as a service, cloud or other technology or service; (c) reverse engineer, disassemble, decompile, decode, adapt or otherwise attempt to derive or gain access to the source code of the Cloudpermit Software; (d) access or use the Cloudpermit Software other than by an authorized End User through the use of his or her own then-valid access credentials; (e) input, upload, transmit or otherwise provide to or through the Cloudpermit Software any content, information or materials that are unlawful or injurious, or contain, transmit or activate any harmful code or content; or (f) access or use the Cloudpermit Software for purposes of competitive analysis of the Cloudpermit Software, or for the development, provision or use of a competing software service or product.
4. SERVICE FEES AND PAYMENT TERMS
4.1 In consideration of Cloudpermit's performance of its obligations under this Agreement, the Customer will pay all Fees in the manner provided for in the Order Form.
4.2 All Fees and other amounts payable by Customer stated in the Order Form and in this Agreement are exclusive of applicable taxes.
4.3 All amounts payable to Cloudpermit will be paid by the Customer in full without any set-off, recoupment, counterclaim, deduction, debit or withholding for any reason.
4.4 Any sum not paid by the Customer when due will bear interest from the due date until paid at a rate of 1.5% per month, compounded monthly, or the maximum rate permitted by law.
4.5 Invoices will be sent to the Customer as provided in the Order Form.
SA v6 - Aug 2023 3
CONFIDENTIAL
5. CHANGES
5.1 Cloudpermit reserves the right to make any changes to the Cloudpermit Software that it deems necessary or useful to: (a) maintain or enhance the quality or delivery of the Cloudpermit Software to its customers, the competitive strength of or market for the Cloudpermit Software, or the cost efficiency or performance of the Cloudpermit Software; or (b) to comply with applicable law.
5.2 Cloudpermit will make reasonable efforts to notify the Customer of any changes in advance. If such advance notice is not reasonably possible, then Cloudpermit will notify Customer after the change without delay.
6. DATA, PRIVACY AND PROTECTION
6.1 The Parties will each comply with all applicable privacy and data protection laws in force during this Agreement.
6.2 Cloudpermit warrants that it will employ security measures in accordance with Cloudpermit's privacy policy available at www.cloudpermit.com as may be amended from time to time. Neither Party is responsible for the data security of the General Communications Network or any disturbance in the General Communications Network.
6.3 Customer has and will retain sole responsibility for: (a) all Customer Data and End User Data, including its content and use; (b) all information, instruction and materials provided by or on behalf of the Customer or any End User in connection with the Cloudpermit Software; (c) the Customer Systems; (d) the security and use of Customer's and End Users' access credentials, including Identifiers; and (e) all access to and use of the Cloudpermit Software directly or indirectly by or through the Customer Systems or any End Users' systems.
6.4 Customer will employ all physical, administrative, and technical controls, screening, and security procedures and other safeguards necessary to: (a) securely administer the distribution and use of Identifiers or other credentials to access the Cloudpermit Software; and (b) control the content and use of Customer Data and End User Data, including uploading or other use or processing of Customer Data and End User Data, whether or not related to the Cloudpermit Software.
6.5 Cloudpermit warrants that it will not cause or permit any Customer Data to be collected, reproduced, stored or otherwise processed in any manner or for any purpose other than performance of Cloudpermit's obligations stated in this Agreement.
6.6 As between Customer and Cloudpermit, Customer is and shall remain the sole and exclusive owner of all right, title, and interest in and to Customer Data. Customer hereby grants to Cloudpermit a license to use and process Customer Data as necessary for performance of the Cloudpermit's obligations stated in this Agreement and the Customer's and End User's use of the Cloudpermit Software.
6. 7 The Cloud permit Software may provide external links to other sites on the internet, as a convenience for the Customer and End Users. Cloudpermit is not responsible for such linked destinations and such links do not imply Cloudpermit's association, affiliation, sponsorship or endorsement of the content, operation or security of any such linked destination.
SA v6 - Aug 2023 4
CONFIDENTIAL
6.8 Cloudpermit will provide a mechanism for the Customer to download and export Customer Data and End User Data during the Term of the Agreement to the fullest extent commercially reasonable in light of the circumstances that required such data recovery and restoration.
6.9 Upon termination of the Order Form for any reason, whether or not Customer has retrieved Customer Data, Cloudpermit reserves the right to permanently and definitively delete the Customer Data held in the Services thirty (30) days following termination of the Order Form.
7. IDENTIFIERS AND THEIR USE
7 .1 Cloudpermit will deliver to the Customer identifiers necessary for access to and use of the Cloudpermit Software in accordance with this Agreement and any additional terms and conditions for use by End Users.
7.2 The Customer will be responsible for the use of the Cloudpermit Software by its employees, agents and End Users, including use of Identifiers. The Customer will notify Cloudpermit without delay if an Identifier has been disclosed to a third party or if the Customer suspects that an Identifier has been disclosed or otherwise misused.
7.3 Upon request by Cloudpermit, the Customer will change any Identifier for access to the Cloudpermit Software.
7.4 Cloudpermit may change any Customer Identifier and wilt provide prompt notice to Customer of such change.
8. DATA LOCATION
8.1 The servers used by Cloudpermit to provide the Cloudpermit Software and all data regarding the Cloudpermit Software will be hosted in the USA. 9, WARRANTIES
9.1 Each Party represents and warrants to the other Party that it has all required powers and capacity to enter into this Agreement, to grant the rights and license granted under this Agreement, and to perform its obligations under this Agreement.
9.2 The Customer represents, warrants and covenants to Cloudpermit that the Customer owns or otherwise has, and will have, the necessary rights and consents in and relating to the Customer Data and End User Data so that, as received by Cloudpermit and processed in accordance with this Agreement, neither Party and will infringe, misappropriate or otherwise violate any intellectual property rights, or any privacy or other rights of any third party or violate any applicable law.
9.3 EXCEPT FOR THE EXPRESS WARRANTIES STATED IN THIS AGREEMENT, ALL
SOFTWARE, SERVICES AND MATERIALS PROVIDED BY ONE PARTY TO THE OTHER HEREUNDER ARE PROVIDED "AS IS". CLOUDPERMIT HEREBY DISCLAIMS ALL
CONDITIONS AND WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY OR
OTHERWISE UNDER THIS AGREEMENT, AND CLOUDPERMIT SPECIFICALLY DISCLAIMS
ALL IMPLIED CONDITIONS AND WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE, AND ALL WARRANTIES ARISING FROM COURSE OF DEALING, USAGE OR TRADE PRACTICE.
SA v6 - Aug 2023 5
CONFIDENTIAL
10. OWNERSHIP AND INTELLECTUAL PROPERTY RIGHTS
10.1 The Customer acknowledges that, as between the Customer and Cloudpermit, Cloudpermit owns all right, title, and interest, including all intellectual property rights, in and to the Cloudpermit Software. The Customer and End Users are granted only a limited right to use the Cloudpermit Software during the term of this Agreement in accordance with this Agreement and the additional terms and conditions for use by End Users.
10.2 If the Customer or any of its employees or contractors sends or transmits any communications or materials to Cloudpermit by mail, email, telephone, or otherwise, suggesting or recommending changes to the Cloudpermit Software, including without limitation, new features or functionality relating thereto, or any comments, questions, suggestions, or the like, Cloudpermit is free to use and incorporate such feedback irrespective of any other obligation or limitation between the Parties governing such feedback for any purpose whatsoever and without any requirement to pay any compensation to the Customer or to any other person or entity.
10.3 If any part of the Cloudpermit Software is, or in Cloudpermit's reasonable opinion is likely to be, claimed to infringe, misappropriate or otherwise violate any third party intellectual property right, or if the Customer's or any End User's use of the Services is enjoined or threatened to be enjoined, Cloudpermit may, at its option and sole cost and expense: (a) obtain the right for the Customer to continue to use the Cloudpermit Software materially as contemplated by this Agreement; (b) modify or replace the Cloudpermit Software, in whole or in part, to seek to make the Cloudpermit Software (as so modified or replaced) non-infringing, while providing materially equivalent features and functionality, in which case such modifications or replacements will constitute the Cloudpermit Software as provided under this Agreement; or (c) by written notice provided sixty (60) calendar days in advance to the Customer to terminate this Agreement with respect to all or part of the Cloudpermit Software (providing a pro-rated refund for any prepaid access to the Cloudpermit Software) and require the Customer to immediately cease any use of the Cloudpermit Software or any specified part or feature thereof.
11. INDEMNITY
11.1 Each party will indemnify, defend and hold harmless the other Party and its officers, directors, employees, agents, successors, subcontractors, attorneys, affiliates and assigns from and against any and all losses, damages, liabilities, claims, penalties, fines, costs or expenses of whatever kind, including legal fees, disbursements and charges, and the cost of enforcing any right to indemnification and the cost of pursuing any insurance providers incurred by a Party to the extent arising out of or relating to:
(a) any claim by a third party that a Party's acts or omissions with respect to the Cloudpermit Software infringes a third party's intellectual property right, provided that the foregoing obligation does not apply to any claim arising out of or relating to any access to or use of the Cloudpermit Software in a manner contrary to this Agreement or the additional terms and conditions for use by End Users available at www.cloudpermit.com as may be amended from time to time, or contrary to any instructions provided by Cloudpermit regarding use of the Cloud permit Software or use of the Cloudpermit Software in combination with any hardware, system, software, network or other materials or service not provided or authorized by Cloudpermit; (b) the indemnifying Party's breach of this Agreement; or (c) the indemnifying Party's negligence or willful misconduct in connection with this Agreement.
SA v6 - Aug 2023 6
CONFIDENTIAL
12. LIMITATION OF LIABILITY
12.1 IN NO EVENT WILL EITHER PARTY BE LIABLE TO THE OTHER PARTY IN CONTRACT,
TORT OR OTHERWISE, WHATEVER THE CAUSE THEREOF, FOR ANY LOSS OF PROFIT,
BUSINESS, REVENUE OR GOODWILL, DAMAGES CAUSED BY DELAYS, OR A FAILURE
TO REALIZE EXPECTED SAVINGS, OR ANY INDIRECT, SPECIAL, CONSEQUENTIAL,
INCIDENTAL, EXEMPLARY, AGGRAVATED OR PUNITIVE COST, DAMAGES OR EXPENSE
OF ANY KIND, HOWSOEVER ARISING UNDER OR IN CONNECTION WITH THIS
AGREEMENT OR THE CLOUDPERMIT SOFTWARE, WHETHER OR NOT SUCH DAMAGES,
COSTS, LOSSES OR EXPENSES COULD REASONABLY BE FORESEEN OR WHETHER OR NOT THEIR LIKELIHOOD HAS BEEN DISCLOSED.
12.2 NEITHER PARTY SHALL BE LIABLE FOR THE DESTRUCTION, LOSS OR ALTERATION OF
THE OTHER PARTY'S DATA OR DATA FILES, NOR FOR ANY DAMAGES AND EXPENSES INCURRED AS A RESULT, INCLUDING EXPENSES INVOLVED IN THE RECONSTRUCTION OF DATA FILES.
12.3 IN NO EVENT SHALL EITHER PARTY'S AGGREGATE LIABILITY ARISING OUT OF OR
RELATED TO THIS AGREEMENT, WHETHER ARISING OUT OF OR RELATED TO BREACH
OF CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, EXCEED THE
AGGREGATE AMOUNT PAID OR PAYABLE TO CLOUDPERMIT PURSUANT TO THIS AGREEMENT DURING THE SIX (6) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM. MAXIMUM LIABILITY SHALL BE SIX (6) MONTHS OF THE ANNUAL SUBSCRIPTION FEE.
12.4 NOTWITHSTANDING THIS SECTION 12, NOTHING IN THIS AGREEMENT SHALL LIMIT
EITHER PARTY'S LIABILITY FOR DELIBERATE BREACH, DELIBERATE DEFAULT, WILLFUL MISCONDUCT OR GROSS NEGLIGENCE.
13. CONFIDENTIALITY
13.1 In connection with this Agreement each Party (as the "Disclosing Party") may disclose or make available Confidential Information to the other Party (as the "Receiving Party"). "Confidential Information" means information in any form or medium (whether oral, written, electronic or other) that the Disclosing Party considers confidential or proprietary, including, information consisting of, or relating to, the Disclosing Party's technology, trade secrets, know-how, business operations, plans, strategies, customers and pricing and information with respect to which the Disclosing Party has contractual or other confidentiality obligations, in each case whether or not marked, designated or otherwise identified as "confidential".
13.2 Confidential Information shall not include any data or information: (i) that, at the time of disclosure, is in or, after disclosure, becomes part of the public domain, through no act or failure on the part of the Receiving Party; (ii) that, prior to disclosure by the Disclosing Party, was already tn the possession of the Receiving Party, as evidenced by written records kept by the Receiving Party in the ordinary course of its business, or as evidenced by proof of actual prior use by the Receiving Party; (iii) that was independently developed by the Receiving Party, by persons having no direct or indirect access to the Disclosing Party's Confidential Information provided that the Receiving Party prov,des clear and convincing evidence of such independent development; or (iv) which, subsequent to disclosure, is obtained from a third person:
(A) who is lawfully in possession of the such information; (B) who is not in violation of any contractual, legal, or fiduciary obligation to either Party, as applicable, with respect SA v6 - Aug 2023 7
CONFIDENTIAL
to such information; and (C) who does not prohibit either Party from disclosing such information to others; (v) is further disclosed with the prior written consent of the Disclosing Party, but only to the extent of such consent; or (vi) is a disclosure required by state or federal open records laws or a disclosure ordered by a court or similar adjudicator or authority.
13.3 Each Party will, and will cause its employees, agents and contractors to hold Confidential Information of the other Party in confidence, and will use the same degree of care by instruction, agreement or otherwise, to maintain the confidentiality of the other Party's Confidential Information that it uses to maintain the confidentiality of its own Confidential Information, and with at least a reasonable degree of care commensurate with the nature and importance of such Confidential Information. Each Party agrees not to make use of Confidential Information other than for the exercise of rights or the performance of obligations under this Agreement, and not to release, disclose, communicate or make it available to any third person other than employees, agents and contractors of any Party or third party who reasonably need to know it in connection with the exercise of rights or the performance of obligations under this Agreement.
13.4 In the event that a Party receives a request to disclose all or any part of the Confidential Information under the terms of a valid and effective subpoena or order issued by a court of competent jurisdiction or by a governmental authority, such Party will: (i) immediately notify the other Party of the existence, terms and circumstances surrounding such a request; (ii) consult with the other Party on the advisability of taking legally available steps to resist or narrow such request; and (iii) if disclosure of such Confidential Information is required, exercise reasonable efforts to obtain an order or other reliable assurance that confidential treatment will be accorded to such portion of the disclosed Confidential Information which the other Party so designates.
13.5 Each Party acknowledges and agrees that any unauthorized use or disclosure by it of any of the other Party's Confidential Information, in whole or part, will cause irreparable damage to the Disclosing Party, that monetary damages would be an inadequate remedy and that the amount of such damages would be extremely difficult to measure. The Receiving Party agrees that the Disclosing Party shall be entitled to seek temporary and permanent injunctive relief to restrain the Receiving Party from any unauthorized disclosure or use. Nothing in this Agreement shall be construed as preventing the Disclosing Party from pursuing any and all remedies available to it for a breach or threatened breach of this Agreement, including the recovery of monetary damages from the Receiving Party.
13.6 Cloudpermit is entitled to identify the Customer as a user or former user of the Cloudpermit Software without violating any confidentiality obligation.
14. TERM AND TERMINATION
14.1 This Agreement commences on the date of its execution by the Customer and will continue in effect for the term stated in the Order Form unless terminated earlier under any of this Agreement's express provisions.
14.2 Either Party may terminate this Agreement by giving written notice to the other Party upon the occurrence of any of the following: (a) the other Party defaults with respect to a material obligation under this Agreement and does not remedy that default within SA v6 - Aug 2023 8
CONFIDENTIAL
ten (10) Business Days after receiving written notice of the default; or (b) the other Party: (i) makes a general assignment for the benefit of its creditors; (ii) has issued against it a bankruptcy order or otherwise becomes subject to any involuntary proceeding under any domestic or foreign bankruptcy law; or (iii) commences or institutes any application, proceeding or other action under any law relating to bankruptcy, insolvency, winding-up, reorganization, administration, plan of arrangement, relief or protection of debtors, compromise of debts or similar laws.
Termination related to such assignment or bankruptcy will not result in any penalties or liability to either Party.
14.3 Upon the expiration or termination of this Agreement, except as expressly otherwise provided in this Agreement: (a) all rights, grants of rights, licenses, consents and authorizations by either Party to the other will immediately terminate; (b) notwithstanding anything to the contrary in this Agreement, with respect to Confidential Information then in its possession or control: (i) the Receiving Party may retain the Disclosing Party's Confidential Information in its then current state and solely to the extent and for so long as required by applicable law, (ii) Cloudpermit may retain Customer Data in its backups, archives and disaster recovery systems until such Customer Data is deleted in the ordinary course of its business, (iii) all information described in this Agreement will remain subject to all confidentiality, security and other applicable requirements of this Agreement; and (c) Cloudpermit may disable all Customer and End User access to the Cloudpermit Software.
14.4 Termination or expiration of this Agreement will be without prejudice to any rights, remedies or obligations of the Parties accrued under this Agreement prior to termination or expiration.
15. FORCE MAJEURE
15.1 Neither Party will be liable for failure to fulfill, or for delay in fulfilling, its obligations required hereunder due to a Force Majeure Event,
15.2 The Party whose performance under this Agreement is prevented or delayed by a Force Majeure Event will advise the other Party by notice in writing of the occurrence of the Force Majeure Event as soon as possible and shall do all things reasonably possible to mitigate any loss being caused to the other Party by reason of the Force Majeure Event, and will notify the other Party of the termination of the Force Majeure Event.
16. NOTICES
16.1 Every notice or other communication between the Parties will be deemed to have been given and made if in writing and if served by personal delivery upon the Party for whom it is intended, when sent by registered or certified mail, return receipt requested, or by a national courier service, or if sent by email (receipt of which is confirmed) to the Customer's and Cloudpermit's contact persons as stated in the Order form.
16.2 Any such notification will be deemed to have been delivered: (a) upon receipt, if delivered personally; (b) on the next Business Day, if sent by national courier service for next business day delivery or if sent by email and (c) in five Business Days if sent by mail when the actual time of receipt is not otherwise shown by the postal system.
Any correctly addressed notice or last known address of the other Party that is reasonably relied upon that is refused, unclaimed, or undeliverable because of an act SA v6 - Aug 2023 9
CONFIDENTIAL
or omission of the Party to be notified shall be deemed effective as of the first date that said notice was refused, unclaimed, or deemed undeliverable by the postal authorities by mail, through messenger or commercial express delivery services.
17. ASSIGNMENT
17 .1 Neither Party may assign or transfer this Agreement or any right under this Agreement without the prior written consent of the other Party, except to an Affiliate or successor in interest by merger, acquisition or reorganization.
18, AMENDMENTS AND WAIVERS
18.1 No amendment to this Agreement will be valid or binding unless it is made in writing and executed by all Parties. No waiver of any breach of any provision of this Agreement will be effective or binding unless made in writing and signed by the Party purporting to give any waiver and, unless otherwise provided, any waiver will be limited to the specific breach waived.
19. SEVERABILITY
19.1 If a provision of this Agreement is or becomes invalid, ineffective or unenforceable, the validity, effectiveness or enforceability of the remaining provisions will remain unaffected. The Parties will negotiate in good faith to replace the invalid, ineffective or unenforceable provision immediately with a valid, effective or enforceable provision which comes as close as possible to the spirit and purpose of the provision to be replaced.
20. APPLICABLE LAW AND DISPUTES
20.1 This Agreement is governed by the laws of the state in which the Customer is located excluding any conflict of law rule or principle of such laws that might refer such interpretation or enforcement to the laws of another jurisdiction. Each Party submits to the jurisdiction of the applicable court(s) in such location with respect to any matter arising under this Agreement.
21. CONTINUING TO PERFORM
21.1 Except in the event of termination of this Agreement pursuant to its terms, during a dispute or notice or cure period, Cloudpermit will continue to fulfill all its obligations under this Agreement, and Customer will continue to make all payments required by the Agreement.
22. ENTIRE AGREEMENT
22.1 This Agreement is the complete agreement between the Parties concerning the subject matter of this Agreement and replaces any prior oral or written communications between the Parties. There are no conditions, understandings, agreements, representations, or warranties expressed or implied, that are not specified in this Agreement including, without limitation, the Order Form. In the event and to the extent of an inconsistency or conflict between any of the terms of this Agreement, including its appendices, and any other documents incorporated herein by reference, SA v6 - Aug 2023 10
CONFIDENTIAL
the conflict or inconsistency shall be resolved by gIvIng those provIs1ons and documents the following order of descending precedence: (1) the Order Form; (2) this Software Service Agreement; (3) any Appendices; (4) any other document referenced by this Agreement or agreed to by the Parties, unless it expressly and specifically replaces or modifies any of the prior documents, in whole or in part.
23. RELATIONSHIP
23.1 The Parties are independent contractors and no other relationship is intended. Nothing herein shall be deemed to constitute either Party as an agent, representative or employee of the other Party, or both Parties as joint venturers or partners for any purpose. Neither Party shall act in a manner that expresses or implies a relationship other than that of independent contractor. Each Party shall act solely as an independent contractor and shall not be responsible for the acts or omissions of the other Party. Neither Party will have the authority or right to represent nor obligate the other Party in any way except as expressly authorized by this Agreement.
24. NO THIRD PARTY BENEFICIARIES
24.1 This Agreement is for the sole benefit of the Parties and their successors and assigns and nothing herein, express or implied, is intended to or shall confer upon any other person any legal or equitable right, benefit or remedy. End Users may benefit from their use of the Cloudpermit Software, but End Users' relationships to the Parties are not defined by this Agreement because they are defined solely: (a) to Cloudpermit by the terms and conditions for use by End Users available at www.cloudpermit.com as may be amended from time to time; and (b) to the Customer by separate agreement(s), if any, between the Customer and End Users.
SA v6 - Aug 2023 11
CONFIDENTIAL
25. EXECUTION
25. 1 This Agreement must be executed simultaneously in two separate places: (1) on the Order Form; and (2) in the signature block below (both documents must be signed by the Customer before execution of this Agreement is complete). They may be executed in two or more identical counterparts, or by way of facsimile and electronic transmission without any further exchange of documents containing original signatures, each of which when executed by a Party will be deemed an original and such counterparts together will constitute one and the same Agreement.
CUSTOMER NAME:
Signature:
Printed Name of
Person Signing:
Title:
Date:
D I confirm that I have received and read all applicable product descriptions.
By signing here, the Customer agrees to the Order Form, this Software Service Agreement and any other appendices and documentation expressly referenced in the Order Form, this Software Service Agreement and/or any amendments (together the "Agreement").
The individual signing this Agreement represents and warrants that he or she has the right and authority to bind the Customer.
Signature:
Printed Name of
Person Signing:
Title:
Date:
SA v6 - Aug 2023
Cloud permit
Jarkko Turtiainen
SVP North America
12 1
Cloudpermit ®
CLOUDPERMIT
IMPLEMENTATION MODEL
Cloudpermit ®
TABLE OF CONTENTS
CLOUDPERMIT IMPLEMENTATION DESCRIPTION ............................................................................... 2 IMPLEMENTATION TIMELINE ............................................................................................................ 2 IMPLEMENTATION MODEL ............................................................................................................... 3 Kickoff .......................................................................................................................................... 3 Workshop .................................................................................................................................... 3 Configuration .............................................................................................................................. 3 Training & Testing ....................................................................................................................... 3 Go Live ......................................................................................................................................... 3 MILESTONES & ACCEPTANCE CRITERIA .......................................................................................... 4 CHANGE MANAGEMENT .................................................................................................................. 4 ADDITIONAL SERVICES COST ........................................................................................................... 4
CLOUDPERMIT IMPLEMENTATION DESCRIPTION
The implementation model, described herein, details the proven model used to implement the various products offered by Ctoudpermit for a new public-facing solution for the Customer. This is accomplished through a five-stage implementation process: Stage 1 - Kickoff, Stage 2 - Workshop, Stage 3 - Configuration, Stage 4 - Training & Testing and Stage S - Go Live.
The product(s) to be implemented is identified on the approved order form and is inclusive of the functionality that is identified in the product specific documentation.
Any services not listed on the Order Form are considered out of scope and can only be added through an agreed upon change order.
IMPLEMENTATION TIMELINE
The implementation schedule for Cloudpermit is mutually agreed upon prior to the Kickoff meeting and documented with a project plan. Any modifications or extensions to the project plan will be requested through the customer's authorized representative and evaluated by Cloudpermit Head of Professional Services for review and discussion. If this modification or extension is granted, Cloud permit will provide a change order to be signed by the Customer. Cloudpermit standard implementation timeline is detailed below.
Building Department
By-Law or Code Enforcement
Planning Department
2 Week Week week week week Week Week week week Week Week Week Week Week Week Week week week week 1 2 3 4 5 6 7 8 9 W U U U M U ~ U IB ~
S•6weeks
4-SWeelts
1·10wuks
Cloudpermit ®
To manage this timeline, Cloudpermit Implementation Specialist will establish a weekly meeting checkpoint to ensure the implementation is on track and weekly action items are achieved.
IMPLEMENTATION MODEL
As part of the Implementation Model, Cloud permit and the Customer will be responsible for performing tasks throughout the various stages of the implementation process. The following is a description of tasks needed to successfully complete the implementation of the Cloudpermit Product. For a more detailed description please refer to the Cloud permit Implementation Methodology documentation.
Kickoff
A meeting between Cloudpermit and the Customers staff and key stakeholders to provide an overview of the product, discuss the goals and objectives and the agreed upon project schedule to establish a plan for a successful implementation.
Workshop
Cloud permit solution is built on standard, out of the box, functionality. The workshop will ensure that the Implementation Specialist has a full understanding of the business processes, the details the municipality needs to collect from the applicant, fee schedules and any templates which needs to be generated.
Cloudpermit standard out of the box solution integrates with ESRI ArcGIS through a REST(API) to establish the property location and also integrates with certain Payment Providers to allow for online payments.
Cloudpermit encourages the use of 3rd party payment providers which are already integrated with Cloudpermit. The Implementation Specialist can provide a full list of the 3rd party payment providers, however, if the municipality uses another 3rd party vendor, then a custom integration is needed and could impact the schedule. This should be identified as soon as possible to minimize the impact to the schedule.
Note: Any Non-Standard Integrations are subject to additional Scope and costs.
Configuration
Configuration of Cloudpermit with the features and functionalities needed to allow the customer the ability to process applications using the online Cloudpermit solution.
Training & Testing
Cloudpermit Implementation Specialist will provide two (2) standard training sessions to key users of the system to ensure the customer can successfully test the product.
Additional Training: Cloudpermit's training is built to ensure the customer is ready to utilize the software to its full extent. In some cases, additional training is necessary during tmplementation or Post Go Live.
The customer can order additional training according to Cloudpermit's price list.
Go Live
Go Live includes a Go/No Go decision prior to a scheduled Go Live meeting where the training environment configuration will be promoted to the production. At the Go Live meeting the customer will 3 Cloudpermit ®
submit their first Customer permit/application and/or create their first case in Cloudpermit to satisfy the Customers go live.
MILESTONES & ACCEPTANCE CRITERIA
Milestones are used for acceptance of various steps within the Implementation process. At the completion of each milestone the client will receive a Milestone Acceptance Document to be signed accepting that the tasks provided within each milestone have been completed. It is agreed that the Customer will accept each Milestone, unless such Milestone contains a "go live blocker" defect and Customer so notifies Cloudpermit, in writing, within 5 business days of the Milestone Acceptance Request.
Milestones that do not receive notification of non-acceptance within 5 business days will be deemed accepted.
Milestone Milestone Description Billable '
I
Number Amount
Ml Project Plan Acceptance 50%
M2 The kickoff, configuration, and 1'1 training sessions has been completed 50% Go Live tasks have been completed and the first permit/application is entered in Cloudpermit production Environment.
Once Cloudpermit has provided corrections, Customer will have Seven (7) business days to verify that the corrections are sufficient and to provide written notice of any failure to correct a Go Live Blocker. If no written notification is provided, the corrections and the Milestone will be deemed accepted.
Cloudpermit will correct all Go Live Blockers as described above and handle Post Go Live issues within a reasonable Post Go Live window. All other Defects will be tracked for potential future releases. Notice of any Go Live Blocker defect must be provided to Cloudpermit in writing.
CHANGE MANAGEMENT
Cloud permit Implementation Model provides a comprehensive, fully inclusive approach to implement the Cloudpermit solution. During the implementation process, additional needs may be identified for the Customer, that are outside of the project scope. These items once identified will be managed through a Change Request. The Change Order will identify the request, detail the requirements and justification and any scheduling or cost implications resulting from the change Request.
ADDITIONAL SERVICES COST
Additional Services are available from the Professional Services team that may not be included in the previously agreed upon scope. Cloudpermit can provide additional services as per the price list and through a change order
For on-site meetings, travel and per diem expenses will be invoiced to the Customer in accordance with Cloudpermit Travel Policy which will include airfare, mileage, hotel accommodations and daily per diem. 4 1
Contents
General Description ..................................................................................................................................... 2 C1oudpermit Core Benefits ... ................................................................................................................ , ..... 2 Ctoudpermit Building Permitting .............................................................................................................. 2 Ctoudpermit Common and Building Permitting Features .................................................................... 3 Cloudpermit Registration and Log in .................................................................................................... 3 Cloudpermit Dashboard ......................................................................................................................... 4 Cloudpermit Wort:spoce ......................................................................................................................... 5 Interactive Mops ...................................................................................................................................... 5 Messaging ................................................................................................................................................. 6 Pre-Consultation ...................................................................................................................................... 7 Review Management ............................................................................................................................... 7 Circulotioo ................................................................................................................................................. 8 Permit Issuance ........................................................................................................................................ 9 Inspections ................................................................................................................................................. 9 Fees Monogernent ................................................................................................................................ 10 Repo, t Management ............................................................................................................................ 11 Configuration Tools .................................................................................................................................. 11 Configuration Oesc ript ion ............. .......................................................................................................... 12 Cloudpermit Third-Porty Integrated Systems ...................................................................................... 13 Standard Configurable Thi rd-Pai ty Integrations ............................................................................ 13 Geographic Information System (GISl .............................................................................................. 13 Authentication through Open ID Connect (OIDC) .......................................................................... 14 Mui ti-Factor Authent k ation (MFA) .................................................................................................... 14 Additions and Minor Changes to Third-Porty Integrations ........................................................... 15 Custom Integrations .............................................................................................................................. 15 Integrations w,th 8-ackeod Systems .................................................................................................. 15 Integrations with Electronic Archives ................................................................................................ 15 ©2023 Cloudpermit Confidential
2 General Description
Cloudpermit is online community development software that provides local governments with Software· as-a-Service (SaaS) products available 2417.
The Cloudpermit product portfolio includes Building Permitting, Planning, Land Use Permitting, and Code Enforcement products.
This product description applies to Building Permitting product.
The information in this document is subject to change without notice aligning with future releases.
Releases supply information about new features and non-security updates.
Cloudpermit Core Benefits
Cloudpermit supplies one complete end-to-end product for local governments to manage the entire building, licensing, and planning e-permitting and code enforcement case process. It allows all parties integral to the process, from applicants to authorities to key stakeholders. This ensures that all parties receive real-time information about applications, licenses, and cases.
Below are described the primary benefits Cloudpermit provides to its customer base:
⇒ Cloudpermit standardizes local government's building, licensing, planning, and code enforcement processes by supplying the best digital practices.
⇒ The 24/7 online service on any browser or operating system allows remote and mobile work onsite. ⇒ Monthly releases enable automatic updates to the product providing the latest updates and enhancements while not requiring users to download or install any software files. ⇒ A cloud-based Saas product provides a quick and easy implementation with a municipality-based configuration, lessening the burden on municipal resources. ⇒ Through interactive maps, local governments can use high-quality location data and up-to-date property information. This up-to-date property information is derived directly from the local government's Geographic Information System (GIS).
⇒ Workspaces enable instant collaboration and communication within applications and code enforcement cases, simultaneously speeding up processes and improving the workflow for all involved parties.
Cloudpermit Building Permitting
The Building Permitting product supplies online applications for public builders and municipal building authorities. The product is accessible on any browser and mobile device with an Internet connection.
The Building Permitting product enables the following features:
⇒ It provides end-to-end, online software for local government building department customers, which helps them to manage applications efficiently and effectively. ⇒ It allows the public to submit and track their building applications online. ⇒ It helps streamline processes associated with the day-to-day responsibilities of building departments.
⇒ It offers unique features to assist with pre-consultation, application reviews, inspections, permit issuance, and much more.
©2023 Cloudpermit Confidential
The Cloudpermit software is automatkaUy updated periodk ally with the latest updates and enhancements, not requiring users to download or install any software files.
Cloudpermit Common and Building Permitting Features
Cloudpermit comprises unique features standard throughout the product. These include Registration and Login, Dashboard, Workspace, Configuration tools, Interactive Maps, and Messaging.
The Building Permitting software provides Pre-Consultation, Review Management, Circulation, Inspections, Fees Management, and Report Management features to enhance an excellent user experience in the building workflow.
Clouclpe, 1111t f3url<i11HJ Per rnit ting teotu, es:
Pr e-Consu:t(lt 1011
Rev1ev1,,• rv1(11l(lijCln(;llt
Ci1culot1011
l_~pect ions
Fees lv'unogement
Report tv'lonogement
Cloudpermit Registration and Login
Cloudpermit maintains one centralized login function supplying the same functionality for public users and municipal authorities.
The login can be integrated with the organization's Active Directory (option) or a third-party Multi-Factor Authentication (MFA).
Municipal authorities will receive the Cloudpermit User ID during the product configuration. 9 oudpermit ®
...... ........ _..
©2023 Cloudpermit Confidential
4 A public user must first register the Cloudpermit account to the service. Through registration, the user is guided through a draft application to ensure an understanding of functionality. a . --
S,loudpermit®
·----- - ·-
Cloudpermit Dashboard
The Cloudpermit dashboard displays high-level information in a compact view. It enables new application creation, tracking user notifications and action requests, and searching, sorting, and filtering workspaces at each application lifecycle stage.
The dashboard includes the "Tasks and requests" view that notifies users about action requests.
My dashboard
Tasks and requests
--, .. ._ ..
I
Elm
-.. -- I
The dashboard allows applicants and munidpal authorities to search and filter properties, applications, and code enforcement cases using various preconfigured search criteria.
The "Results" section shows the filtered workspaces In a hst mode or a mop view according to a user's choice.
= In the map view, the users can adjust their map by zooming in/out or choosing different layers to display the property location.
⇒ The list view shows the results as cards with the selected essential information of each workspace.
The "Results" section with a map view.
m i~s:::s:s:::::::::>< •·-- ., ,,~'"' "'"' -~'-'""-.... --,~• > -.. - -
•
©2023 Cloudpermit Confidential
\
5 The primary navigational and functional elements are the same for applicants and municipal authorities in their dashboard in Cloudpermit. However, municipal authorities have additional features, like the Inspections section with quick access links to My today, Dispatching, and Cancelled inspections workspaces.
The quick access links in the user dashboard.
Inspections
Cloudpermit Workspace
The Cloudpermit workspace is the core collaborative space for adding, updating, changing, uploading, and storing application and project informatlon.
Each workspace holds the processes, functionality, and data fietds necessary to manage, approve, and issue building and planning apphcations and code enforcement coses.
The "Building Permit" application workspace.
@....,,._,.,
11066 LAMONT DR, Middlesex Centre ~CINCQRl':xl1 rri,...,_~•~Ol'~~S~ W ¥IEE f§iiliEPM O linat~CYl'I
--)9l900(.0,(0:'.tl'OO('()O(
-I
II APPUCA~ )
GI
PwtM ~ ----- J-.1~
PARTIES TO TK APl'UCAIION
APPl.lCATtoN DATA
ATTACHMENTS
Interactive Maps
l~ i~~•.un ,o,,. ~
All Cloudpermit users con benefit from the interactive maps within Cloudpermit.
The interactive maps enable applicants to search for properties by address, roll number, PIN, or PID, enter property details manually, or map properties on the interactive mop during the application creation. ©2023 Cloudpermit Confidential
6 Cloudpermit displays the property on a mop with the location details.
Location for the applicat1on
Sclloc.l.apopwl~ ~tNI~ SeM.t\c.,ai».u•,Ql---o, por(IO•~o,, r.-.,nup.•tf'I ~1~0Cl"IMlrJ'"'1f'll'\#'O,.,.P't!Ofl'lt ~c:t,c,et':itt-,~~ ..
"
~IYde~,
ll.'.lt--31),oox,JOl~
~,oe,,OU-U,fli
~t,OOolt'.!ll•W,,.,OO'l'l'e,JC,,lf'Cll"-1•.,._~•"1:",J""•'._"fl'I ,_,,....vil~:)e,OIQ~
....,,
l ... ~~1'"'"1lOtT
On the department side, the GIS integratton aids municipal authorities in selecting permit and inspection working areas, planning routes, and navigating optimal driving instructions for inspectors with a Google Maps integration. The map integration anows municipal authori,ties to read and accurately calculate property size, display information, and assign different sites based on locations and zones.
Messaging
The Messages feature is for all users and stakeholders. Built into each application, users can send, reply, and follow an application's public (messages visible to all users) or direct (messages visible to selected recipients) workspace messages within the application.
This real-time communication con remarkably speed up the application process for all parties associated with the application.
The workspace for public messages .
.. ~ ..... ~. AIICt -.om"1ittarot @jijfilfi@ ~11• Out.
la6i-Oac :un> 02 11 a.so.,,,.
HI d0 t nffd la pti:r.-tdc:- fNM"e bltlk11n~ dra~11',.g1i I~ ,,,., ~gpJlt.iUon? ...... '
...... w,ma:,ii+
I ~ SotW ''\jl"'k )OU 10" yuwi ff'icJ~~•UV Vou, ..iilU- hn"'nlt .. w C ~ No Olhor i.11aw"'9~ .:1r• nC?Cdeo
""'
©2023 Cloudpermit Confidential
7 Pre-Consultation
Pre-consultation is a pre-application step that is usually voluntary for building applicants. However, local governments may configure it as a mandatory step for specific application types.
Suppose pre-consultation is not mandatory in the selected building application type. In that case, applicants may decide during the application creation if they wish to have pre-consultation for their building plans. The pre-consultation option is available ofter selecting the application type, category, work type, and target for the draft application.
The applicant requests a pre-consultation in the application.
Select calegory, type and target for your appllcalion
-·- ~-~dp,11'~---~~t ....... -ini...,i....,,,,.. n-.--....--w~,,.,_~•a.....,....•kw• ~ ... Pl.._._ Ot+•~t....-,b,_IIIIMal.....,d,,.,.=-,py
-
"'-~-
--
--
----
_,,_
S'oll, .... ______..
..-~~ftJliotllttN~~---tl',_..ll•~amt11G11\0t•lll"CIOI'..--. _
[ ...... Daol.Coulto."°'°''-"•'SlN
...
The pre-consultation process includes one or more interactive meetings arranged through Cloudpermit. In that way, applicants and their authorized representatives con present and discuss their development proposal with relevant staff and external agencies within the local government well advanced of the project start. Cloudpermit enables municipalities to track and document their pre-consultation process digitally.
The pre-consultation process is as follows:
⇒ Applicants request a pre-consultation through a guided step-by-step process in Cloudpermit. The pre-consultation usually includes one or more meetings between the parties, which the municipal building authorities set up via Cloudpermit.
=> Upon meeting completion, the municipal building authority prepares a pre-consultation report and a draft approval application with requirements for the applicants to submit to the municipality in Cloudpermit.
Review Management
The Review Management is for municipal authorities.
Cloudpermit enables municipal authorities the management of opptication submission reviews by providing a variety of review types that municipal administrators can configure for relevant application reviewers in Cloudpermit.
©2023 Cloudpermit Confidential
8 Municipal authorities assess each application and its plans ofter they ore submitted. If the opphcotion requires extra reviews, municipal authorities request them from the appropriate reviewers. After completing evaluations, reviewers mark the forms and attachments evaluated as complete. If the application requires revisions from the applicant, o change request will be sent to the oppticont.
The Reviews section in the building application workspace. -REVIEWS J.OO~A(Vl(W + ""-·
- .,_
v -- - - ·~~If.MOO' HEHN: ~
v--
.. _ ..... ....,.. .. Iv~ ... ,.... __ .. j.lc.e~UMCII' a I V ArcMtctl.nf!Pllnl ..-.w
- •t-:e~U-1(0, .,
When a change is requested for the application, Cloudpermit creates a task for applicants, which appears in the dashboard's Task and requests section. Applicants will also be notified via email about the change request.
After providing the required changes for the application, municipal authorities verify them. Also, the review result, notes, and time used ore recorded in Cloudpermit. After completing all required application reviews, municipal authorities create a permit on configurable templates in Cloudpermit.
Circulation
Circulation is on essential port of processing workspaces within Cloudpermit.
Cloudperm1t allows municipalities to decide which internal and external organizations, agencies, and corporations may participate as stakeholders in the Circulation process and odd them to the municipality's approver groups in Cloudpermit.
In practice, the responsible municipal authority circulates the building application to the stakeholders, such as fire, water, or sewerage deportments requesting comments or approvals in Cloudpermit. This way, comments and approvals con be requested from all stakeholders concurrently, which speeds up the approval processes.
Cloudpermit supplies user management and task assignment functionoOties for stakeholder organizations to manage requests and internal circulation. However, the municipal building deportment's authorities can control who con see the original comments online. Cloudpermit also notifies the assigned circulation authorities or organization's administrators of new circulation requests and approaching due dates.
Additionally, Cloudpermit allows municipal department authorities to complete the circulation request on the stokeholders(s} behalf and record their results in Cloudpermit. That way, Cloudpermit con help municipal authorities ensure all circulations are accurately recorded on Cloudpermit and save time. © 2023 Cloudpermit Confidential
9 The municipal building authority completed the circulation request.
QRCI.UIIOH
- _ ..
..,...Cltlltt•VWWJ«~Mltt
- -
"l.orra,OMfl~ --M-ll"C! ~n<IJdiCll'IU'9lh MG»....,.O.,C41'!t)O' ~~'-Crt ctOll,7t~....,_Ut...,..11:1__,,,.,,,...,,_~,no,r.tvll .. .-;,,.¥-,;n~ola ... M>LA .. ••u~c~ l),.cM!f,.,....«iiet~~ifl~~• .. tMWO._,.,:xt:W'l..,t.q,ae,.__lp,wl,l'I.., (-<~~~Q,QO,r.~~Ol~Wll41.;..liNOl,lo,'r<..a~'f-aM_,ldHt~ -'\,;a-.,,.OWll~k""'1.CCl'M:'lfl.,, - .. ~.L-~N4'NX't~~Mllab:nlltdl,Q'aT~:/IQ,,,t,.tA ..... a1....,.--,.~.-h,,d .... ~~oll~'"'""_,,.,.~.,,~~~MNlt ..... OCIIOfl\~11~♦ .. -tsw~~ ... t,O,, ..... l~ ( .-~W1100CHC•001atMIYl!t~ ~ llll ~ a.1 '1"c.l°'""""'~ .... ldWl.ioo'ul'I I ""'""°"r,,, + 1
After circulation, the requesting municipal authority prepares and publishes a report to applicants, including received comments and approvals for the project.
Cloudpermit notifies the assigned circulation authorit ies or the organization's administrator of new circulation requests and approaching due dotes.
Permit Issuance
The Permit Issuance feature is for municipal authorities.
The feature enables municipal authorities to define, create, and issue permits on pre-configurable templates. It also allows them to decide the project's required inspections and permit fees.
After completing reviews and acknowledging application payments, municipal authorities prepare the permit for issuance.
⇒ All issued permit PDFs ore downloadable and saved in the application's "Permits" section in Cloud permit.
= Applicants and municipal authorities hove access to all permits on the application anytime.
The "Permits" section in the building application workspace.
PERMITS
.. .-
........ l:uwdon . .. ~ ... , ..... ,.,.mtldDc:\lmW1t
....,.. ZOU•l>l·1~. . ... h ,1.,9e1
- "~:~~10'1
XIU•i-l 10 l1.1t11 A.J~.thW
Inspections
A crucial component of Cloudperm,t is the Inspections feature for municipal building authorities.
The Cloudpermit configuration enables municipal authorities to configure a set of default inspections for the selected apptication types.
They can manage inspections by adding new ones, removing unnecessary ones, and publishing a list of required inspections on each oppHcotion they work on.
©2023 Cloudpermit Confidential
10 The inspections configuration workspace.
Inspection 1ypes
W;)INM!f...a-101
..... l'\1,1,JHIUOnot MwwJII« SC!f..-.Cct W.M«mullOO hiilll.Joto and I lr.K'N 1111.-,, leQu,n,cl iT 11'1111 ',11,,Jfa,t la'~• --
NTJ1Hihon0C sarvl¥)1 5C\WI' 1T'Xt'fhaOJOP«t"t.,.. to•t>e nl«ol' ot U,c ~Olng. It f('St f ~ tl'M PO'tlO'lot pt~ s,,wn ci '90Virod
Applicants request inspections through the Inspections feature in their application in Cloudpermit and decide the date and time of the inspection.
Once the inspection request is dispatched to the relevant inspector, Cloudpermit allows building and planning inspectors to conduct on-site mobile inspections.
Inspectors only need to write their notes once, ensunng all data is available for all municipal authorities within the department online on any connected mobile device.
Inspectors have all permit information, property contact information, approved drawings, reports, and previous inspection data online in Cloudpermit.
Inspectors can do the following:
=> Manage deficiencies and orders online.
::> Upload photos to their inspection notes during the on-site visit. = Benefit from the configured templates while creating reports and certificates on-site.
All conducted inspections with the downloadable inspection report PDFs are recorded in the "All Visits" section in Cloudpermit.
The "All Visits" section in the inspection workspace.
AU. 'VlllTS
Fees Management
The Fees Management feature is for municipal authorities.
The feature is an all-in-one solution that allows Cloudpermit to manage permit and application fees. It facilitates payments made and received in person or online via native third-party integrations.
Municipality administrators create and process fees using preconfigured fee items. Additionally, Cloudpermit allows automation of fee calculation for deposits and upfront fees. The fee automation inserts the appropriately calculated fee for the bill to be paid online. Additionally, Cloudpermit automatically prepares and sends applicants a downloadable invoice PDF via email. ©2023 Cloudpermit Confidential
11 The fees and schedules configuration workspace.
Configure fees & schedules:
Building Control
··-.. --■-•---------··---~ .... ~ •••• ------··--- · -
-·
The integrated online payment solution hos the following benefits; = Online payment remarkably reduces on•premises cash payments because applicants con safely make payments online 24/7 and benefit from better transparency in their paid fees. =- Online payment enables municipal authorities to automate permit delivery straight ofter the permit fee is acknowledged.
The selection of integrated online payment providers in Cloudpermit is limited. The third-party integration chapter on page 13 lists available mtegrated payment checkout systems.
However, Cloudpermit can integrate the payment process into local governments' payment checkout systems upon agreement (priced separately}.
Report Management
The Report Management feature is for municipal authorities . . ,. • '• ' • :t: I .' - ~ ._ .. ' r, "' ,
PERMITS ASSESSMENTREPOlmNQ PAYMENTS IISl>ECTIOHS Rf.WW$ ITATcAII This feature provides customizable data exports for permits, payments, inspections, and review data. It also enables automatic assessment reporting for selected regions.
Processing time, review, and inspection reports reveal the organization's performance, supporting the process's improvement. The reporting data helps municipalities report issued permit numbers and types. It also provides a view of current open permits and in-progress applications.
Configuration Tools
According to the municipality's requirements, local government administrators hove complete control of the service, including the Cloudpermit configuration.
Cloudpermit Building Permitting configuration enables the following:
=> Managing approver and user groups
⇒ Working application type configuration with requirements for each type ⇒ Configuring and managing inspections
©2023 Cloudpermit Confidential
12 ⇒ Configuring and managing application fee items for schedules ⇒ Managing payment page settings
⇒ Supporting managing review configurations
⇒ Allowing automating notifications, for example, for permit expiry. ⇒ Managing language settings and selection in the user interface ⇒ Managing building document templates
⇒ Managing role-based permission in user management.
Cloudpermit also develops and sets various application templates and forms for municipal users.
Configuration Description
The tables below display the Building Permitting features configuration.
Configuration:
Section Cornponerit Description
Bu,ld11HJ pcI •11It
cutcgor res
1 . Cotegory -------lt- c1-ll~o-V'_-'_S_r_l_1c_1_n_9_1119 the clesr11pt,on of c:
_ clescr 1ptIc,1_1 cotc9o•y
Bu1icl1 rHJ per 1111\
cntecJor res
Supplernentol
lrn1ld1rHJ perrnrt
Attuchrnent types
I Project types It 1nclucles work cc1t PCJOI res, \\'OI k types, rn1d work torqets
Reviews und 1equ11ed
fo11ns, uttocl11nents,
ond ,ev1e\.\1 co,)fi~Js
Per rnrt number IncJ
Fees Management:
Cc:tC<Jor ,es
/\Ciel Cl ll('\'!
ot :ochrnent tvpe
forlllS
I Per r•11t numlwr
Section Coniponent
f-ee schedule Confic1urc1t1or1
I
It crl ows the serectIon c111cl ed,t,119 of types of
supplt"1ientu. hu 1ld1nrJ peI •111ts.
It ·ncludPS c1vrnlc11Jle uttc:rl1111e11t types for
pern,its.
lhe ovrnlohle forms w1ll lw ocld,·cl cIs 1equ1recl
for Clll\' c1pplrcc1tron type.
It nllows os,IqI11IHJ c, 1n11nlw11tHJ systern ton
mun1c:1pol1ty.
Des er rpt 1011
It 111clucles er 11st of uv<rilcrlile fees spec1f1c to
coch cl ient.
--------• ------------
Othe, settlllCJS I Dnl111e pcryrncnt
Inspections:
Sect 1011 Componrnt
Inspections Tr rne slots
©2023 Cloudpermit
It er I lows confrcJur 111CJ C louclpe, m ,t to uccept
onl111e pc,yrnents from V{I' IOUS SE'IVICC
prov1clc1 s
Descr,ptron
Clouclpe1rrnt suppolts two timeslots for
r11spec:tI0·1 scl'edul,nq 8:00 : 2.00 [) rn c1nd
17:00 p.m. - •l:00 p.rn.
Confidential
13 i Inspect1on types Inspect ion subtypes Cloucl:1e1rn1t suppo1ts t\·m InspectI011 suiltvpes I cu1,ent ly
Templates:
Section
·1 ernplc,tes
·1 emplc,tes
Component
PDF Templc,tes fo,
inspections ..
PDF Ternplotes fo,
Desc, 1pt1on
It ,nclucles pe, rnit ternplotes with custo,rnzoble
lc1youts
It ,ncludes templc,te types.
.1. ,nspe~_t_Io_n_s __________________ ~
Locot,on to, the
cI ppl1cot1on
I Extrn rnop lc,yers
Application & Review:
Section Component
S1911 off Compl1c111ce lon9uc1ge
Cloudperrrnt crn1 enoble mlcl1t 101wl mop loye1s
for tile client.
Description
It enc11Jles worcl11HJ speer fie to
count1y/p1ov1ncc/stote. Clouclperrnit suppoI ts
the follow1n9 lc1119uo9es: en-cc,. en -us. c111d f,.
cc1.
Cloud permit Third-Party Integrated Systems
Cloudpermit hos standard configurable integrations to over twenty (20) systems categorized under six different integration types described below.
Suppose the need for integration with a standard configurable integration cannot be fulfilled. In that case, Cloudpermit may integrate a new system, make a minor change to an existing one, or develop a custom one. These integrations are priced separately and, if applicable, addressed within your contract.
Standard Configurable Third-Party Integrations
Cloudpermit hos integrations to third-party systems that can be configured for the client as part of the standard implementation. These integrations may include monthly or annual fees, which will be stated in a contract.
Geographic Information System (GIS)
Cloudpermit supports a one-way integration with the municipal authority's GIS to search properties by civic address or property identifier, retrieve property information, read map layers to be shown on mops, and retrieve owner information.
Supported GIS integrations include the following:
• ESRI ArcGIS
• CGIS
• CartoVista
• MuniSight
©2023 Cloudpermit Confidential
14 Online Payment
Cloudpermit integrates with most online payment providers through various online checkout systems or payment gateways to process fees and dues. Users con choose an online payment option for their bills when an online payment integration is configured for a municipality.
Payer information and bill contents are sent to the Pel-compliant payment provider and forwarded to the provider's checkout page. The payment provider returns information about the success of the payment.
Where necessary (and possible), the convenience fees are configured in the payment system.
Supported Online Payment integrations include the following:
• Allpaid
• Bambora
• CCP/NIC Online Payment
• ePay
• E-xact
• Government Window
• Merchante
• Moneris
• OpenEdge
• Paymentus
• PayNowlink
• Square
• Stripe
• Payeezy
Authentication through Open ID Connect (OIDC)
When a user account is linked to an external system for authentication, Cloudpermit sends the authentication through on Open ID Connectivity (OIDC) API (Application Program Interface) to a third• party login page for the organization.
With this integration, the whale authentication happens in the third-party system, which returns a success of authentication to Cloudpermit. The integration does not include authorization; all groups and permissions ore managed in Cloudpermit.
Supported OIDC authentication integrations include the following:
• Azure AD
Additional AD integrations ore priced separately and, if applicable, addressed within your contract.
Multi-Factor Authentication (MFA)
When a Multi-Factor Authentication (MFA) is needed for a department, Cloudpermit login will require at least Two-Factor authentication.
After successful Cloudpermit authentication, the users will be sent to a third-party system for secondfactor authentication, such as a mobile opp or Security Management System ISMS). ©2023 Cloudpermit Confidential
15 The third-party system must supply on OIDC (Open ID Connect) interface, and it returns the success of the second-factor authentication to Cl!oudpermit.
Supported MFA integration includes the following:
• Duo
Additions and Minor Changes to Third-Party Integrations Cloudpermit adds integrations with new systems if the integration is for on existing integration type, e.g., Online Payment or GIS. Cloudpermit has confirmed that the third•porty system hos Application Program Interfaces (APls) that support the current integration model.
All integrations to new systems and minor changes to existing system integrations must be agreed upon separately, and they ore not included In the standard implementation. Delivery may contain a development fee and on annual or monthly fee.
Cloudpermit will give an estimated future retease for integration upon agreement.
Custom Integrations
All other integrations not Configurable Standard integrations, minor changes to existing integrations, or new systems with on existing integration type ore considered Custom Integrations.
All custom integrations require a feasibility study and specifications before the agreement. Cloudpermit will give an estimated future release for integration upon agreement.
Delivery of a Custom Integration contains a deve1opment fee and on annual or monthly fee.
Integrations with Backend Systems
In backend system Integrations, Cloudpermlt leverages an integration process that enables sending the information to a bockend system.
⇒ Cloudpermit creates a folder in the bockend system for each workspace. :::::> Cloudpermit links the properties and contacts into the folder and make new contacts if necessary. ~ Cloudpermit updates the folder's status and specified data fields in the folder.
Integration can be configured to include the transfer of fees to the backend system. Completed reviews and inspections con be configured to be transferred too. The integration setup will require changes in the backend system and mopping statuses and codes between the systems.
Integrated bockend solutions ore priced separately and, if applicable, addressed within your contract.
Integrations with Electronic Archives
This type of integration sends the content of a workspace to on external system for archival. The thirdparty systems ore Enterprise Content Management (ECM) or Electronic Archives. Cloudpermit will create an archival folder in the third party, write the values of the configured data fields in the folder, and transfer configured attachments into the folder for archival.
Integrated electronic archive solutions ore priced separately and, if applicable, addressed within your contract.
©2023 Cloudpermit Confidential
1 Contents
Description ................................................................................................. , ....................... .. ............ 2 Ctoudpermit Core Benellts ......................................................................................................................... 2 Cloudpermit Code Enforcement ...... , ............................................. , .. , .......... , ................................... , ..... , .. 2 Cloudpermit Code Enforcement Features ................................ ,.,, ., .............. , ............................. , ..... , ..... 2 Complaint ond Cose Management ............................................................................................. , ........ 3 P-oblic View ............................................................................................................................................... 4 ConHgurotion Tools ..................................................................................................................................... 5 Configuration Description .......................................................................................................................... 5 Cloudpermit: Third-Party Integrated Systems ......................................................................................... 6 Standard Configurable Third-Porty Integrations ..... , ............................................................. , ..... , .. , .. 6 Geographic Information System (GIS) ............ .. , .... , .. ,, .,, ., ..... ,, ., .......................................... ,., .. , .. , ........ 6 Online Payment ................................................... ... ......... ......................................................................... 7 Authen 0cotion through Open ID Connect (0 IOC) ............................................................................. 7 MulU-factor Authentication {MFA) ....................................................................................................... 8 Additions and Minor Changes to Third-Porty hitegroUons .............................................................. 8 Custom Integrations ................................................................................................................................ 8 Integrations with Backend Systems ....................................................................................... .............. 8 Integrations with Electronic Archives ................................................................................................... 9 ©2023 Cloudpermit Confidential
2 Description
Cloudpermit is on online community development software that provides local governments with Software-as-a-Service (SaaS) products available 24/7.
The Cloudpermit product portfolio includes the Building Permitting, Planning, Land Use Permitting, and Code Enforcement products.
This product description applies to the Code Enforcement product.
The information in this document is subject to change without notice ahgning with future releases.
Releases supply information about new features and non-security updates.
Cloudpermit Core Benefits
Cloudpermit supplies one complete end-to-end product for local governments to manage the entire building, licensing, and planning e-permitting and code enforcement case process. It allows all parties integral to the process, from applicants to authorities to key stakeholders. This ensures that all parties receive real-time information about applications, licenses, and cases.
Below are described the primary benefits Cloudpermit provides to its customer base:
⇒ Cloudpermit standardizes local government's building, licensing, planning, and code enforcement processes by supplying the best digital practices.
⇒ The 24/7 online service on any browser or operating system allows remote and mobile work onsite. ⇒ Monthly releases enable automatic updates to the product providing the latest updates and enhancements while not requiring users to download or install any software files. ⇒ A cloud-based Saas product provides a quick and easy implementation with a municipality-based configuration, lessening the burden on municipal resources. ⇒ Through interactive mops, local governments con use high-quality location data and up-to-dote property information. This up-to-date property information is derived directly from the local government's Geographic Information System (GIS}.
⇒ Workspaces enable instant collaboration and communication within applications and code enforcement cases, simultaneously speeding up processes and improving the workflow for an involved parties.
Cloudpermit Code Enforcement
The Cloudpermit Code Enforcement product supplies functionality to enforce violations of statutes or ordinances regulating public health, safety, pubhc works, and building standards within the municipahty.
Accessible through any browser or mobile device, municipal code enforcement authorities manage citizens' complaints, inspections, and code enforcement cases to ensure the violations ore duly resolved.
Cloudpermit Code Enforcement Features
The Cloudpermit Code Enforcement software provides Complaint and Case Management and Public View functions to provide an excellent user experience in the municipality's code enforcement workflow. ©2023 Cloudpermit Confidential
Clouclpe11 nit Code Enfo1 cement Fec,tures
_Co11_1plc11nt c111cl Cose Mcmoqernent
Puill1c View
Complaint and Case Management
3 The Complaint and Case Management functionality, i.e., the "complaints and new coses" workspace, provides comprehensive functionalities for processing code enforcement complaints and creating new cases.
By clicking the "Open Complaints" or "Crete New Cose" links on the user dashboard, the user will access the "complaints and new coses" workspace.
Access to the "complaints and new cases" workspace. ----------- ----------- -- -- 1 ' , I • r ' • • •,. , • ....
Code enforcement
Using the workspace for complaints and new cases, code enforcement officers can manage all complaints.
These complaints may have come from the public via "Public View" or from code enforcement authorities who received them via phone, email, social media, or municipal website and recorded them in Cloudpermit via complaints and new case workspace.
The Complaint and Case Management in Cloudpermit enables the following:
⇒ Cloudpermit's interactive maps enable one to search for code violation properties by address, PIN, PID, or spot properties on the map.
⇒ Users can filter complaints by selecting the category and status criteria from the drop-down menus. Cloudpermit displays the top-matching cases as case cards in the "Results" section and as pins on the map.
⇒ Users can select to display all past complaints (reviewed, closed, abandoned) in the map or list view.
⇒ Code enforcement officers triage the complaints. The invalid complaints will be abandoned.
However, they remain in the system and can be reopened anytime. ⇒ Creating new cases will take all valid complaints to the code enforcement process. ⇒ Cloudpermit automatically creates pre-scheduled inspections the code enforcement officers can manage by modifying the suggested date and time and assigning them directly to an available inspector.
©2023 Ctoudpermit Confidential
4 Creating a case for the valid complaint in the "complaints and new cases" workspace.
Prionly ~leqt'I',
G - 0 ,._, .. _,...,..v
C.1i1tHsc,tot,on
·------ 1- v • r .11. T '
0t~iM»OIIIWl~<ll"I
··-·-··--.. I""""" v • .1 ll r•
,_
Each municipaHty's category types for complaints and cases are configurable to match their local ordinances and codes.
Additionally, code enforcement officers can open a new case ln the workspace for complaints and new cases without first filing a complaint if they discover a violation without receiving a formal complaint.
Creating a complaint for the specific property location in Cloudpermit. -- °"°'"'-- ltll
I IUl~wmo.,-r=-(IM~t
■ 8 - ·~ Ell ,.LI.SM ll\'t"'(;t.uJ
- ·
'
Public View
A municipal code enforcement department can publish a "Public View" in Cloudpermit to display the existing complaints and code enforcement cases on a map. The "Public View" also enables citizens to submit new complaints.
The "Public View" functionality is configurable. Municipal administrative users can select which contact information, for example, name, phone, address, and email, is required by the complainant and provide options for different categories for the complaints.
©2023 Cloudpermit Confidential
s
Municipal administrators can also restrict the ability to show any existing complaints or code enforcement cases on the map.
The "Public View" is displayed at the top of the "complaints and new cases" workspace. =::::-:::.-·-·· .... ------·--·-----·--·----·--------
-··-·-··-·-·------------·--~---- ---·--•.--..... ------------·---·-··- .... ----·--···- - c---- >c---- -- --)~~<-->El<=' a ---....... ...
Configuration Tools
Administrative users can adjust the service to the municipality's requirements using Cloudpermit's configuration tools.
Cloudpermit Code Enforcement configuration enables the following:
⇒ Adding and managing by-low enforcement categories and visibility of complaints ⇒ Managing the content for field inspections
⇒ Managing attachment types, party roles, and archiving configuration ⇒ Managing case numbering
⇒ Managing fees configuration
⇒ Working forms and templates configuration
⇒ Managing reporting configuration
⇒ Managing user groups and role-based permissions.
Additionally, municipalities can manage their system language selection.
Configuration Description
The tables below describe the Cloudpermit Code Enforcement configuration.
Configuration:
Section
Code Enforcement
categories
©2023 Cloudpermit
Component
C: c1te901v clesc11pt1011, /\rchve
set t11HJ. Com11lc1 nts
Confidential
Description
It c1I1ows c'1c111cJ111c1 the' cc1te(Jo 1y
cle scr ,ptI011, rnch1v111lJ c1 cosc
w o ,kspoce, rn·cl m c111c1tJlrlCJ the
v1s11J1l tv of co1'lplrn11ts 111 the Public
V1ev: uncl othe r cIepc,rtrn e11ts
Fees Management:
Cloud permit Third-Party Integrated Systems
Cloudpermit has standard configurable integrations to over twenty (20) systems categorized under six different Integration types described below.
Suppose the need for integration with a standard configurable integration cannot be fulfilled. In that case, Cloud permit may provide integration to a new system, make a minor change to an existing one, or develop a custom one. These Integrations are priced separately and, if applicable, addressed within your contract.
Standard Configurable Third-Party Integrations
Ctoudpermit has integrations to third-party systems that can be configured for the client as part of the standard implementation. These integrations may include monthly or annual fees, which will be stated in a contract.
Geographic Information System (GIS)
Cloudpermit supports a one-way integratron with the municipal authority's GIS to search properties by civic address or property identifier, retrieve property information, read map layers to be shown on maps, and retrieve owner information.
©2023 Cloudpermit Confidential
7 Supported GIS integrations include the following:
• ESRI ArcGIS
• CGIS
• CartoVista
• MuniSight
Online Payment
Cloudpermft integrates with most online payment providers through various online checkout systems or payment gateways to process fees and dues. Users con choose an online payment option for their bills when on online payment integration is configured for a municipality.
Payer information ond bill contents ore sent to the Pet-compliant payment provider ond forwarded to the provider's checkout page.
The payment provider returns information about the success of the payment. Where necessary (and possible}, the convenience fees are configured in the payment system.
Supported Online Payment integrations include the following:
• Allpoid
• Bambora
• CCP/NIC Online Payment
• ePay
• E-xact
• Government Window
• Merchonte
• Moneris
• OpenEdge
• Paymentus
• PayNowlink
• Square
• Stripe
• Payeezy
Authentication through Open ID Connect (OIOC)
When a user account is linked to an external system for authentication, Cloudpermit sends the authentication through on Open ID Connectivity (OIDC) API (Application Program Interface) to a thirdparty login page for the organization.
With this integration, the whole authentication happens in the third-party system, which returns a success of authentication to Cloudpermit. The integration does not include authorization; all groups and permissions are managed in Cloudpermit.
Supported OIDC authentication integrations include the following:
• AzureAD
©2023 Cloudpermit Confidential
8 Additional AD integrations are priced separately and, if applicable, addressed within your contract.
Multi•Factor Authentication (MFA)
When a Multi-Factor Authentication (MFA) is needed for a department, Cloudpermit login will require at least Two-Factor authentication.
After successful Cloudpermit authentication, the users will be sent to a third-party system for second• factor authentication, such as a mobile opp or Security Management System (SMS).
The third-party system must supply an OIDC (Open ID Connect) interface, and it returns the success of the second-factor authentication to Cloudpermit.
Supported MFA integration includes the following:
• Duo
Additions and Minor Changes to Third-Party Integrations Cloudpermit adds integrations with new systems if the integration is for an existing integration type, e.g., Online Payment or GIS. Cloudpermit has confirmed that the third-party system has Application Program Interfaces (APls) that support the current lntegration model.
All integrations to new systems and minor changes to existing system integrations must be agreed upon separately, and they ore not included in the standard implementation.
Delivery may contain a development fee and an annual or monthly fee. Cloudpermit will give an estimated future release for integration upon agreement.
Custom Integrations
All other integrations that are not Configurable Standard integrations, minor changes to ex1sting integrations, or new systems with on existing integration type ore considered Custom Integrations.
All custom integrations require a feasibility study and spedfications before the agreement. Cloudpermit will give on estimated future release for integration upon agreement. Delivery of a Custom Integration contains a development fee and on annual or monthly fee.
Integrations with Backend Systems
In backend system integrations, Cloudpermit leverages on integration process that enables sending the information to a bockend system.
~ Cloudpermit creates a folder in the backend system for each workspace. = Cloudpermit will link the properties and contacts into the folder and make new contacts if necessary.
⇒ Cloudpermit updates the folder status and spec1f1ed data flelds 1n the folder.
Integration can be configured to include the transfer of fees to the backend system. Completed reviews and inspections can be configured to be transferred too. The integration setup will require changes in the backend system and mapping statuses and codes between the systems.
Integrated backend solutions are prked separately and, if applicable, addressed within your contract. ©2 023 Cloudpermit Confidential
9 Integrations with Electronic Archives
This type of integration sends the content of a workspace to an external system for archival. The thirdparty systems are Enterprise Content Management (ECM} or Electronic Archives. Cloudpermit will create on archival folder in the third party, write the values of the configured data fields in the folder, and transfer configured attachments into the folder for archival.
Integrated electronic archive solutions are priced separately and, if applicable, addressed within your contract.
©2023 Cloudpermit Confidential
Cloudpermit ®
O>ntractor
Rq;stry Software
Description
Guide 2023
1 Contents
Contents ............................................................................................. ~······· .. ·······-············· .. ··········-····· ········· .. ··········~······· 1 Ge11,r.,J Oesaiption .................................................................................................................................................................... 3 Cloudpermtt Core 8tflE!flts ........ , .................................................................................................................................................. 3 Cloudperma Contr~or Registration ......................................................................................................................................... 3 Contractor Regtstration Appl1cation Creation Wizitfd ........ , ....................................... , .......... , .................................................... 4 8eginnin;g the application creation ......................................................................................................................................... 4 O·raft Contractor Re:gi.stratiOn application workspace ............................................................................................................ S Adding partie$ ................................................ - .............. - ...................................................................................................... 6 Appflc.ition Oita and Submission ........................................................ - ................ ....... - ....... - ........... - ..... - ...... - ..... - .......... 7 Contr.1ct0< Registr.ition Wortcflow Phases ......................................................... - ....... - ................ - ........................................... 7 Contractor Registration Apptft.ation IS$uance Process ............................................................................................................... 7 Registration A,ppJ1tatlon Review ............................................................................................................................................. 7 Regi.Stratlon lssoance ............................................................................................................................................................. 8 Registry features ........................................................................................................................................................................ 9 Contractor registration View .. H ....... - .................................................................................................................................... 9 Registration View ................................................ - ....... - ..... _ .................. - ........................ - .......... - .............. - ..................... 10 Registration view for applicants ........................ - ...... _ ................ - ........ - ....... - ..... - .................. - ............... - ..... _ ............. 10 A.egtstration View for Municipal Authorities .................................................................................................................... 11 Su:sn\Hs lnfotmation View ................................................................................ , ................................................... , ............. 12 Renewal and Revoke Management ..................................................................................................................................... 13 Notlfatlons and Alerts ....................................................................................................................................................... 14 Document Mana:gement .............. - ...................................................................................................................................... 14 Oala Import ..................................................................... - ....... _ ....... - ........ ,-........................................... ----· ....... 14 Late fee Minage.rnent .............................................................................................................................. _ ...... - ..... - .......... 14 Report Ma:nagement ............................................................................................................................................................. 1S Registration Reports ......... ............................................................................................................................................... l S Pavment Repons ............................................................................................................................................................. lS Review Repom ................................................................................................................................................................. lS Configuration Description ........... . _ ...... - ................. - ............................................................................................................... 1S Registration Person.as in Business Accounts .................................................................................................... - ...................... 18 Overview of User Pel'missions in 8usiness Accounts: ....................................................................................................... 18 CloudJ)1!1rmit Third..Party Integrated Svste<ns ........................................................................................................................... 1.9 Standard Configurable Third•Party Integrations ........................................................... , ....................................................... 19 Geographic Information Sv>t•m (GJSJ .................................................................................................................................. 19 @2023 Cloudpermlt Confidential
2 Online Payment ················ ······••H••············-·····••H••······ .... • .. ··••H••····· .. ••••••• ............................. ... ....... H••···••H••· .. ··········••H• 19 Authenliution throot1h Open ID Connect (O1DC) ................................................................................................................ 20 Multi-Factor Avthentit.atiof't (MFA) ····································-························••H••·····••H••··················-········-·············· 20 Additions and Minor Change-s to Third-PirtY lnlegrations .................................................................................................. 20 Custom lnt~grations .......................................................................................................... , ................................................. 20 Integrations with 8ackend Systems .................................................................... ,,, .............................................................. 20 lntegratiOns with EJectlOntc Archiv~s .................................................................................................................................. 21 Conduslon: EmPowering Efficient C-0ntn1cto.r Reg.istratlon with Ooudpermi.t .................................................................... 21 @2023 Clovdoermit Confidential
Cloudpermit Contractor Registration Product
Guide
This document provides an oveNiew of our Contractor Registration product, a component of the Cloudpermit product suite.
General Description
Cloudpermit provides an online community development software solution tailored for local governments, ensuring 24/7 accessibility. Our Software-as-a-Service (Saas) products are crafted to streamline and optimize community development processes. The suite encompasses various domains within local government operations including:
• Building Permitting: Facilitate building permits issuance, inspections, and compliance management. • Planning: Efficiently handle land-use planning and development applications. • land Use Permitting: Streamline land use permits approval and ensure zoning compliance. • Code Enforcement: Manage code enforcement activities effectively. • Licensing: Streamline the issuance and management of business licenses within your jurisdiction. • Contractor Registration: This guide focuses ol'! the Contractor Registration product, a tool for managing and verifying contractor- credentials.
Cloudpermit Core Benefits
Cloudpermit unifies the etltire process of building, licensing, planning e-permitting, and code enforcement case management under one digital roof. It brings all stakeholders • from applicants to authorities - onto a common platform, ensuring real-time updates on applications, licenses, and cases. Below are the primary benefits delivered by Cloudpermit:
• Digital Standardization: Cloudpermit embodies best digital practices, standardizing local government's operations in building, plaMing, code enforcement, and licensing.
• 24/7 Online Accesslbllity: Accessible on any browser or operating system, facilitating remote and on-site mobile work.
• Seamless Updates: Mo11thly releases bring automatic updates, delivering the latest enhancements without the need for manual downloads or installations.
• Swift Deployment: A cloud-based Saas product for quick and easy implementati:oit configured to match municipal requirements, hence easing the resource strain. • Interactive Maps: Utilize high-quality location data and updated property information sourced directly from the local government'$ Geographic Information System (GIS). • Collaborative Workspaces: Fosters instant collaboration and communication within applications and code enforcement cases, thus accelerating processes and improving workflows for all parties involved.
As you navigate through this guide, you'll find in-depth insights on how to make the most of the Contractor Registration product to manage and verify contractor credentials efficiently.
Cloudpermit Contractor Registration
Contractor Registration ('Registry') is a specialized module seamlessly integrated mto Cloudpermit to facilitate efficient management of contractor information. Whether you're a local government official overseeing registrations or a contractor keen on establishing your presence, this module provides an intuitive platform for effortless interaction. Utilize the @2023 Ctoudpermit Confidential
4 Contractor Registration to maintain an updated database of contractors within your jurisdiction and allocate them to specific building permits with ease.
Important Note: Information in this document may change without prior notice due to our continuous efforts to enhance our products in line with industry standards and valuable user feedback. Our regular releases, detailed within, will keep you informed about new features, enhancements, and non-security updates.
We trust this Product guide will be an invaluable resource as you explore the Contractor Registration module. For any inquiries, challenges, or aid, feel free to contact our dedicated support team. We are here to aid you in maximizing the benefits of Cloudpermit's offerings for your community development needs.
Contractor Registration Application Creation Wizard
The Cloudpermit Contractor Registration ('Registry) product provides a simple user interface for creating, applying for, reviewing, managing, and issuing business registrations.
Beginning the application creation
Since registry applications in Cloudpermit are not associated with projects, and some registry applications do not have a specific address or property, the application creation wizard accessib'e from the user dashboard assists applicants in creating the appropriate workspace for the registry application. ' My dashboard
0 Soloctclly
- 0 Select type ol appllcatton
A ..... pMffiil .. Meia..,.,.,._,.,..aNll10
~.ftnt"aW- ~'.l'C: ..... "19tlNUM
~•t:uli:! .. V1.J~9'll..,1htfd~~
A=" v:.
,rn
1 OOTO-O<Cl 1111111
- Applicants will choose the state and municipality to which they wUI submit their application. As a result, applicants can only submit application types permitted in the selected municipality. @2023 Cloudpermit Confidentfal
s
Applicants will select the registry category and trade(s) that best describes the purpose of their applications in the "Create a New Application" workspace. These choices will determine the application's requirements and process in Cloud permit. NOTE:
Create a new application
. ,.,..,........_ - Select type of registration and trades for your application _,,_
Daaie.lM,.._._,,_..~ ... ~tyt,alfll,.__.,.._. .... tJrw~WtN~,_,_,__,_ ... ~ .. NMt,.. .... lfl'POW....,_ Cltl:tl'Mdl ........... t#t ..... ..._......,...._..,,..~ 0--
An applicant can select multiple trades in one application.
D ~,-... c.c,..,_
0.....,..e.etc11r
D ,,_...Tri.,...,
0 ~OHt«wl
a_.__
Within Cloud permit, the contractor can be a private individual or a business. Furthermore, authorities can also apply for registrations on behalf of their customers. Municipalities can also create an online copy for those applications sent by paper or email.
Draft Contractor Registration application workspace
Once a contractor's application data is in place, applicants will be redirected to the draft contractor registration ('registry') application workspace. The "Required Tasks" progress bar displays the actions the applicant must take to complete and submit the registry application. These actions are related to the selected registry category type. -
-
New reglslrallon --
·-
- IWtJIUJD.Tl.:A""-CUIITlON
(!I IJlflUCAnoN Do\TA.
'11 ••~
@2023 Cloudpermit
• 4'
~,.,,.,. _,,,__ ........... ~ .... --... -,.__,,,, __ .,._ Confidential
-·
Adding parties
Applicants can add individuals and businesses to the Cloudpermit database as ~parties" within the "Parties to the Application" section of the application workspace.
Ill PARTIES TO THE APPLICATION Close ~
Mandatory rolea lor thla application
To assign a role, click on lhe dropdown arrow and choote the action you wish co perform. This wHI walk you through Che process of assigning an existing party 10 an appllcellon ~e or adding a new pally.
ASSIGN ROLES 0.
APPLICANT
JIM - ~
Additional parties
PROPERTY OWNER v
.111ne.-
To i" v,te add11ional parties 10 t><t lnvolvecl In or have access to tile app~catlon, elick tile •• · 1>111ton to add a someone with tlle,r email address and specilyl119 their role ADD OR INVITE PARTY +
Brown Corp (Jim /
Brown)
Wo<kspac:• .,..,or
Property owner Applicant
llm.btown.1est190gma
h.com
+ I 519·999·3805
6 Party invitations are sent to individual recipients via email. Upon acceptance, the new party can access and participate in the registry application, subject to limitations set by the application owner. However, all parties in the application will automatically have permission to access and read the application details. • When you add a person with an email address to your registry application, an invitation to collaborate will be automatically sent. The invitee may accept or decline the invite. • If you enter the party details manually because the party doesn't have an email account, the party will become active immediately, regardless of whether the invite is ignored, accepted, or declined. • If a business partner already appears in your account database, they will become active on the registry application once their data is added to the "Parties to the Application" feature. • If you invite a new business to your registry application, you will create a new business account and choose at least one role for the company. All members of the business can access and read the application data.
Business data can be managed in the "Business Information" view, accessible from the user dashboard. @2023 Cloudpermit Confidential
1 Application Data and Submission
The application data may require specific actions based on the registry category and trade(s) selected during the registry application creation. The municipal administrator determines this information during the Cloudpermit setup, ensuring the correct form for applicants is automatica~y added to the registry application. (!) AP!'UCATION DATA
;."C\ro,in.11iotll1o~aivt0m.1tk#'I
Al requhd t~s •• ff'l.111100 wiu.
Buslnes1 lnf0<maUon
After completing the required application information, applicants will digitally 5lgn off on the registry applications before submitting them to the municipal department via Cloudpermlt .
Contractor Registration Workflow Phases
The workflow for Contractor Registration ('Registry') is divided into two phases: Application and Archival. • Application Phase: begins once the applicant has completed and submitted the registry application to the municipality.
• Archival Phase: begins after the registration has been approved.
Municipal administrators can use Cloudpermit to set up an automated archiving system for all approved applications. These applications, as well as all associated data, are stored in the Cloudpermit database and are available at any time.
Contractor Registration Application Issuance Process
The municipal authorities will begin reviewing applicants' registry applications once submitted. The application issuance process includes the below-described action steps.
Registration Application Review
The application review begins when a registry application is submitted to the munictpal department.
DE Cl AAA TION
_,,Ol'l ... ~-f~l~•oit1,wt.,.-.1,11,11~.,_.._.-vt,tvoiw'#Cllll'lir~MN11it1 t;t,N'!,P11&.-.t'~lti•~l"~ .. ca.fif~•Wi¥10t ,;t'1N~.• .o,,,e1hf;t .,..,_.~ ... '-WtlOlt~C~~--,Pff,n(,.l .. (Dti!i:l'ffltO"-,...!°"'w,t1.Y9'~tMbc.-7o,w'IQO,~ ... _.t111_.,. l tNIUl~,n::.l1t1U"lf-- ~C)~ ...,l.-,gqooU\o11-.-otll P9~\l'ODIM4~Mllt;lfn,ic~.,a;tHt"IIJ'tt,::&lns...:1PICC:M9_... iM,.c;t,~lhll~~~r.,eocl:,IM;tlc.~,il'\ ""'-'blOU1~'1thlhAtnQ¢t1n'I' ¥'d...,I .. PMths.lr\.<IV•~C,,-lo>9,~'7fth)IOlit041'PC»Ct41Wra$'""°3lc,, I ~ S1Cl1'D IOAU J. I
Cloudpermit aids municipal departments in managing registry application submission reviews by offering a variety of review types that municipal administrators can customize within Cloudpermit, Examples include variations in application forms and attachment types.
@2023 Cloudpermit Confidential
Moreover, if the registry type necessitates it, municipal authorities can request additional reviews for the application by selecting the review type and assigning it to a suitable reviewer in the "Reviews" section of the registry application.
Upon completing registry application evaluations, the reviewer marks the forms and attachments as complete and records the results in Cloudpermit.
If there's a need for the applicant to alter the application forms or attachments, a change request will be submitted.
Cloud permit creates a task for applicants, which appears in their dashboard's "Task and Requests" section. Additionally, an email will be sent to applicants and business members informing them of the change request in the registry application workspace. The assigned reviewer verifies the changes provided in the workspace.
Registration issuance
Following a review of the registry application and the absence of any objections to registry issuance, the municipal authority prepares a registry bill that can be paid onllne or in person as instructed by a municipality.
FEES & PAYMENTS
ii+EHHM I AD04DOITlON.UU + I
U-IDCII
_, .. 7S
Oft.l fC1TAl
TOTAi.OW
175.00
1--11 CNtal.Blll ._ I tlDffi■
Additionally, the municipal authority prepares a registry permit using the preconfigured registry template. Municipal administrators configure the following default date input configuration settings based on municipal registry issuance practices to the registry template:
• Issue Date
• Valid From
• Expiration Date
" Contractor Aeglstratlon
"''"
....-.'--... -t...-..-..,c...;\-~
-··
8 These data input settings can be defined at the main registry level so that each category level inherits them. They can also be determined separately for each category.
@2023 Cloudpermit Confidential
9 Once the registry has been created, the registry application workspace includes a "Registry" section that houses the draft and issued registry permits with PDFs for the registry application. The permit is automatically issued once the municipal authority acknowledges receipt of the registry fee in Cloudpermit.
Additionally, Cloud permit sends automated emails to the workspace parties informing them that the registry permit has been issued.
REGISTRATION ~-
Atgl•tr•~~ lteued on St.atu1 RavlstraUan cartrfki1t•
2023~09-27, 12 00 p.m. f'lt:l.lf'd
Contractor Registration Features
The Cloudpermit Registration ('Registry') product encapsulates a range of features designed to streamline the registry workflow, enhance user interactions, and ensure efficient management of contractor data. These features include:
• Application, Registry View, and "My Businesses" View: Manage registry applications, review registered entities, and oversee business details.
• Renewal and Revoke Management: Handle renewals and revocations efficiently. • Notifications & Alerts: Receive real-time updates on application status, renewals, and other critical activitie$. • Document Management: Organize, store, and retrieve essential contractor registration documents. • Data Import: Import necessary data effortlessly, ensuring a smooth transition and data integrity. • Late Fees Management: Administer late fees for overdue renewals or other instances as per municipal poMcles. • Report Management: Generate irtd manage comprehensive report5 011 w ntractor registrations.
Contractor Registration View
The Contractor Registration ('Registry') view allows applicants and municipal authorit ies to find and keep track of issued registrations. The view is accessible via a widget from the user dashboard, ' Contractor registrations
SUA<:KIIEG1$'1RATIONS
Municipalities may have hundreds of active registrations in their registry. Cloudpermit simplifies the process of searching for, filtering, and sorting registrations in the registry workspace by providing a "Search" feature with various search and filter criteria. These include the following:
Free text search.
Registry status filters (expired, issued, or revoked).
Filter for selecting municipal departments.
Filter for selecting different action items. like open bills or inspections in applications.
Filter for searching for expiring registrations.
Filter for selecting trades
@2023 Cloudpermit Confidential
10 ' Contractor registrations (6)
11.1~.....C.'IOf'ICCIIIIM'l'N~I~~
-- CMdteNl'dl '°'' - Ae."'4, 111
I
..., ... _ -- ..,._
O.OWM CCIMrtuOI
u,MNJ-.. ... --- ~J ....... ---- __.._ ...... ~~M.1 ....... 1 ........ ,.,1,-ff.., VW.~JN......, ~---.., ..... " --- .___ ...... ....., ---- ·- ...... - - --.......,.6 ---_,... ---.... , ....... ..._.nam,.._tt
.,...,. ... ..,_a, --- ....... ~
..... -
The number displayed in the registry widget represents the number of valid registrations the user can access in the "Registry" view.
Selecting a sorting value from the drop-down list on the right under "Results" allows users to sort filtered registrations as cards. This feature applies only to the "List" view mode.
Registration View
The Registration view displays the issued registry applications for both applicants and municipal authorities in one centralized location.
Registration view for applicants
The Registration view enables users to view their issued registration data, like inspections, and request renewals for expiring permits. Applicants access the Registration view from their dashboard via the licensing widget.
To proceed, they must select the registration and click the Open Registration button on the registration card, redirecting them to the Registration view.
The Registration view comprises the Inspections section and the registration application workspace entry. Applicants can request a registration renewal by clicking the Renew Registration button situated at the top right of the workspace. @2023 Cloudpermit Confidential
eon""'°'~
New registration
111--
1 I
~flllllllW ...........
tlOo0.1'»'.lCOl 202)·01·08. 119•.m.
(11 APPUCAllON
C:U'UlfNT STEP: tSSUlO 5 f 5
- PAIITIES TO THE APPLICATION
APPUCATION DATA
Registration View for Municipal Authorities
°""".
0,,00 -
Authority users are redirected to the selected registration application workspace through the Registration view. The Registration view facilitates municipal authorities in following up on registration applications or renewing or revoking a registration. These options are accessible in each application workspace's More Actions drop down menu. -......-
New registration
Ed
• -..CA11011
•
tJ.MI.Nf t.UP Ilia.Ab 111
0 - Q
- - l'AATII$ TO THli APPUCATION
APPIJCATlON DATA
--
lj
- -- -·
- ·
Registrations hold validity for a defined period. Upon expiry or near expiry, the holder may request a renewal through the issued registration application. Municipalities can smoothly renew expired registrations by viewing current and historical registration data in one place in the application.
@2023 Cloudpermit Confidential
u
Occasionally, municipal authorities may need to cancel a valid registration for specific reasons. The Revoke feature is available in all issued applications in the Registration view.
Business Information View
The "Business Information" view is generated when a user adds an existing business as a party or invites a new business to the application workspace. Within this view, users can access business contact details, view associated applications, registrations, and manage business users through a user management section.
Once a business party is established in the "Parties to the Application• section, the business data within the "Business Information" view becomes readily available for use across registration applicatlons in Cloud perm it. 12 For convenient access, the ~My Businesses"' section is prominently displayed at the top of the applicant's dashboard after the creation of business parties. This section lists all current business parties linked to the app(icant's account, with each business account directly linked to its respective "Business Information" view, accessible by clicking the business name link.
The "Business Information" view includes contact information, a list of business contractor registration the business has, and expiring and revoked registrations. Furthermore, administrators of the business account have full access to all information in the ''Business Information" view. They can add new members (view-only access) and other administrators (fu11 access to the business data) in the ~users in Business• section. Administrators can also remove other administrators and members from the business account. However, a business account must have at least one administrator.
B_Visibile
Boorac, IIINJI~
CONTACT INFORMATION
B.V
St.alt
BUSINESS LICENSES
LiceJrSes
IIUS1N[SS IJCOIS'E
USERS IN BUSINESS
@2023 Cloudpermit
IIUSINESSUCDISE
Confidential
llut.l••H~t.r-.. ■
., •23;s;,1a9'J
ZOlJ-03-29 fl.20 p.m
13 Renewal and Revoke Management
Renewal and Revoke Management are integral to the contractor registration application workspaces.
The contractor registration renewal process applies to applicants and authorities who can apply for a registration renewal on behalf of their customers. The Cloudpermit system sends an email notification to all parties and business representatives in the most recent application workspace well before the registration expires, followed by another on the day the registration expires. The renewal process includes the following:
• Renewal of expired contractor registrations
• Renewal and late penalty fees
The contractor registration holder can create a renewal application for the expired registration in the contractor registration application workspace. The registration renewal fee is determined by the type of business and the municipality's fee schedule. Municipal authorities will manage contractor registration renewals in contractor registration applications by selecting the "Renew registration" option from the "More Actions" drop-down menu. _ ...,..,_
New registration
-
■ .vl'UCATIOII
- 9
- - MIITllS TO THI Al'PUCATION
APPUCATION DATA
_..,,_, _
--
--
- --·
-·
Municipal authorities may revoke valid registrations for specific reasons. The reason for the revocation must always be specified. The contractors and the parties in the most recent registration application workspace are notified by email that their registration has been revoked.
R,,;-,o1<e
]
@2023 Cloudpermit Confidential
Notifications and Alerts
Contractor registration renewal notification is triggered based on the municipality's configuration setting. The expiration not1f1cation will display on the user interface. Additionally, the system will send two email notifications: one a few days before the registration expiry and another on the expiration day. Municipal administrators can customize email notifications' frequency, notification type, and content.
Cloudpermit automatically sends contractor registration expiration notifications to all parties involved in the most recent application workspace. Renewal notifications submitted will also appear in the audit log for the "Registration" view.
Document Management
Cloudpermit generates all documents in downloadable and archivable PDF format by default. Contractor registration documents, such as uploaded attachments, permits, inspection visit results, contractor registration fee invoices, and receipts, are automatically saved to the respective workspace sections as PDF templates. ~ ,o~ Q r,...••.,... ....
__ .._......,,
New registration
-
HUt::aca,n-11•
The latest registration also appears in the application's workspace header, which is accessible at any time.
Data Import
Authority users can import previously issued business registrations and attachments into the Cloudpermit database.
This process involves uploading Excel sheet columns containing registration data, including registration number, registration holder, address, property ID, and municipality. Users can then map the Excel file to define a form that will appear in the workspace. A preview of the draft registration and workspace is available for users to review before importing data. Similarly, attachments for existing registrations can be imported seamlessly.
Upon importing a registration, Cloudpermit creates and links it to a permit (if required). The application workspace is constructed using form data from the registry import and attach men ts from their respective Excel sheets.
Late Fee Management
In the context of the contractor registration , businesses may sometimes incur penalties, specifically late fees, for delayed payments. Cloudpermit streamlines this process with automated late fee calculations, capable of managing potentially high volumes of late fee scenarios. The calculation of late fees is contingent on the type of business and the fee schedule established by the municipality. Cloudpermit accommodates the following types of late fees:
• One-time fees
• Recurring monthly fees
@2023 Cloudpermit Confidential
ts
Administrators have the flexibility to define these fees as flat or calculated, as well as set a maximum number of months for recurring monthly fees (ranging from 2 to 12). If a registration renewal is overdue, administrators can designate the late fee as "one-time• and add it as a new fee item to the registration bill. In cases of "recurring monthly" late fees, administrators can include a new fee item in the bill and calculate the number of months for which it has been overdue.
Late fees can be automatically calculated when a bill is generated, taking into account the registration's expiration date and considering bank holidays and weekends. Cloudpermit also altows municipalities to align registration fees with their established fee schedule.
Report Management
The contractor registration module enables municipal authorities to create basic reports for registered organizations in Cloudpermit.
•c::i,._,...
Reporting: Boone County, Contractor Registration
PHMITS MYMENTII Rf.VIEWS
Generating reports can assist a municipality in ensuring compliance, regenerating revenue, planning, allocating resources, and enhancing transparency and accountability.
Municipal authorities have the capability to generate reports related to registrations, payments, inspections, and reviews.
Users can select one report at a time and customize its time range, registration type (submitted/issued), and registration categories. Cloudpermit supports CSV and Excel spreadsheet report formats.
Registration Reports
Contractor registration reports enocompas'> both submitted applications and issued registrations. • Submitted Applications Report: This report provides a list of registration applications submitted within th@ selected time range, along with any other applied filters, such as registration category. • Issued Registrations Report: Here, you'll find a list of all applications with a given date within the time range and miltching any other filters, such as registration category.
Payment Reports
Payment reports include" Online Payments" (the default option) and "Fees and Payments." Review Reports
Report-type options for review reporting include reviews and review events.
Reviews Report: This report compiles a list of applications with a "Review start date" falling within the specified time range and aligning with any other applied filters, such as category or review name.
Review Events Report: Here, you'll find a list of applications with an "Event date" within the designated time range and matchi11g any other filters, such as category or review name.
Configuration Description
Below are the tables mustrating the configuration of Cloudpermit Contractor registration features. @2023 Cloudpermit Confidential
16 ) )' 11 H,)()'l
.,,t·c o 1 I r(~r 1.H)f) , : D(",( , it o
@2023 Cloudpermit Confidential
I ,., · , " ,,. • ·,·1•,.•1n,1C11111;q:1,1·,1·ois,
I , 11.•,•c;,o 1,, 1 H a11,1cll .,,, 1,s
@2023 Cloudpermit Confidential
18 Registration Personas in Business Accounts
A business is established when a user adds it as a party to an application. This action designates the user as an administrator within the business account. It's essential to note that a business account must always be maintained by at least one administrator. The administrator holds the authority to extend invitations to new administrators and members or remove them from the business account.
In Cloudpermit Contractor registration, there are two distinct personas: administrators and members. Each persona is assigned specific responsibilities or privileges tailored to workflows within the Contractor registration.
Overview of User Permissions in Business Accounts:
• Initially, the municipality that created the business account maintains editing permissions for business information, including user invitations, until the first admin invitation for the account is accepted. • Subsequently, the business account functions like any other, with only the designated business administrator having edit access.
• The first individual to receive an invitation becomes the administrator, It's only after an administrator party is included that the municipality's control can be revoked. • Administrators cannot self-remove from a business if they are the last administrators, preventing the business entity from being orphaned.
@2023 Cloudpermit Confidential
19 Cloudpermit Third-Party Integrated Systems
Cloudpermit offers a set of standard configurable integrations with over twenty (20) systems, grouped into distinct integration types as detailed below.
In situations where the specific integration requirement cannot be met through the standard configurable options, Cloudpermit may explore alternatives such as integrating a new system, making minor adjustments to existing integrations, or developing a custom solution. These specialized integrations are subject to separate pricing and, if relevant, will be discussed within your contract.
Standard Configurable Third-Party Integrations
Cloudpermit offers integrations with third-party systems that can be tailored to suit the client's needs as a standard part of the implementation process. It's important to note that these integrations may come with associated monthly or annual fees, which will be explicitly outlined in the contract.
Geographic Information System (GIS)
Cloudpermit provides support for a one-way integration with the municipal authority's Geographic Information System (GIS). The supported GIS integrations encompass the following platforms:
• ESRI ArcGIS
• CGIS
• CartoVlsta
• MunlSlght
Online Payment
Cloudpermit integrates with various online payment providers through checkout systems or gateways, enabling users to pay bills online when configured by a municipality. Payer info and bill details are securely sent to the payment provider, with payment success information returned. Supported integrations include:
• ACI
• Allpald
• Bambora
• CCP/NIC Online Payment
• ePay
• E-,cact
• Elavon
• Government Window
• Merchante
• Monerls
• MSB (Municipal Services Bureau)
• OpenEdge
• Payeezy
• Paymentus
• Pay Now link
• Point& Pay
@2023 Cloudpermit Confidential
20 • Square
• Stripe
Authentication through Open ID Connect (OIDC)
When a user's account is linked to an external system for authentication, Cloudpermit sends the authentication via an Open ID Connectivity (OIOC) API to a third-party login page. The entire authentication process occurs in the third-party system, which then signals successful authentication back to Cloudpermit. Please note that this integration does not cover authorization; all groups and permissions are still managed within Cloudpermit. Supported OIOC authentication integrations include:
• AzureAD
Additional AO integrations are priced separately and, if applicable, addressed within your contract.
Multi-Factor Authentication (MFA)
When Multi-Factor Authentication (MFA) is required for a department, Cloudpermit login mandates at least Two-Factor authentication. Following a successful Cloudpermit authentication, users are directed to a third-party system for the secondfactor authentication, which can be a mobile app or Security Management System (SMS). This third-party system must provide an OIDC (Open ID Connect) interface and subsequently relay the success of the second-factor authentication back to Cloudpermit. Supported MFA integration options include:
• Duo
Additions and Minor Changes to Third-Party Integrations Cloudpermit can incorporate integrations with new systems, provided they align with an existing integration type (e.g., Online Payment or GIS) and the third-party system offers Application Program Interfaces (APls) compatible with our current integration model.
Any integrations with new systems or minor alterations to existing system integrations will be subject to separate agreements and are not part of the standard implementation package. These integrations may Involve a development fee as well as annual or monthly charges.
Cloudpermit will provide an estimated release timeline for the integration upon reaching an agreement.
Custom Integrations
Integrations falling outside the scope of Configurable Standard integrations, minor modifications to eKisting integrations, or new systems within an existing integration type are categorized as Custom Integrations.
All custom integrations necessitate a feasibility study and the creation of specifications before an agreement can be reached. Cloudpermit will provide an estimated release time line for the integration upon agreement.
The implementation of a Custom Integration involves a development fee as well as annual or monthly charges.
Integrations with Backend Systems
In backend system integrations, Cloud permit employs a streamlined process for transmitting information to a backend system. This process involves the following key steps:
• Record Creation: Cloudpermit establishes a dedicated record within the backend system for each workspace. @2023 Cloudpermit Confidential
ll
• Property and Contact Unking: Cloudpermit links properties and contacts to their respective records, creating new contacts if needed.
• Status and Data Updates: Cloud permit ensures that record status and specified data fields are updated as required.
Additionally, the integration can be configured to encompass the transfer of fees to the backend system. It can also include the transfer of completed reviews and inspections. Implementing this integration may necessitate adjustments in the backend system and mapping statuses and codes between the two systems.
Please note that integrated backend solutions are subject to separate pricing, which will be detailed in your contract, Integrations with Electronic Archives
This integration method involves transmitting the contents of a workspace to an external system for archival purposes.
These external systems typically fall under the categories of Enterprise Content Management (ECM) or Electronic Archives.
The integration process is as follows:
• Archival Folder Creation: Cloudpermit establishes an archival folder within the third-party ECM or Electronic Archives system.
• Data Field Values: Cloud permit writes the values of the configured data fields into the archival folder. • Attachment Transfer: Configured attachments are transferred into the folder for archival purposes.
Please be aware that integrated electronic archive solutions are subject to separate pricing, which will be outlined in your contract.
Conclusion: Empowering Efficient Contractor Registration with Cloudpermit In this comprehensive user guide for Cloudpermit's Contractor Registration product, we've explored the various functionalities and features that empower munid pahties and contractors in managing and verifying contractor credentials sea mies sly.
From the initial application creation to renewal management and integration possibilities, Cloudpermit streamlines the entire process. Users can effortlessly add parties, access essential business information, and generate reports for compliance and planning. With the flexibthty of custom and standard integrations, Cloudpermit offers a versatile solution to meet diverse needs. Whether it's online payment processing. GtS integration, or electronic archival, Cloudpermit provides the tools for efficient contractor registration management.
@2023 Cloudpermit Confidential
Description
Cloudpermit Data Import allows the Customer to import the Customer's exi,sting legacy data (applications, permits, inspections, and attachments) into the Cloudpermit system.
The information in this document is subject to change without notice aligning with future releases.
Data Import Process
The data import process includes five (5) steps:
l. Exporting data from the Customer's existing system.
2. Adding the exported data into an Excel spreadsheet.
3. Reviewing the data in the spreadsheet.
4. Correcting possible errors in the spreadsheet.
5. Importing data into the Cloudpermit system.
Roles and responsibilities
1. Exporting data from existing system: Customer is responsible for exporting cleansed and normalized data from Its existing system into a CSV file format.
• Oata Cleansing: the process of fixing incorrect, incomplete. duplicate or otherwise erroneous data in a data set. • Data Normal'zat1on: the process of organizing data entries so they appear similar across all fields and records, making it possible to find, group and analyse the information.
2. Adding exported data into on Excel spreadsheet. Customer adds the data into the Cloud permit-provided Excel template. Customer is responsible that the data matches the Excel template's format.
3. Reviewing data. Cloudpermit does one round of reviewing the spreadsheet and provides information to Customer about possible errors in entry of the data to the Excel spreadsheet.
4. Possible correction of errors. Customer corrects possible errors and provides a cleansed Excel spreadsheet back to Cloudpermit.
5. Import data into Cloudpermit system. Cloud permit and Customer imports the data from the spreadsheet Into the Cloudpermit system.
After data has been successfully imported to Cloudpermit, the Customer can find and use the data in the Cloudpermit workspace section as if it would have been created in the Cloudpermit system. ©2023 Cloudpermit Confidential 2
Excel Spreadsheet and data requirements
In order for the content to operate properly within the Cloudpermit system, the exported data will need to be in certain required column and format. Cloudpermit provides an Excel template to Customers who are importing data. The examples below shows the required formatting for each import and field found within the Import Excel templates:
Workspace Import format requirements . . • Permit Numbar y[S TEXT OR NUMBER NlA C Locat:k>n YES mCTORNUMBER Mitch GIS fOtlNt
0 Mun.., ... ....., 110 rIJCTOR MJMHR NIA
E Roll Nul'T'IN:1/P"' YES TEXT OR NUMBER Matct\GISfOt'l'NI f Pffffllt dtteriation 110 TEXT OR NUMBER NlA
(i ClteHn, NO TEXT OR NUMBER Mia to CP UIHoriH
H Work ,ne 110 TEXT OR NUMBER MIDtoCPC1te10Ms
I Work Tat.Ht NO TEXT OR NUMBER Mao to CP C.atHories
J Wotk•ace Statu1 110 mer OR NUMBER MilotoCPCatnOM:s
• AlmnH IWorlu.aac•• NO TEXT OR NUMBER Mip to CP Uu,s
L Doto $11bMllto4 110 OATEANDTIME uu=-000000
M Date luuecl NO DAT( AND TIME MMIDO/'(YY 0000:00
N .......... NO TEXTORN~R NlA
0 Zonlna: NO TEXT OR NUMBER MJt<.h GIS format , Wortull NO nxT OR NUMBER NlA Q Gon,",Ktlon cost NO NUMBER N/A
R •• ... iant ftnt Name NO JEXT OR NUMIER lnltao
s Anlkantlltt"arne NO TEXT OR NUMBER lnitcao
T .a---cantll:l'ffladd-rfll NO TEXT OR NUMBER NIA
u Applk.ant 1,1nil numbH NO mer OR NUMBER N/A
V """llcantoo-.t- NO JfXT OR NUMBER N/A
w ADGlkant m1.1nlda•Utv NO TEXT oa NUMBER N/A
X ....... ~nt•ro\lfflc• NO mcr OR NUMBER NJA
y .annlk.iint coraoratkln ar Dartnushlo NO TEXT OR NUMIER lnit,aa z •••lkMI mobll. ....,...,., NO TEXT OR NI/MIER ,m, lOOMOOOC ,.,. ADDlkanl other DhDfle NO TEXT OR NUMBER UCXXI XXX·XXXX ,.. annlkanl tmlll NO TVCT OR NUMBER NIA AC Own..-flrstn.unit NO TEXT OR NVMB[R tnit,ap
AO Owne,a.stn~ NO TEXT OR NUMBER lnlwoo
AE Owr.er Rrffl addrew NO TEXT Oft NUMBER N/A
Af 0wnllf unk numNf NO TEXT OR NUMBER NJA
Ali Owntr aosl.111 code NO TEXT OR NVMBER N/A
All Owner mun--- NO TEXT OR NUMBER NIA
Al OWntr DfO'llftct NO TElCTORNVMIER N/A
IU Owner c:omoratlon or -rtnenf'IID NO TEXT OR NUMBD lnitt,10 AK owner mobU1 ohon• NO TEXT OR NUMBER CXXKI )()(K.)000( Al Owner othlf DhOM NO Tffi OR NUMBER IIIlll )00(.)000( AM OWn1r1maM NO lEXT OR NUMBER NIA
AN lulldtf ffnt name NO mcr OR NUMBER lnittH
AO luitde, last Hffill NO JEXT OR NUMBER lnitcan ,., lluUdtt' RNtt•ddnt1 NO TEXT OR NUMBER NIA AQ lluildef untt numb« NO TEXT OR NUMBER NIA
AR sun,., DOIUI cod• NO TEXT OR NUMIEA NIA
AS Build ... ma,nkiHlltll' NO TEXT OR NUMBER HIA
AT lulld1torovlnm NO TEXf OR NUMIER NIA
AU klhter co,oo,aHon or HnHrshlo NO TEXT OR NUMBER fl'lil.UD AV 1u•dttmoblle thHe NO TIXT OR NUMBER -IZI )001-JOOD(
AW BuHde, othtf 111hon1 NO TEXT OR NUMBER OIXXIJ00<,)000( AX lkllW•rema• NO TlXT OR NUMeER NIA
AY Pt-rffNt Commt1'1ti NO TEXT OR NUM8U HIA
•rnitcop = replace the first letter of every word in o chorocter string with on uppercose letter.
Inspection Import format requirements
I ,_N_ Yl$ TUTCHl:NUMl(lli N>A
C ..,_.Ion.._ m TEXT Olt HUMBER ~teC,-,..,o,e't'Mlrli
0 __ ,....,.,_ NO TUT OR NUMl(lt MIDtoUIIIIJUlb
' Sit• Cond;tlom NO TE~ Oft NUM8Ut Nl4
, •temllMot41 NO TmOIIHUMlllt .,. • 1n-1onO.t• NO OAT( AND TIM( uumprrn,C(ICIJ'(Q • - NO (MAIL USH IN Ct.Oll)f)( •• I .. orStatu1 HO TEXTOltNU"4:IER M1n10C,-5UhlM, ' ., __ NO mer 011 NUMIER NIA
' R-1.Mtted W'ls.Ktion s1ut time NO DATE A~DTIW UUfflnrYVV ll)1'.1)1Ja' ' (oft- ....... ,u .... NO O.TE .ANO TIME - Attachment Import format requirements I fl• Ntm■ YlS lEXTORNUMIElt •• C P«MH VIS TEXT OR NUMBER NIA • Anect.lNIIC TWOI HO TEXT Ok ..-tR Nl4
' OMataUoft NO U:.ll'T OR NUMBU .,.
©2023 Cloudpermit Confidentia I 3
AGENDA ITEM
November 7, 2023, City Council Meeting
Jon P
Adam Whelen, Public Works Director
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From: Adam Whelen, Public Works Director
Date: November 7, 2023
I SUBJECT
Allow Shasta County to apply for the SB 1383 Local Assistance Grant Program on behalf of the City of Anderson.
I RECOMMENDATION
The Public Works Director recommends that the City Council:
Consider allowing the Interim City Manager to sign the Letter of Authorization to allow Shasta County to apply for the SB 1383 Local Assistance Program on behalf of the City of Anderson.
!FISCAL IMPACT
There is no fiscal impact.
I DISCUSSION and BACKGROUND
SB 1383 is a California State Law that requires all food waste and organics to be diverted from landfills to reduce Green House Gas Emissions. All of Shasta County has not rolled out the SB 1383 program due to the lack of an organics waste processing facility. Although the organics and food waste diversion from the landfill is a significant part of SB 1383, a second portion of the law requires Edible Food waste to be diverted from the landfills. Currently, ITEM 8.9b PAGE1 11/7/2023
Tier 1 generators, which include grocery stores, wholesale food vendors, food service providers, and food distributors, are required to implement an edible food recovery program and develop a relationship with either a food bank or food recovery organization to divert the maximum amount of edible food possible from the landfill to those who can use it. Beginning January 1, 2024, this requirement extends to Tier II generators, which include restaurants, hotels, health facilities, large venues, events with food vendors, schools, and non-local entities.
Shasta County, the City of Shasta Lake, and the City of Anderson are all in a Joint Powers Authority (JPA) through Calrecycle. This means the three entities collectively submit one extensive report yearly for the SB 1383 Electronic Annual Report. The City of Anderson has been fortunate to work alongside Shasta County to reduce edible food waste. Shasta County oversees and conducts the edible food recovery portion of SB 1383 for the City of Anderson. Shasta County conducts all the site visits, phone calls, reporting, education, outreach, and regulation of the Tier I and Tier II Generators on behalf of the City of Anderson. Shasta County has come to the City of Anderson to ask permission to apply for this grant on the City of Anderson's behalf as a JPA to continue their efforts in complying with the state-mandated regulations on edible food waste diversion and recovery.
I ATTACHMENTS
1. Letter of Authorization
ITEM 8.9b PAGE2 11/7/2023
October 23, 2023
Shasta County Health and Human Services
Attn: Laura Burch, HHSA Director
2600 Park Marina Drive
Redding, CA 96001
RE: Letter of Authorization - CalRecycle SB 1383 Local Assistance Grant Program Fiscal Year 2022-23
I am the Interim City Manager of the City of Anderson. I am authorized to contractually bind the City of Anderson. Pursuant to this authority, I hereby authorize the County of Shasta to submit a Regional application and act as Lead Participant on behalf of the City of Anderson.
The County of Shasta is hereby authorized to execute all documents necessary to apply for, implement, and secure payment for the project under the SB 1383 Local Assistance Grant Program Fiscal Year 2022-23.
This authorization is effective as long as the Resolution is in effect.
Sincerely,
Jon Poletski
City of Anderson
Interim City Manager
[email protected]_s
530-378-6620
City Manager's Office
1887 Howard Street
Anderson, CA 96007
www.ci.anderson.ca.us Phone: (530) 378-6646
Fax: (530) 378-6648
AGENDA ITEM
!November 7, 2023, City Council Meeting!
Adam Whelen, Public Works Director
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From: Adam Whelen, Public Works Director
Date: November 7, 2023
!SUBJECT
Agreements pertaining to declared disaster 4308-DR.
I RECOMMENDATION
The Public Works Director recommends that the City Council:
Consider adoption of the attached Resolution authorizing the City Manager to execute for the City of Anderson an application and to file it with the California Governor's Office of Emergency Services to obtain certain federal financial assistance under Public Law 93-288 as amended by the Robert T. Stafford Disaster Relief and Emergency Assistance Act of 1988, and state financial assistance under the California Disaster Assistance Act.
1 FISCAL IMPACT
Repairs to damage associated with the storm events between February 1, 2017, and February 23, 2017, are eligible for reimbursement at 75% from the federal government and 18.75% from the state.
ITEM 8.9a PAGE1 11/7/2023
I DISCUSSION and BACKGROUND
On March 19, 2017, Governor Brown requested a major disaster declaration due to severe winter storms, flooding, and mudslides during February 1-23, 2017. The Governor requested a declaration for Public Assistance for 42 counties and Hazard Mitigation statewide. On April 1, 2017, President Trump declared that a major disaster existed in the State of California. This declaration made Public Assistance requested by the Governor available to state and eligible local governments and certain private nonprofit organizations on a cost-sharing basis for emergency work and repairing or replacing facilities damaged by the severe winter storms.
Anderson River Park sustained substantial damage during the high-water events on the Sacramento River associated with the February storm events. Staff is working with FEMA and CalOES to identify and execute projects to restore park facilities to pre-storm conditions. In addition, emergency response by the City during storm events is eligible for reimbursement.
Due to the recent retirement of City Manager Jeff Kiser, CalOES recommended we submit a new Designation of Applicants Agent for grant forms.
I ATTACHMENTS
1. Resolution
ITEM 8.9a PAGE2 11/7/2023
STATE OF CALIFORNIA
GOVERNOR'S OFFICE OF EMERGENCY SERVICES Cal OES ID No: ____ _ Cal OES 130
DESIGNATION OF APPLICANT'S AGENT RESOLUTION FOR
NON-STATE AGENCIES
BE IT RESOLVED BY THE CITY COUNCIL OF THE CITY OF ANDERSON (Governing Body} (Name of Applicant)
THAT _______________ PUBLIC WORKS DIRECTOR ,OR
(Title of Authorized Agent)
_T_H_E_C_IT_Y_M_A_NA_G_ER ____ , OR
(Title of Authorized Agent)
(Title of Authorized Agent)
is hereby authorized to execute for and on behalf of the CITY OF ANDERSON , (Name of Applicant) a public entity established under the laws of the State of California, this application and to file it with the California Governor's Office of Emergency Services for the purpose of obtaining federal financial assistance for any existing or future grant program, including, but not limited to any of the following:
- Federally declared Disaster (DR), Fire Mitigation Assistance Grant (FMAG), California State Only Disaster (CDAA), Immediate Services Program (ISP), Hazard Mitigation Grant Program (HMGP), Building Resilient Infrastructure and Communities (BRIC), Legislative Pre-Disaster Mitigation Program (LPDM), under - Public Law 93-288 as amended by the Robert T. Stafford Disaster Relief and Emergency Assistance Act of 1988, and/or state financial assistance under the California Disaster Assistance Act.
- Flood Mitigation Assistance Program (FMA), under Section 1366 of the National Flood Insurance Act of 1968.
- National Earthquake Hazards Reduction Program (NEHRP) 42 U.S. Code 7704 (b) ( (2) (A) (ix) and 42 U.S. Code 7704 (b) (2) (B) National Earthquake Hazards Reduction Program, and also The Consolidated Appropriations Act, 2018, Div. F, Department of Homeland Security Appropriations Act, 2018, Pub. L. No. 115-141 - California Early Earthquake Warning (CEEW) under CA Gov Code -Gov, Title 2, Div. l, Chapter 7, Article 5, Sections 8587 .8, 8587. 11, 8587.12 That the CITY OF ANDERSON . a public entity established under the (Name of Applicant)
laws of the State of California, hereby authorizes its agent(s) to provide to the Governor's Office of Emergency Services for all matters pertaining to such state disaster assistance the assurances and agreements required.
Cal OES 130 (Rev 3/9/22)
STATE OF CALIFORNIA
GOVERNOR'S OFFICE OF EMERGENCY SERVICES
Cal OES 130
Please check the appropriate box below
0 This is a universal resolution and is effective for all open and future disasters/grants declared up to three (3) years following the date of approval.
D This is a disaster/grant specific resolution and is effective for only disaster/grant number(s):. ______ _
Passed and approved this 7th day of November 20 23 ' -- Mayor Mike Gallagher
(Name and Title of Governing Body Representative)
Vice Mayor Stan Neutze
(Name and Title of Governing Body Representative)
Council Members: Susie Baugh, Dan Gallier and Melissa Hunt (Name and Title of Governing Body Representative)
C ERTi Fi CATiON
l,_C_h_r_is_ty_W_hi_te ____ ., duly appointed and City Clerk of (Name) (Title)
_C_IT_Y_O_F_A_N_D_E_R_S_O_N ______ ,, do hereby certify that the above is a true and (Name of Applicant)
correct copy of a resolution passed and approved by the CITY COUNCIL (Governing Body)
of the CITY OF ANDERSON on the 7th day of November , 20~ (Name of Applicant)
City Clerk
(Signature) (Title}
(Page 2 of 2)
Cal OES 130 (Rev 3/9 /22)
STATE OF CALIFORNIA
GOVERNOR'S OFFICE OF EMERGENCY SERVICES
Cal OES 130 - Instructions
Cal OE$ Form J30 lostrucfloos
A Designation of Applicant's Agent Resolution for Non-State Agencies is required of all Applicants to be ellglble to receive funding. A new resolution must be submitted If a previously submitted resolution Is older than three (3) years from the last date of approval, Is Invalid, or has not been submitted.
When completing the Cal OES Form 130, Applicants should fill in the blanks on pages 1 and 2. The blanks are to be filled in as follows:
ResolvU0o section;
Governing Body: This is the group responsible for appointing and approving the Authorized Agents.
Examples include: Board of Directors, City Council, Board of Supervisors, Board of Education, etc.
Name of Applicant: The public entity established under the laws of the State of California.
Examples include: School District, Office of Education, City, County or Non-profit agency that has applied for the grant, such as: City of San Diego, Sacramento County, Burbank Unified School District, Napa County Office of Education, University Southern California.
Authorized Agent: These are the individuals that are authorized by the Governing Body to engage with the Federal Emergency Management Agency and the California Governor's Office of Emergency Services regarding grants for which they have applied.
There are two ways of completing this section:
1. Titles Only: The titles of the Authorized Agents should be entered here, not their names. This allows the document to remain valid if an Authorized Agent leaves the position and is replaced by another individual. If "Titles Only" is the chosen method, this document must be accompanied by either a cover tetter naming the Authorized Agents by name and title, or the Cal OES AA Names document.
The supporting document can be completed by any authorized person within the Agency (e.g., administrative assistant, the Authorized Agent, secretary to the Director). It does not require the Governing Body's signature.
2. Names and Titles: If the Governing Body so chooses, the names and titles of the Authorized Agents would be listed. A new Cal OES Form 130 wm be required if any of the Authorized Agents are replaced, leave the position listed on the document, or their title changes.
(Page 1 of 2)
Cal OES 130 (Rev 3/9/22)
STATE OF CALIFORNIA
GOVERNOR'S OFFICE OF EMERGENCY SERVICES
Cal OES 130 - Instructions
Checking Universal or Disaster-Specific Box: A Universal resolution is effective for all past disasters and for those declared up to three (3) years following the date of approval. Upon expiration it is no longer effective for new disasters, but it remains in effect for disasters declared prior to expiration. It remains effective until the disaster goes through closeout unless it is superseded by a newer resolution.
Governing Body Representative: These are the names and titles of the approving Board Members.
Examples include: Chairman of the Board, Director, Superintendent, etc. The names and titles cannot be one of the designated Authorized Agents. A minimum of three (3) approving board members must be listed. If less than three are present, meeting minutes must be attached in order to verify a quorum was met.
certiflcattoo section;
Name and Title: This is the individual in attendance who recorded the creation and approval of this resolution.
Examples include: City Clerk, Secretary to the Board of Directors, County Clerk, etc. This person cannot be one of the designated Authorized Agents or Approving Board Member. If a person holds two positions (such as City Manager and Secretary to the Board) and the City Manager is to be listed as an Authorized Agent, then that person could sign the document as Secretary to the Board (not City Manager) to eliminate "Self-Certification." (Page 2 of 2)
Cal OES 130 (Rev 3/9 /22)
AGENDA ITEM
November 7, 2023, City Council Meeting
Approved for Submittal By:
Adam Whelen, Public Works Director
To:
Through:
Honorable Mayor and Members of the Anderson City Council Jon Poletski, Interim City Manager
From: Adam Whelen, Public Works Director
Date: November 7, 2023
!SUBJECT
Acceptance of a Public Service Easement on Parcel Map 22-02 for McMurry Drive.
I RECOMMENDATION
The Public Works Director recommends that the City Council:
Adopt a Resolution accepting the dedication of the offered five-foot-wide (5') public service easement based on the Planning Commission Resolution approval of the Tentative Parcel Map.
I FISCAL IMPACT
This action should not create any fiscal impact on the City.
ITEM 8.9c PAGE1 11/7/2023
I DISCUSSION AND BACKGROUND
On May 22, 2023, the Planning Commission approved the Metro Tentative Parcel Map 22- 02 by Resolution 23-05. The proposed project consists of a tentative parcel map for dividing one parcel into three (3) parcels. The parcels are in the 2800 block of McMurry Drive.
Typically, parcel maps do not need council approval before recordation. Since there is an offer of dedication of a five-foot-wide public service easement on McMurry Drive, the parcel map must be brought before the City Council to accept the offered easement.
The proposed final parcel map for PM 22-02 has been reviewed by the City Engineer and the City's Planner. The City Engineer has determined that the subdivision complies with the Subdivision Map Act.
The City Engineer has examined the final map and determined that the proposed map is substantially the same as it appeared on the tentative map that was approved in May 2023 and that all the provisions of the Anderson Municipal Code Chapter 16, Final Maps - Procedures and Contents and the Subdivision Map Act are technically correct and have been satisfied.
I ATTACHMENTS
1. Resolution
2. Parcel Map 22-02
3. Approved Tentative Parcel Map TPM 22-02
ITEM 8.9c PAGE2 11/7/2023
A TI ACHMENT l
RESOLUTION NO. 23-_
RESOLUTION OF THE CITY COUNCIL OF THE CITY OF ANDERSON AUTHORIZING ACCEPTANCE DEDICATION BETTY J. METRO (TRUSTEE) TO THE CITY OF ANDERSON FOR A FIVE FOOT (5') WIDE PUBLIC UTILITY EASEMENT
AS SHOWN ON PARCEL MAP 22-02
BE IT RESOLVED by the City Council of the City of Anderson to accept the dedication of a five-foot (5') wide public service easement located on McMurry Drive, as shown on Parcel Map 22-02.
PASSED AND ADOPTED by the City Council of the City of Anderson this 7th day of November 2023, by the following vote:
AYES:
NOES:
ABSTAIN:
ABSENT:
Michael Gallagher, Mayor
ATTEST:
Christy White, City Clerk
! In
... ,. Jf t•S 1·· I
ilii IQ!i 11111,
. ntn HIil mm
b ! I I
rn1111111 I .. lu11I ~
w w
SS 0
.... P 201-e20-0,e "-.P 201-620-019
, _____ ______ CG ----- •sw
w- wb w w w w - - w- - w w
. -~·-~···,-•·~;::·;:::7· S:llrXJ«rE
NC 7
p•,.c•A
0.73~res
31691.68 sq ft
""-/' m ~-- ~
J ... .. -
' -- \ . NC -
7~ ~
~,., ........ ,
tEGENO:
--Exl.-ior prOl)«ly hnG
--Proposed p,Optfly 1in ..
---- Exi,tin; nc:elin ..
~MMtn1 lines
E PowerlinM
-u- S.W.li""
- W- Wtlertjn•
0 F"ir ♦ HVdr•nt
1 .... 202,ee
w
f ~ i • ... 0
.... g
~'t.>w t <# ~,.. ... i : , , Ganyon
1 , ' AP 201-820-058 A.P 201-620-057 ,111 I\, ,,,'~ Orive~ ,' ... ... w
! _ _£:~&SY!_ ·-F---- - - - - - - - - - _fq&~ - ~·- - .. .... - - - ·-- - - - ·- ... 3; h .,P. SS - SS SS - - SS SS- W- <ti w w w w- - w- ~ w w w w - w-,.. - w w w . -.w w- w w w w w--v.. ____ McMurray Drive j • _ _ _ __ ~
~ Edgil,ot~I 3: ·
.~=:········--·-------···r--····------------"':::·~---h~--: r ~; ;.; ----.-;..,, .... 1~4r Parcel 8
0 731creo
~1.73,qh
A.P201-7
Record ularior
2 1&acres
.-.. ····-L . .......
T •lephOne end T .. eo,ei,h Eesemtnl
---r$i"'~ffl, ,_
,_ 1':111'13'..rE
le.&4 ,. N ~4G'W S210d'
AbU'IW'S Rigr(l 10 I~♦ S relinqutshed
s--Book 18$0.R. 248.
Scale 1 tnch = 40 feet
I I I iii7ii7 ~ ~ ~ ~ ~
"iiii'r
--c I
10Q' wldt e1ecL Tr-rra6l)f'I Ease~nl
per 786 OR 242
SYrS14#'E 17131'
;>(>•
~%'\ I ~ ',' -,:. ~ j ~1e11-- ~
/f \
J:, ; -
·'
'"'
,;
Interstate - 5
~ rdOwnet: AP1 2111-7
Bal1y J. Melro (TNSIN)
31128 Golf Drive
Rodd,fg. CA lle002 (530> 225-8773
AQent:
Lehmann and-.. C<>neulling Ftank Lolvnl/VI P.L.S. 5880
358 t-tartnel Ave. Ste -C"
Rodding CA. 96002 (5301241-2598
l'!oporty Si:M.
[""""9):one 2.1e -•~ c_...it 1 .... 0.n .... .,.,-
P!Oporty SlatllO: Vec:anl Und.,_ped land. with I WAPA
Tranuni:s:lion tawar and • faw Oak ......._
U1ifit ... • _ ,
-- PG&E CilyofMd....,,
c ;iyor -
Aerial Photo
Vicinity map
(N.T.S.)
TENTATIVE PARCEL MAP
for
Betty J. Metro. Trustee
ofthe B. Metro Marilal Trust Dated
June 14. 2018
in a fl()flion of
See. 45, P.B, Reading Grant
'" the City of Andenon
COUNTY OF SHASTA
STATE OF CALIFORNIA
Octobet' • 2022
• !:'.,~2,1.~ 358 Hartnell Ave • Suije ·c· Redding, California 96002 (530) 241-2596 Phone
[email protected]
SHEET 1:11
Attachment 3