Agenda packet — Modesto City Council, July 9, 2024 (part 1 of 12)

- 1 -
7/9/2024 5:30:00 PM

MODESTO CITY COUNCIL
www.modestogov.com
AGENDA
City of Modesto

CITY COUNCIL MEETING
Chambers, Basement Level
Tenth Street Place, 1010 10th Street
Modesto, California
Tuesday, July 09, 2024 at 5:30 PM
Roll Call - Councilmembers Alvarez, Bavaro, Escutia-Braaton, Ricci, Williams, Wright, Mayor Zwahlen
* Public Comment will only be in-person. Members of the public who wish to address the Council, by providing public comment, during the meeting must do so in-person in the Council Chambers.

As an alternative, members of the public may also provide written public comment submitted via email as indicated in the Submitting Comments by Email instructions on this agenda. Zoom will still be available for viewing and Wordly translation.
*Members of the public will be allowed to provide public comment through Zoom if a Councilmember is participating remotely pursuant to the provisions of Assembly Bill 2449. *Effective March 1, 2023, if a technical issue arises with Zoom or the phone dial-in option, the Council meeting will continue unless the meeting is being held pursuant to the provisions of Assembly Bill 2449. Alternative viewing options are listed below, and the meeting is physically open to the public.
“Wordly” can translate into 25+ different languages! To access written translation during the meeting, please scan the QR Code or click this link https://attend.wordly.ai/join/RJDY-6364.
"Wordly" puede traducir a más de 25 idiomas diferentes! Para acceder a la traducción durante la reunión, por favor escanee el código QR o haga clic en el enlace https://attend.wordly.ai/join/RJDY-6364.
- 1 -
7/9/2024
- 2 -
7/9/2024 5:30:00 PM
You may observe a livestream of the meeting at http://media.modestogov.com. You may also view or listen to the meeting as indicated below.

THE MEETING CAN BE VIEWED BY ZOOM VIDEO

CONFERENCING OR TELEPHONE
Joining the City Council meeting via Zoom
The City of Modesto is now offering the ability to view Council meetings via telephonic conferencing via “Zoom” video conferencing computer technology. The meeting may be accessed through the use of Zoom using the following options:
 Enter the following link into an Internet Browser
https://us02web.zoom.us/j/86945970570,
 Enter the following link into an Internet Browser https://zoom.us/ and using the Webinar ID 869 4597 0570
 Passcode 84326
To use Zoom, please visit: https://zoom.us/ and either sign-up for a free Zoom account or continue as a guest. Once you have downloaded the app onto your mobile device, joined from your web browser, or downloaded the Zoom software on your computer you will be ready for the upcoming Council meeting.

Joining the City Council meeting via Telephone
If you don’t have a smart phone or computer to access the meeting via Zoom, you can listen by phone, by calling 1-877-853-5257 (Toll Free) or 1-888-475-4499 (Toll Free) and enter the Webinar ID 869 4597 0570 Passcode 84326

SUBMITTING COMMENTS BY E-MAIL
Written comments may be submitted via email to: [email protected] (include Agenda Item Number in the subject line). All comments will be shared with the Councilmembers and placed in the record but will not be read aloud during the meeting. Written comments must be received two hours before the meeting.

This Agenda is on file in the City Clerk’s Office, Sixth Floor, 10th Street Place, Posting Board at entry of 10th Street Place, and is available on the City’s Web site at www.modestogov.com.

Materials related to an item on this Agenda submitted to the Council after distribution of the agenda packet are available for public inspection in the Clerk’s office during normal business hours. Such documents are also available online, subject to staff’s ability to post the documents before the meeting, at the following website https://www.modestogov.com/council-meetings In accordance with the requirements of Title II of the Americans with Disabilities Act (“ADA”) of 1990, the Fair Employment & Housing Act (“FEHA”), the Rehabilitation Act of 1973 (as amended), Government Code section 11135 and other applicable codes, the City of Modesto (“City”) will not discriminate against individuals on the basis of disability in the City’s services, programs, or activities. For more information, please visit the City of Modesto website at - 2 -
7/9/2024
- 3 -
7/9/2024 5:30:00 PM
https://www.modestogov.com/865/Americans-with-Disabilities-Act-ADA In compliance with the Americans with Disabilities Act, if you need special assistance to participate in this meeting, please contact the City Clerk (209) 577-5396. Notification 48 hours prior to the meeting will enable the City to make reasonable arrangements to ensure accessibility to this meeting.

Pledge of Allegiance to the Flag
Invocation: Mark Hammond, Celebration Center
City Clerk’s Announcements
Declaration of Conflicts of Interest
Reports from Closed Session

ACKNOWLEDGEMENTS AND PRESENTATIONS

1. Proclamation declaring July as National Parks and Recreation Month. (Funding Source: Not Applicable)
CITY COUNCIL; Ariana Harbottle-Jarrett, 209-571-5597, [email protected]

2. Proclamation declaring July as Plastic Free July. (Funding Source: Not Applicable) CITY COUNCIL; Ariana Harbottle-Jarrett, 209-571-5597, [email protected]

3. Proclamation declaring August 4-10, 2024 as National Health Center Week. (Funding Source: Not Applicable)
CITY COUNCIL; Ariana Harbottle-Jarrett, 209-571-5597, [email protected]

4. Proclamation declaring August 6th as National Night Out. (Funding Source: Not Applicable)
CITY COUNCIL; Ariana Harbottle-Jarrett, 209-571-5597, [email protected]

MISCELLANEOUS
Legislation, Appointments, Other

5. Consider accepting the resignation of David Seymour from the Landmark Preservation Commission (Funding Source: Not Applicable)
Staff Recommendation:
 Resolution accepting the resignation of David Seymour from the City of Modesto Landmark Preservation Commission
CED; Jessica Hill, 209-577-5267, [email protected]

6. Consider appointing David Barber, Margie Johnson, and Gloria Edith Verdin to the City of Modesto Citizen’s Housing and Community Development Committee with - 3 -
7/9/2024
- 4 -
7/9/2024 5:30:00 PM
terms expiring December 31, 2027 (Funding Source: Not Applicable) Staff Recommendation:
 Resolution appointing David Barber, Margie Johnson and Gloria Edith Verdin to the City of Modesto Citizens’ Housing and Community Development Committee with terms expiring December 31, 2027.

CED; Jessica Hill, 209-577-5321, [email protected]

7. Consider appointing Joan Clendenin to the City of Modesto Landmark Preservation Commission with term expiring December 31, 2027 (Funding Source: Not Applicable) Staff Recommendation:
 Resolution appointing Joan Clendenin to the City of Modesto Landmark Preservation Commission with a term expiring December 31, 2027 CED; Jessica Hill, 209-577-5267, [email protected]

8. Consider approving the appointments of Evan Yoshino as a Member-At-Large for a four-year term from January 1, 2024, to December 31, 2027 and Martin Montez as a Youth Member-At-Large for a one-year term from July 1, 2024 to June 30, 2025, on the City of Modesto Golf Courses Advisory Committee. (Funding Source: Not Applicable)
Staff Recommendation:
 Resolution approving the appointments of Evan Yoshino as a Member-AtLarge for a four-year term from January 1, 2024, to December 31, 2027 and Martin Montez as a Youth Member-At-Large for a one-year term from July 1, 2024 to June 30, 2025, on the City of Modesto Golf Courses Advisory Committee.

PRN; Jessica Franco, 209-577-5278, [email protected]

PUBLIC COMMENT IN PERSON
Three-minute time limit per speaker.

Only interested persons in the audience may present these matters. Under State law, Councilmembers may respond to matters being presented under this item only as follows:
a. Briefly respond to statements made or questions raised. b. Ask a question for clarification.
c. Provide a reference to staff or other resources for factual information. d. Request staff to report back at a subsequent meeting. e. Finally, a Councilmember or the Council itself may take action to direct staff to place a matter of business on a future agenda.

CONSENT ITEMS – ROLL CALL VOTE REQUIRED
Information concerning the consent items listed below has been forwarded to each Councilmember prior to this meeting for study. Unless some member of the audience or Councilmember has a question concerning an item and asks that it be withdrawn from the consent list, the Council approves the items at one time. The action taken by the Council in approving consent items is set forth in the explanation of this individual item. - 4 -
7/9/2024
- 5 -
7/9/2024 5:30:00 PM

CONSENT
An item may be removed from consent and discussed at the request of an audience member or Councilmember.

Consent

9. Consider approving the minutes for the June 25, 2024 Council Meeting. (Funding Source: Not Applicable)
Staff Recommendation:
 Motion approving the minutes for the June 25, 2024 Council Meeting.

CITY CLERK; Diane Nayares-Perez, 209-577-5396, [email protected] Consent

10. Consider accepting the 2024 Citywide Internal Controls Review Report. (Funding Source: Not Applicable)
Staff Recommendation:
 Motion accepting the Internal Controls Review Report
CITY AUDITOR; Colleen Rozillis, 206-302-6795, [email protected] Consent

11. Consider approving the purchase of a Public Safety Computer Aided Dispatch (CAD) system and associated public safety mobile and workstation licenses from Central Square Technologies for a total amount not to exceed $2,977,904. (Funding Source:

Measure H, Grant Funding)
Staff Recommendation:
 Resolution approving the competitive bidding process from the City of Glendale with Central Square Technologies, Lake Mary, FL for the purchase of a Public Safety Computer Aided Dispatch (CAD) system and associated components with Central Square Technologies for a total amount not to exceed $2,977,904; authorizing the City Manager or his designee to negotiate and enter into an agreement with Central Square Technologies; to carry out any necessary budget adjustments to implement the approved funding for the purchase and negotiate and enter into agreements with the County of Stanislaus, Stanislaus Regional 9-1-1 (SR911) and those agencies dispatched by SR911, allowing the agencies to use the CAD system at their cost.

CITY MANAGER; Scotty Douglass, 209-577-9149, [email protected] Consent

12. Consider approving the recommended Budget Adjustments to Fiscal Year 2023-24 Annual Operating and Capital Improvement Program Budgets. (Funding Source:

Various Funds)
Staff Recommendation:
 Resolution amending Fiscal Year 2023-24 Annual Operating and Capital Improvement Project Fund Budgets and authorizing the City Manager to take the necessary steps to implement the provisions of this Resolution.

BUDGET; Steve Christensen, 209-577-5390, [email protected] - 5 -
7/9/2024
- 6 -
7/9/2024 5:30:00 PM
Consent

13. Consider approving a First Amendment to the Memorandum of Understanding (MOU) with the Stanislaus Council of Governments (StanCOG) for Regional Early Action Planning Grant Program Funds. (Funding Source: Regional Early Action Planning (REAP) Grant Funds)
Staff Recommendation:
 Resolution approving a First Amendment to the Memorandum of Understanding with the Stanislaus Council of Governments for a suballocation of Regional Early Action Planning Grant Program Funds; and authorizing the City Manager, or his designee to sign the First Amendment to the Memorandum of Understanding.
 Resolution amending Fiscal Year 2024-25 Multi-Year project budget for project 100838 – Modesto General Plan Update in the amount of $219,654.13 to recognize the additional allocation under the Regional Early Action Planning (REAP) Grant, and fund certain housing-related work associated with the comprehensive General Plan update; and authorizing the City Manager, or his designee, to implement the provisions of this resolution.

CED; Sean Rando, 209-577-5473, [email protected]
Consent

14. Consider a one-year extension of the Transient Occupancy Tax Funding Agreement and the Modesto Tourism Marketing District Owners’ Association Agreement with Visit Modesto for Tourism Marketing Services. (Funding Source: General Fund) Staff Recommendation:
 Resolution approving a one-year extension of the Transient Occupancy Tax Funding Agreement with Visit Modesto, Inc. for Convention and Tourism Services, and authorizing the City Manager, or his designee, to execute the Agreement.
 Resolution approving a one-year extension of the Modesto Tourism Marketing District Owners’ Association Agreement with Visit Modesto, Inc. for Convention and Tourism Services, and authorizing the City Manager, or his designee, to execute the Agreement.

CED; Trevin Barber, 209-860-1251, [email protected] Consent

15. Consider accepting the Sutter Avenue Strengthen and Replace Water Mains Project as complete, releasing securities, releasing payments totaling $2,245,435 to West Valley Construction Company of Stockton, CA., and authorizing the City Clerk to file a Notice of Completion. (Funding Source: Water Fund)
Staff Recommendation:
 Resolution accepting the Sutter Avenue Strengthen and Replace Water Mains Project as complete, releasing securities, releasing payments totaling $2,245,435 to West Valley Construction Company of Stockton, CA., and authorizing the City Clerk to file a Notice of Completion.

ENGINEERING SERVICES; Peter Kambel, 209-577-5444, [email protected] - 6 -
7/9/2024
- 7 -
7/9/2024 5:30:00 PM
Consent

16. Consider approving Agreements with Burton Fire, Modesto, CA for the purchase of Fire Fleet Parts and Services for a total amount not to exceed $625,000 over five years. (Funding Source: General Fund and Outside Fire Contract Agencies) Staff Recommendation:
 Resolution approving the Agreements with Burton Fire, Modesto, CA for the purchase of Fire Fleet Parts and Services for a two-year Agreement with three one-year extension options, for an annual estimated amount of $125,000 and a total amount not to exceed $625,000 over five years; and authorizing the City Manager or his designee to execute the Agreements.

FINANCE DEPARTMENT; Dianne Love, 209-571-5164, [email protected] Consent

17. Consider approving the purchase of various Fleet Replacements for Public Safety Fleet Vehicles which include twenty-two Ford Interceptors and five Chevrolet Tahoes in an amount not to exceed $1,980,238. (Funding Source: Fleet Replacement Fund) Staff Recommendation:
 Resolution approving the Competitive Bidding Process from the State of California, Department of General Services to Folsom Lake Ford, Folsom, CA for the purchase of twenty-two Ford Police Interceptors for an amount not to exceed $1,374,633; and authorizing the Purchasing Manager, or her designee, to issue the Purchase Order; and authorizing the Purchasing Manager or her designee to execute any Change Orders not to exceed 15% of the total purchase price.
 Resolution approving the Competitive Bidding Process from the State of California, Department of General Services to Winner Chevrolet, Elk Grove, CA for the purchase of five Chevrolet Tahoes for an amount not to exceed $347,311 and authorizing the Purchasing Manager, or her designee, to issue the Purchase Order; and authorizing the Purchasing Manager or her designee to execute any Change Orders not to exceed 15% of the total purchase price.

FINANCE DEPARTMENT; Dianne Love, 209-571-5164, [email protected] Consent

18. Consider approving the Purchasing Agreements for the purchase of Equipment and Vehicle Parts and Services with Terex Services, Stockton, CA and Golden State Emergency Vehicle Services, Sacramento, CA for a total amount not to exceed $1,250,000 over five years. (Funding Source: Fleet Fund, Outside Service Agreements) Staff Recommendation:
 Resolution approving the Purchasing Agreements for purchase of Equipment and Vehicle Parts and Services with Terex Services, Stockton, CA and Golden State Emergency Vehicle Services, Sacramento, CA for a two-year Agreement with three one-year extension options, for an annual combined estimated amount of $250,000 and a total amount not to exceed $1,250,000 over five years; and authorizing the City Manager or his designee to execute the Agreements.

FINANCE DEPARTMENT; Dianne Love, 209-571-5164, [email protected] - 7 -
7/9/2024
- 8 -
7/9/2024 5:30:00 PM
Consent

19. Consider approving the Purchasing Agreements for the purchase of Equipment and Vehicle Parts and Services with CenCal Auto and Truck Parts, Modesto, CA and Rush Truck Center, Ceres, CA for a total amount not to exceed $1,000,000 over five years. (Funding Source: Fleet Fund, Outside Service Agreements) Staff Recommendation:
 Resolution approving the Purchasing Agreements utilizing the Competitive Bidding Process from Sourcewell and OMNIA Partners for the purchase of Equipment and Vehicle Parts and Services with CenCal Auto and Truck Parts, Modesto, CA and Rush Truck Center, Ceres, CA for a two-year Agreement with three one-year extension options, for an annual combined estimated amount of $200,000 and a total amount not to exceed $1,000,000 over five years; and authorizing the City Manager or his designee to execute the Agreements.

FINANCE DEPARTMENT; Dianne Love, 209-571-5164, [email protected] Consent

20. Consider approving the City of Modesto Pandemic Recovery Strategy – Modesto Forward Grant Agreements with Del Rio CC Foundation (First Tee – Central Valley) and the Boys and Girls Clubs of Stanislaus County, for $250,000 each and a total amount not to exceed $500,000 in American Rescue Plan Act Funding. (Funding Source: American Rescue Plan Act Funds)
Staff Recommendation:
 Resolution approving the City of Modesto Pandemic Recovery Strategy – Modesto Forward Grant Agreement with Del Rio CC Foundation (First Tee – Central Valley), in an amount not to exceed $250,000 in American Rescue Plan Act Funding, and authorizing the City Manager, or designee, to execute the Agreement.
 Resolution approving the City of Modesto Pandemic Recovery Strategy – Modesto Forward Grant Agreement between the City of Modesto and the Boys and Girls Clubs of Stanislaus County, in an amount not to exceed $250,000 in American Rescue Plan Act Funding, and authorizing the City Manager, or designee, to execute the Agreement.
 Resolution amending the Fiscal Year 2023-24 Non-Capital Project Budget to fund Project #101345 (American Rescue Plan Act Project) in an amount not to exceed $500,000 in transfers, revenue, and to budget expenditures to fund the Project, and authorizing the City Manager, or his designee, to implement the provisions of this Resolution.

PRN; Diane Sheatsley, 209-577-5418, [email protected] Consent

21. Consider approving the Culture Commission’s request to move forward in issuing its Request for Proposals calling for artists and muralists for Modesto’s 150th Anniversary Mural Project. (Funding Source: General Fund)
Staff Recommendation:
- 8 -
7/9/2024
- 9 -
7/9/2024 5:30:00 PM
 Resolution approving the Culture Commission’s request to move forward in issuing a Request for Proposals calling for artists and muralists for Modesto’s 150th Anniversary Mural Project.

PRN; Diane Sheatsley, 209-577-5418, [email protected] Consent

22. Consider approving a list of projects to be funded with Road Repair and Accountability Act tax proceeds for Fiscal Year 2024-2025. (Funding Source: Senate Bill 1 Funds) Staff Recommendation:
 Resolution approving the list of projects to be funded with Road Repair and Accountability Act tax proceeds in Fiscal Year 2024-2025 in an amount up to $5,888,194, and authorizing the City Manager, or his designee, to approve the projects.

PUBLIC WORKS; John Sphar, 209-342-2235, [email protected] Consent

23. Consider approving the Second Amendment with Champion Industrial Contractors Inc.

Modesto, CA for On-Call Plumbing Services increasing the Agreement amount by $120,000 for a new total amount of $552,370, within the term of the Agreement. (Funding Source: General Fund, Utility Funds, Centre Plaza, Golf Fund and Building Maintenance Fund)
Staff Recommendation:
 Resolution approving the Second Amendment with Champion Industrial Contractors Inc. Modesto, CA for On-Call Plumbing Services and increase the Agreement amount by $120,000 within the term of the Agreement for a new total amount of $552,370, and authorizing the City Manager, or his designee, to execute the Amendment.

PUBLIC WORKS; Gabe DaSilva, 209-577-5319, [email protected] Consent

24. Consider approving an Agreement with East Bay Municipal Utility District (EBMUD), Oakland, CA for the disposal of non-hazardous brine waste for a total amount not to exceed $352,450 over three years. (Funding Source: Water Fund) Staff Recommendation:
 Resolution approving an Agreement with East Bay Municipal Utility District (EBMUD), Oakland, CA for the disposal of non-hazardous brine waste for a total amount not to exceed $352,450 over three years; and authorizing the City Manager, or his designee, to execute the Agreement.

UTILITIES; Manuel Martinez, 209-342-4599, [email protected]

COUNCIL COMMENTS & REPORTS

CITY MANAGER COMMENTS & REPORTS
- 9 -
7/9/2024
- 10 -
7/9/2024 5:30:00 PM

HEARINGS
Published in the Modesto Bee on June 17, 2024 & June 24, 2024.

25. Hearing to consider approving the adoption of the Revised 2022 Modesto Sub-basin Groundwater Sustainability Plan and authorize the Stanislaus and Tuolumne Rivers Groundwater Basin Association Groundwater Sustainability Agency to submit the Revised 2022 Modesto Sub-basin Groundwater Sustainability Plan to the California Department of Water Resources. (Funding Source: Water Fund) Staff Recommendation:
 Resolution adopting a revised Groundwater Sustainability Plan and documenting the commitment to develop and implement a Well Mitigation Program and Management Actions in the Modesto Groundwater Subbasin.

UTILITIES; Timothy Barahona, 209-577-5485, [email protected]

MATTERS TOO LATE FOR THE AGENDA
These may be presented by members of the City Council and staff upon determination by a majority vote that an emergency exists, as defined by State law, or by a 2/3 vote that (1) there is a need to take immediate action, and (2) that the need for action came to the City’s attention after the agenda was posted.

ADJOURNMENT

CLOSED SESSION
Please take notice that a special Closed Session meeting of the Council of the City of Modesto has been called pursuant to Section 2-1.02 of the Modesto Municipal Code to be convened on TUESDAY, JULY 9, 2024 AT 4:45 PM
and after the regularly scheduled meeting in the Tenth Street Place, Chambers Conference Room, Basement Level, 1010 Tenth Street, Modesto, California.

Any and all of the following agenda items are subject to action being taken by the Modesto City Council.

The business to be considered at said City Council meeting shall consist of a Closed Session concerning the following:
- 10 -
7/9/2024
- 11 -
7/9/2024 5:30:00 PM

CLOSED SESSION
CONFERENCE WITH LEGAL COUNSEL – EXISTING LITIGATION
One Case (Pursuant to Section 54956.9(d)(1) of the Government Code) Name of Case: Magda Abraham v. City of Modesto, et al.

Superior Court of California, County of Stanislaus
Case No.: CV-18-003342
Posted pursuant to Government Code Section 54954.2 on the bulletin board at Tenth Street Place on
at by
date time signature
- 11 -
7/9/2024

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: June 3, 2024
TO: Mayor and City Council
THROUGH: Joseph P. Lopez, City Manager
FROM: Jessica Hill, Community and Economic Development
SUBJECT: Landmark Preservation Commission Resignation
CONTACT: Jessica Hill, Director of Community and Economic Development [email protected], 209-577-5267
DESCRIPTION:

Consider accepting the resignation of David Seymour from the Landmark Preservation Commission. (Funding Source: Not Applicable)
STRATEGIC PLAN ELEMENT:

This action supports the City’s Strategic Commitment, “Build Community trust in City Government through Responsive, Transparent and Efficient Service Delivery. Goal I. Promote Trust and Engagement between the Community and the City”.

BACKGROUND:

The Modesto Landmark Preservation Commission (LPC) serves as an advisory group to the City Council on matters related to City designated landmarks. Seven (7) members are appointed by the City Council for a 4-year term, starting January 1st and ending December 31st.

Section 11021 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions with the recommendation of the City’s Appointments Committee.

DISCUSSION:

On December 5, 2023, by Resolution No 2023-515, David Seymour was appointed to the Landmark Preservation Commission with a term expiration date of December 31, 2027. On June 3, 2024, David Seymour formally resigned from the Landmark Preservation Commission.

FISCAL IMPACT:

There is no fiscal impact related to this action.

COMMITTEE RECOMMENDATION:

This item did not go to committee, all resignations go directly to City Council for acceptance. 1 https://library.municode.com/ca/modesto/codes/code_of_ordinances?nodeId=CHTR_ARTXIAPBOCO_S1102APTE #5..
- 12 -
City Council. July 9, 2024
Landmark Preservation Commission Resignation
RECOMMENDED COUNCIL ACTION:

Staff Recommendations:

Resolution accepting the resignation of David Seymour from the City of Modesto Landmark Preservation Commission.

Approved by:

Jessica Hill, Director of Community &
Economic Development
Joseph P. Lopez, City Manager
Attachments:

1. Resolution

2. David Seymour Resignation Letter
#5..
- 13 -
1 2024- 20

MODESTO CITY COUNCIL
RESOLUTION NO. 2024-XXX

RESOLUTION ACCEPTING THE RESIGNATION OF DAVID SEYMOUR

FROM THE CITY OF MODESTO LANDMARK PRESERVATION

COMMISSION
WHEREAS, the Landmark Preservation Commission was established to advise City Council on matters related to historic structures and other resources in addition to policies and practices pertaining to preservation of Modesto'slandmarks, and
WHEREAS, on December 5, 2023, by Resolution No. 2023-515, David Seymour was appointed to serve as a member of the Landmark Preservation Commission, and
WHEREAS, David Seymour has tendered his resignation from the Landmark Preservation Commission effective June 3, 2024.

NOW, THEREFORE, BE IT RESOLVED that the Council of the City of Modesto hereby accepts the resignation of David Seymour from the City of Modesto Landmark Preservation Commission with regret.
#5..
- 14 -
2 2024- 20
The foregoing resolution was introduced at a regular meeting of the Council of the City of Modesto held on the 9
th day of July 2024, by Councilmember ?, who
moved its adoption, which motion being duly seconded by Councilmember ?, was upon roll call carried and the resolution adopted by the following vote:

AYES: Councilmembers: ?
NOES: Councilmembers: ?
ABSENT: Councilmembers: ?
ATTEST:

DIANE NAYARES-PEREZ, CMC, City Clerk
(SEAL)
APPROVED AS TO FORM:

BY:

JOSE M. SANCHEZ, City Attorney
#5..
- 15 -
Submission ID: af9474d6-7992-4d97-a612-25c4afb60b09 Page 1/1 Citizen's Advisory Group Letter of Resignation Submittal 06/03/2024 8:09 AM (PDT)
Citizen Advisory Group Letter of Resignation
Title II Compliance
In accordance with the requirements of Title II of the Americans with Disabilities Act (“ADA”) of 1990, the Fair Employment & Housing Act (“FEHA”), the Rehabilitation Act of 1973 (as amended), Government Code section 11135 and other applicable codes, the City of Modesto (“City”) will not discriminate against individuals on the basis of disability in the City’s services, programs, or activities. For more information, please visit the City of Modesto website.

Name David Seymour
Phone Number
Email Address
Mailing Address
City Turlock
State CA
Zip Code 95382
Which Citizen Advisory Group are
you resigning from?
Landmark Preservation Commission
Why do you want to resign from
this Citizen Advisory Group?
I am no longer living in Modesto. I would love to stay and advise if possible.

Signature
Thank you for providing this information. After clicking ‘Submit’ you will receive a Submission ID number that can be retained for future reference.

You will be updated by our staff, if necessary, as your resignation form is processed.

Have a great day!
#5..
- 16 -

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: June 6, 2024
TO: Mayor and City Council
THROUGH: Joseph P. Lopez, City Manager
FROM: Jessica Hill, Director of Community and Economic Development SUBJECT: Appointments to the Citizens’ Housing and Community Development Committee CONTACT: Jessica Hill, Director of Community and Economic Development [email protected] , 209-577-5321
DESCRIPTION:

Consider appointing David Barber, Margie Johnson, and Gloria Edith Verdin to the City of Modesto Citizen’s Housing and Community Development Committee with terms expiring December 31, 2027. (Funding Source: Not Applicable)
STRATEGIC PLAN ELEMENT:

This action supports the City’s Strategic Commitment, “Build Community trust in City Government through Responsive, Transparent and Efficient Service Delivery. Goal I.

Promote Trust and Engagement between the Community and the City”.

BACKGROUND:

The Modesto Citizens’ Housing and Community Development Committee (CH&CDC) consists of 11 members appointed by the City Council for a 4-year term. The CH&CDC serves as an advisory group to the City Council on matters related to housing and community development.

The CH&CDC provides an overall review of the City's Housing and Urban Development (HUD) funds. The committee makes funding recommendations to the Modesto City Council regarding the HUD Community Development Block Grant, Emergency Shelter Grant, and Home Investment Partnership Grant programs.

Section 11021of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions with the recommendation of the City’s Appointments Committee.

DISCUSSION:

Committee Member Julie Scherer’s second term has expired, and she is not eligible for reappointment. The initial terms for Committee Members Kyle Fliflet and Dewey Bedford have also expired leaving a total of three vacancies on the Citizens’ Housing and Community Development Committee. These vacancies are to be filled by prospective 1 1
https://library.municode.com/ca/modesto/codes/code_of_ordinances?nodeId=CHTR_ARTXIAPBOCO_S1102APTE #6..
- 17 -
City Council, July 9, 2024
Appointments to the Citizens’ Housing and Community Development Committee

Page 2 of 2 ends

candidates, recommended by the Appointments Committee, with final approval by the City Council. The approved candidates would be appointed to the CH&CDC with a term expiration date of December 31, 2027 to align with the terms of the CH&CDC by laws.

Outreach for the Citizens’ Housing and Community Development Committee vacancies included posting the opportunity in the Modesto Bee and sharing it on the City’s various social media platforms by the City’s Community and Media Relations Team.

Citizen applications for vacant committee positions are accepted online and those considered were received between August 2023 and May 2024. All applicants demonstrated interest in various committees, including the Citizens’ Housing and Community Development Committee.

A total of ten (10) applications were included for Committee consideration, eight of which were new and two (2) of which were requests for reappointment for a second term. Staff verified all ten (10) individuals were qualified to serve in accordance with the CH&CDC bylaws and were still interested in the opportunity.

FISCAL IMPACT:

There is no fiscal impact related to this action.

COMMITTEE RECOMMENDATION:

On June 5, 2024, the Appointments Committee reviewed the applications and recommended the appointment of David Barber, Margie Johnson, and Gloria Verdin to the Modesto Citizens’ Housing and Community Development Committee to fill the three (3) vacancies with terms expiring December 31, 2027, and forwarding to Council for approval.

RECOMMENDED COUNCIL ACTION:

Staff Recommendations:

Resolution appointing David Barber, Margie Johnson and Gloria Edith Verdin to the City of Modesto Citizens’ Housing and Community Development Committee with terms expiring December 31, 2027.

Approved by:

Jessica Hill, Director of Community & Economic
Development
Joseph P. Lopez, City Manager
Attachments:

1. Resolution

2. Citizen’s Housing and Community Development Committee Bylaws

3. David Barber, Margie Johnson, and Gloria Verdin’s Application #6..
- 18 -
07/09/2024/CED/Hill 1 2024-

MODESTO CITY COUNCIL
RESOLUTION NO. 2024-

RESOLUTION APPOINTING DAVID BARBER, MARGIE JOHNSON, AND GLORIA EDITH VERDIN TO THE CITY OF MODESTO CITIZEN’S HOUSING

AND COMMUNITY DEVELOPMENT COMMITTEE WITH TERMS EXPIRING DECEMBER 31, 2027
WHEREAS, Section 1102 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions; and WHEREAS, Citizens’ Housing and Community Development Committee member Julie Scherer’s second term expired on December 31, 2023; and WHEREAS, Citizens’ Housing and Community Development Committee member Dewey Bedford’s initial term expired on January 1, 2024; and WHEREAS, Citizens’ Housing and Community Development Committee member initial Kyle Fliflet’s term expired on January 1, 2024; and WHEREAS, three vacancies currently exist on the Citizens’ Housing and Community Development Committee; and
WHEREAS, a total of ten applications were received, eight of which were new and two of which were requests for reappointment for a second term; and WHEREAS, the Appointments Committee met on June 5, 2024, reviewed the applications, and recommended the appointments of David Barber, Margie Johnson, and Gloria Edith Verdin to the Citizen’s Housing and Community Development Committee.

NOW, THEREFORE, BE IT HEREBY RESOLVED by the Council of the City of Modesto that it herby appoints David Barber, Margie Johnson, and Gloria Edith Verdin who are all citizen’s at large to the City of Citizen’s Housing and Community Development Committee with a term expiring December 31, 2027. #6..
- 19 -
07/09/2024/CED/Hill 2 2024-
BE IT FURTHER RESOLVED, the City Clerk is hereby directed to transmit a copy of this resolution to the appointed members of the Citizen’s Housing and Community Development Committee, and the Secretary thereof.

The foregoing resolution was introduced at a regular meeting of the Council of the City of Modesto held on the 9th of July, 2024 by Councilmember , who moved its adoption, which motion being duly seconded by Councilmember , was upon roll call carried and the resolution adopted by the following vote:

AYES: Councilmembers:

NOES: Councilmembers:

ABSENT: Councilmembers:

ATTEST: ___________________________
DIANE NAYARES-PEREZ, CMC City Clerk
(SEAL)
APPROVED AS TO FORM:

BY: ____________________________________
JOSE M. SANCHEZ, City Attorney
#6..
- 20 -

Page 1 ends

CITIZENS' HOUSING & COMMUNITY DEVELOPMENT COMMITTEE
BYLAWS
(Amended: November 24, 2015, Resolution No. 2015-457)
Article I. Definitions
Section 1.01 There is a Committee created to be known and designed as the Citizens’ Housing and Community Development Committee.

Section 1.02 As used in these Bylaws, unless a different meaning clearly appears from the context:
(a) “Member” shall mean a member of the Citizen’s Housing & Community Development Committee.
(b) “Citizens’ Housing & Community Development Committee” and “Committee” shall mean the Citizens’ Housing & Community Development Committee.

Article II. Objectives
Section 2.01 The Committee shall be responsible for providing overall review of the City of Modesto’s (City) housing programs and making policy and funding recommendations regarding the City’s housing and Community Development Block Grant (CDBG) and Emergency Solution Grant (ESG) funded programs to the City Council.

Article III. Membership
Section 3.01 The Citizens’ Housing & Community Development Committee shall consist of eleven (11) qualified persons comprised of the following:

Seat Designation Term
Councilmember (appointed by the Mayor) 4 years
Councilmember (appointed by the Mayor) 4 years
Housing Rehabilitation Loan Committee Representative 4 years City Planning Commission Representative 4 years
Human Relations Committee Representative 4 years
Citizen-at-Large 4 years
Exhibit "A"
#6..
- 21 -

Page 2 ends

Citizen-at-Large 4 years
Citizen-at-Large 4 years
Citizen-at-Large 4 years
Citizen-at-Large 4 years
Citizen-at-Large 4 years
#6..
- 22 -

Page 3 ends

Section 3.02 The Members of the Committee shall reside within the City limits of the City at the time of appointment and must maintain residence within the City at all times during their service on the Committee.

Section 3.03 No Member of the Committee shall be an employee of the City, nor any bargaining unit for employees of the City, nor a person who receives compensation from the City.

Section 3.04 All appointments shall be made by the City’s Appointments Committee.

Section 3.05 No Member of the Committee shall be a relative, by blood marriage within the third degrees of the Mayor, Councilmember, Charter Officer or any department director or deputy department director.

Section 3.06 One Member of the Committee shall be appointed as an alternate to the Housing Rehabilitation Loan Committee by the Committee Chairperson.

Section 3.07 All Members must complete a Statement of Economic Interest (Form 700) by April 1 of each year and when assuming or leaving Committee membership.

Article IV. Terms of Office
Section 4.01 Members may serve no more than two (2) terms.

Section 4.02 Full terms are four (4) years in duration.

Section 4.03 A partial term of two (2) or more years shall be considered a full term for purposes of Section 4.01.

Section 4.04 Full term appointments begin on January 1 and expire on December 31 four (4) years subsequent.

Section 4.05 Members may be reappointed after their initial term. Members serving two (2) consecutive terms may be reappointed after a break in service of twelve (12) months.
#6..
- 23 -

Page 4 ends

Section 4.06 Members not eligible for reappointment may continue to serve until their successors are appointed. No member shall serve more than eight (8) consecutive years, with the exception of those who are serving until their successors are appointed.

Section 4.07 The Members of the Committee shall receive no compensation for the performance of their official duties.

Section 4.08 Appointments to fill vacancies on the Committee shall be handled in the same manner as original appointments. When a vacancy occurs during a term, the appointment to full such vacancy shall be for the unexpired portion of the term.

Section 4.09 Members of the Committee may be removed by a majority vote of the City Council after a recommendation by the Committee Chairperson for the following reasons:
(a) Misconduct, inefficiency, or willful neglect in the performance of their duties providing the member is first provided in writing the reasons for such removal and gives the member the opportunity to be heard before the City Council in their own defense. (b) Refusal to resign from the Committee when no longer a resident of the City or when a conflict of interest exists.

Article V. Attendance at Meetings
Section 5.01 It shall be the responsibility of each Member to know the dates and times of all Committee meetings. If a Member knows he or she will not be able to attend a regularly scheduled meeting, it shall be his or her responsibility to notice the Committee Secretary at least forty-eight (48) hours in advance of the meeting, in order for the absence to be recorded as an excused absence.

Section 5.02 The minutes of each meeting will list those Members in attendance, those who are excused and those who are unexcused.

Section 5.03 Timely attendance at meetings is expected and necessary to carry out the mission of the Committee. Three (3) or more consecutive unexcused absences are grounds for removal of a Member from the Committee by the City Council. #6..
- 24 -

Page 5 ends

Article VI. Officers and Their Duties
Section 6.01 Officers shall consist of a Chairperson, as appointed by the Mayor, and a Vice-chairperson, elected by a majority vote of the members of the Committee. Officers shall serve a four-year term.

Section 6.02 All officers shall exercise all privileges of membership, including the making of motions, seconding and debate.

Section 6.03 The Chairperson shall preside at all meetings, shall appoint all ad-hoc committees, and shall ensure that the bylaws, rules and regulations as adopted by the Committee are properly enforced
Section 6.04 The Vice-chairperson shall assist the Chairperson in his/her duties and in the absence of the Chairperson shall perform all duties usually performed by the Chairperson.

Section 6.05 The Committee Secretary shall be a City staff member, appointed by the Community & Economic Development Department, to serve as secretary to the Committee. The Committee Secretary shall keep a record of the minutes of all Committee meetings and such other duties as are usually performed by a secretary.

Article VII. Meetings
Section 7.01 Special meetings shall be called by the Chairperson as necessary.

Section 7.02 Notices of all meetings, including agendas, shall be given to all Members of the Committee, to the City Clerk, to the City Manager, and to all others as provided by law. All such notices shall be furnished to the Committee in writing at least seventy-two (72) hours prior to the time of such meeting.

Section 7.03 All meeting agendas will be posted at Tenth Street Place.

Section 7.04 All meetings shall comply with the requirements of the Ralph M. Brown Act.

Section 7.05 A quorum is necessary for the Committee to transact any business. A quorum shall be defined as a simple majority of active Committee members which is one-half of the active members plus one.
#6..
- 25 -

Page 6 ends

Section 7.06 All meetings of the Committee shall be open to the public and shall be held at a public facility, which is accessible in accordance with the regulations of the Americans with Disabilities Act.

Article VIII. Order of Proceedings
Section 8.01 Sturgis’ Standard Code of Parliamentary Procedure shall be the guide for the parliamentary procedures in the conduct of Committee meetings.

Section 8.02 The order of proceedings of all meetings shall be as follows, subject to majority vote of the members present:
(a) Roll Call
(b) Declaration of Conflict of Interest
(c) Public Comment Period
(d) Consent Items
(e) Old Business
(f) New Business
(g) Committee Comments & Reports
(h) Matters Too Late For the Agenda
(i) Adjournment
Section 8.03 Members of the public shall not speak unless recognized by the Chairperson and shall state their names before making any statement, which shall become a part of the public record. The Chairperson may remove any person who refuses to follow these rules or the decision of the Chairperson.

Article IX. Amendments
Section 9.01 The Bylaws and any future amendments shall be subject to the final approval of the City Council and shall not and are not intended to go beyond any of the powers and duties given to the Committee by the City Council. #6..
- 26 -
1 Cynthia Formosa
From: Erica Hunt
Sent: Tuesday, August 15, 2023 12:31 PM
To: Cynthia Formosa
Cc: Sydney Bettencourt
Subject: FW: Online Form Submission #40140 for Boards, Commissions & Committees Application
From: [email protected] <[email protected]>
Sent: Tuesday, August 15, 2023 12:29 PM
To: Optimize <[email protected]>; Jessica Hill <[email protected]>; Erica Hunt <[email protected]>
Subject: Online Form Submission #40140 for Boards, Commissions & Committees Application External Email: Please use caution when clicking links and/or opening attachments.

Boards, Commissions & Committees Application
Title II Compliance
In accordance with the requirements of Title II of the Americans with Disabilities Act (“ADA”) of 1990, the Fair Employment & Housing Act (“FEHA”), the Rehabilitation Act of 1973 (as amended), Government Code section 11135 and other applicable codes, the City of Modesto (“City”) will not discriminate against individuals on the basis of disability in the City’s services, programs, or activities. For more information, please visit the City of Modesto website.

Apply To: Citizens Housing & Community Development Committee First Name David
Last Name Barber
Address
City
State
Zip Code
Home Phone
Work Phone
Email Address
#6..
- 27 -
2 Occupation Senior Consultant
Employer / Business Infor
Business Address 641 Avenue of the Americas
City New York
State NY
Zip Code 10011
Education Bachelor of Science in Business Administration, Economics - University of Nevada, Reno
(Section Break)
Qualifications:

Do you have relatives or a
member of your household
who are employed by the
City of Modesto, or who are
currently serving on the City
Council, or who are Board
members or
Commissioners?
No
List relevant employment,
training, and experience,
certificates of training,
licenses, and professional
registration.
3+ years public sector consulting experience
How did you learn about
the board for which you are
applying?
Other (Please specify)
If other, please specify: Linkedin
Describe your involvement
in community activities and
civic organizations. (Do not
list partisan political
parties.)
Volunteer, Central Valley Tykes & Trykes
What is it about this
position that interests you?
I have a passion for urban planning and community
development. Since moving to Modesto in 2020 I have learned to love this community, and ended up purchasing a home here.

There are some issues facing the region and a great need for more affordable housing, housing for the homeless, and
additional housing downtown. I would love to be a part of the solution and help the community develop in a sustainable and inclusive manner.

What qualities, experience,
and expertise would you
bring to it?
With years of experience in public sector consulting, I am a passionate and skilled communicator with a strong desire to see the community grow in a positive way. In addition, I have prior experience in commercial real estate and construction along with expertise in current land use, smart growth, and land development practices.
(Section Break)
Demographics
#6..
- 29 -
4 City of Modesto invites all applicants to voluntarily self-identify their gender, race/ethnicity, veteran status and disability. Submission of this information is voluntary and refusal to provide will not affect the application process. The information will be kept confidential and will only be used in accordance with the provisions of applicable laws, executive orders and regulations, including those that require the information to be summarized and reported to the federal government for civil rights enforcement.

Apply To: Citizens Housing & Community Development Committee First Name Margie
Last Name Johnson
Address
City
State
Zip Code
Home Phone
Work Phone Field not completed.

Email Address
External Email: Please use caution when clicking links and/or opening attachments.

Employer / Business None
Business Address Field not completed.

City Field not completed.

State Field not completed.

Zip Code Field not completed.

Education Field not completed.
(Section Break)
Qualifications:

Are you a member from a
bona fide local nonpartisan
political organization, with
tax-exempt status under
Section 501(c)(3) of the
Internal Revenue Code,
dedicated to encouraging
informed and active
participation in
government?
No
Are you a member from a
former Civil Grand Jury who
has served in that role
within in the previous five
years?
No
Are you a Modesto
resident?
Yes
If yes, what was the date of
residency?
10/24/1981
Are you a registered voter
in the City of Modesto?
Yes
Are you a registered voter
in Stanislaus County?
Yes
Are you now or have you
ever been employed by the
City of Modesto?
No
Inclusive dates: Field not completed.
#6..
- 32 -
3 Do you have relatives or a
member of your household
who are employed by the
City of Modesto, or who are
currently serving on the City
Council, or who are Board
members or
Commissioners?
No
List relevant employment,
training, and experience,
certificates of training,
licenses, and professional
registration.

Behavioral Health Board, CSOC
How did you learn about
the board for which you are
applying?
Other (Please specify)
If other, please specify: Meetings
Describe your involvement
in community activities and
civic organizations. (Do not
list partisan political
parties.)
Field not completed.

What is it about this
position that interests you?
Being able to help the people of Modesto
What qualities, experience,
and expertise would you
bring to it?
I have had experience with different non profit organizations. (Section Break)
Demographics
City of Modesto invites all applicants to voluntarily self-identify their gender, race/ethnicity, veteran status and disability. Submission of this information is voluntary and refusal to provide will not affect the application process. The information will be kept confidential and will only be used in accordance with the provisions of applicable laws, executive orders and regulations, including those that require the information to be summarized and reported to the federal government for civil rights enforcement.

Gender
Ethnicity
#6..
- 33 -
4 Are you currently, or have
you ever, served in the
Armed Forces?
Do you consider yourself
disabled?
(Section Break)
Email not displaying correctly? View it in your browser. #6..
- 34 -
1 Cynthia Formosa
From: [email protected]
Sent: Wednesday, February 21, 2024 12:06 PM
To: Optimize; Cynthia Formosa; Erica Hunt
Subject: Online Form Submission #45439 for Boards, Commissions & Committees Application External Email: Please use caution when clicking links and/or opening attachments.

Apply To: Citizens Housing & Community Development Committee First Name Gloria Edith
Last Name Verdin
Address
City
State
Zip Code
Home Phone
Work Phone
Email Address
Occupation Associate Regional planner
Employer / Business SAN JOAQUIN COUNCIL OF GOVERNMENT
Business Address 555 East Weber Avenue
City Stockton
State California
#6..
- 35 -
2 Zip Code 95202
Education BA-Sociology
(Section Break)
Qualifications:

Planner for StanCOG, planner for CSG, Planner for SJCOG How did you learn about
the board for which you are
applying?
Other (Please specify)
If other, please specify: webpage
Describe your involvement
in community activities and
civic organizations. (Do not
list partisan political
parties.)
Field not completed.

What is it about this
position that interests you?
I would like to be more involved in my community, and its growth, and provide support/recommendations to help improve the challenges we are facing.

What qualities, experience,
and expertise would you
bring to it?
I have a general understanding of funding distribution, project planning, and delivery and would like to contribute to my community's needs and future growth.
(Section Break)
Demographics
City of Modesto invites all applicants to voluntarily self-identify their gender, race/ethnicity, veteran status and disability. Submission of this information is voluntary and refusal to provide will not affect the application process. The information will be kept confidential and will only be used in accordance with the provisions of applicable laws, executive orders and regulations, including those that require the information to be summarized and reported to the federal government for civil rights enforcement.

Gender
Ethnicity
Are you currently, or have
you ever, served in the
Armed Forces?
Do you consider yourself
disabled?
(Section Break)
#6..
- 37 -
4 Email not displaying correctly? View it in your browser. #6..
- 38 -

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: June 10, 2024
TO: Mayor and City Council
THROUGH: Joseph P. Lopez, City Manager
FROM: Jessica Hill, Director of Community and Economic Development SUBJECT: Appointment to the Landmark Preservation Commission CONTACT: Jessica Hill, Director of Community and Economic Development [email protected] , 209-577-5267
DESCRIPTION:

Consider appointing Joan Clendenin to the City of Modesto Landmark Preservation Commission with term expiring December 31, 2027. (Funding Source: Not Applicable) STRATEGIC PLAN ELEMENT:

This action supports the City’s Strategic Commitment, “Build Community trust in City Government through Responsive, Transparent and Efficient Service Delivery. Goal I.

Promote Trust and Engagement between the Community and the City”.

BACKGROUND:

Section 11021 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions with the recommendation of the City’s Appointments Committee.

DISCUSSION:

Commissioner Babette Wagner was appointed on December 5, 2023, by Resolution 2023-515 and her resignation was effective February 27, 2024, by Resolution 2024-050.

Her resignation leaves a vacancy on the Landmark Preservation Commission and a term to fulfill. This vacancy should be fulfilled by a candidate with one of the following requirements (if possible): an architect or a person in building trades, experience in history, law, architectural history, planning, real estate, landscaping architecture, or has a background in finance, accounting or appraisals, a member of the Modesto Historical 1 https://library.municode.com/ca/modesto/codes/code_of_ordinances?nodeId=CHTR_ARTXIAPBOCO_S1102APTE #7..
- 39 -
City Council Meeting, July 9, 2024
Appointment to the Landmark Preservation Commission

Page 2 of 3 ends

Society and the McHenry Museum or demonstrate an interest in historic properties and preservation. These vacancies are to be filled by the prospective candidates, subject to review by the Appointments Committee, as required by Council policy, and final approval by the City Council.

Outreach for the Landmark Preservation Commission vacancies included posting the vacancy in the Modesto Bee, emails to those who have applied for a Planning Permit, emails to those who have a business license as an Engineer or Architect, and emails to current members of all Planning Committees to send on to their colleagues to apply. In addition, the vacancies were advertised through the City of Modesto’s social media.

The Appointments Committee received ten (10) applications for the Landmark Preservation Commission, two (2) candidates have experience in History, Law and/or Planning, and eight (8) candidates have an interest in historic properties and preservation.

FISCAL IMPACT:

There is no fiscal impact related to this action.

COMMITTEE RECOMMENDATION:

At the June 5, 2024, Appointments Committee meeting, a motion was made recommending the appointment of Joan Clendenin to fill the one (1) vacancy with a term expiring December 31, 2027, for the City of Modesto Landmark Preservation Commission and forwarding to Council for approval.

RECOMMENDED COUNCIL ACTION:

Staff Recommendations:

Resolution appointing Joan Clendenin to the City of Modesto Landmark Preservation Commission with a term expiring December 31, 2027.
#7..
- 40 -
City Council Meeting, July 9, 2024
Appointment to the Landmark Preservation Commission

Page 3 of 3 ends

Approved by:

Jessica Hill, Director of Community & Economic
Development
Joseph P. Lopez, City Manager
Attachments:

1. Resolution

2. Landmark Preservation Bylaws
#7..
- 41 -
07/09/2024/CED/Hill 1 2024-

MODESTO CITY COUNCIL
RESOLUTION NO. 2024-

RESOLUTION APPOINTING JOAN CLENDENIN TO THE CITY OF

MODESTO LANDMARK PRESERVATION COMMISSION WITH A TERM
EXPIRING DECEMBER 31, 2027
WHEREAS, Section 1102 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions; and WHEREAS, Landmark Preservation Commissioner Babette Wagner resignation was effective as of February 27, 2024; and
WHEREAS, the Appointments Committee met on June 5, 2024, and recommended the appointment of Joan Clendenin to the Landmark Preservation Commission.

NOW, THEREFORE, BE IT HEREBY RESOLVED by the Council of the City of Modesto that it herby appoints Joan Clendenin, who has experience in History, Law and/or Planning, to the City of Modesto Landmark Preservation Commission with a term expiring December 31, 2027.

BE IT FURTHER RESOLVED, the City Clerk is hereby directed to transmit a copy of this resolution to the appointed member of the Modesto Landmark Preservation Commission, and the Secretary thereof.
#7..
- 42 -
07/09/2024/CED/Hill 2 2024-
The foregoing resolution was introduced at a regular meeting of the Council of the City of Modesto held on the 9th of July 2024, by Councilmember , who moved its adoption, which motion being duly seconded by Councilmember , was upon roll call carried and the resolution adopted by the following vote:

AYES: Councilmembers:

NOES: Councilmembers:

ABSENT: Councilmembers:

ATTEST: ___________________________
DIANE NAYARES-PEREZ, CMC City Clerk
(SEAL)
APPROVED AS TO FORM:

BY: ____________________________________
JOSE M. SANCHEZ, City Attorney
#7..
- 43 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
1 RULES AND REGULATIONS
Of

LANDMARK PRESERVATION COMMISSION OF CITY OF MODESTO
ARTICLE I.

ORGANIZATION
Section 1.1 Establishment. The Landmark Preservation Commission of the City of Modesto, hereafter called “The Commission”, is established pursuant to the provisions of Chapter 10 of Title IX of the Modesto Municipal Code.

ARTICLE II.

POWERS AND DUTIES
Section 2.1 Enumerated. The Commission shall have the powers and duties as noted in Chapter 10 of Title IX and as contained in its enabling Ordinance No. 2619-CS and all subsequent ordinances amending Chapter 10 of Title IX.

ARTICLE III.

MEETINGS
Section 3.1 Regular Meetings. The regular meetings of the Commission shall be held at 1:00 p.m. on the third Monday of each calendar month. If a regular meeting day falls on a holiday as defined by the Government Code of the State of California, the meeting shall be held on the following Monday. If the following Monday falls on a holiday, the meeting shall be held on the next business day after the following Monday.

If all members are absent from any regular or adjourned meeting, the Secretary may declare the meeting adjourned to a stated time and place. If the Secretary does so, the Secretary shall cause written notice of the adjournment to be given in the same manner provided for special meetings.

Whenever a regular or adjourned regular meeting is adjourned as provided in this section, the resulting adjourned regular meeting is a regular meeting for all purposes. When an order of adjournment of any meeting fails to state the hour at which the adjourned meeting shall be held, it shall be held at the hour specified for the regular meeting which was adjourned.

Section 3.2 Special Meetings. A special meeting may be called at any time by the Chairperson of the Commission whenever, in the Chairperson’s opinion, the public business may require it, or upon the written request of two (2) members of the Commission. Whenever a special meeting shall be called, written notice of such meeting shall be delivered personally or by mail by the office of the Secretary of the Commission to each member of the Commission #7..
- 44 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
2 and to each local newspaper of general circulation, radio or television station requesting notice in writing.

Such notice must be delivered at least twenty-four (24) hours before the time of such meeting as specified in the notice. The notice shall specify the time and place of the special meeting and the business to be transacted. No other business shall be considered at such meetings by the Commission. The written notice may be dispensed with as to any member of the Commission who, at or prior to the time the meeting convenes, files with the Secretary a written notice of waiver. The written notice may also be dispensed with as to any member who is actually present at the meeting at the time it is convened.

Section 3.3 Place of Meetings. All meetings shall be held in the official Council Chamber of the City of Modesto or in such other location of the City as may be designated by the Landmark Preservation Commission.

Section 3.4 Quorum. A majority of the members of the Commission (four members of seven) shall constitute a quorum for the transaction of business, but fewer members than a quorum may adjourn from time to time.

Section 3.5 Meetings to be Public. All meetings of the Commission shall be open to the public.

Section 3.6 Seating and Roll Call Vote. Each quarter, the Chair may establish the order of seating of members. A roll call vote shall be taken upon the passage of all resolutions and be entered upon the journal of the proceedings of the Commission. Upon the request of any member, a roll call vote shall be taken and recorded on any vote. Whenever a roll call vote of the Commission is in order, the names of the members shall be called in the order seated, provided that the name of the presiding officer shall be called last. All members present shall be required to vote, unless a member has a conflict of interest which requires abstention from voting. The affirmative or negative vote of a majority of the entire membership of the Commission shall be necessary for it to take action.

Section 3.7 Attendance. Regular attendance at all meetings of the Commission is required of all members to enable the Commission to discharge the duties imposed upon it by law. If a member is absent from three (3) regular meetings of the Commission consecutively, without securing the permission of the Commission expressed in its official minutes, the member shall be deemed to have resigned from the Commission, and the member’s office shall become vacant.

Section 3.8 Agenda and Reports. In order to facilitate the orderly conduct of the business of the Commission, the Secretary shall arrange an agenda of the matters to be considered by the Commission at its next meeting together with a report outlining all known facts in each case to be considered by the Commission, with such analysis as is necessary, including recommended action when appropriate. The agenda and all reports shall be delivered or mailed to each member of the Commission, the City Manager, and the City Attorney prior to #7..
- 45 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
3 the Commission meeting at which they are to be considered, as far as possible in advance of the meeting as time for preparation will permit.

Matters not included on the agenda will not be acted upon by the Commission unless (a) a majority of the Commission present determine that an emergency situation exists, or (b) the Commission by a two-thirds vote, or if less than two-thirds of the members are present by a unanimous vote, determines that the need to take action arose subsequent to the agenda for the meeting being posted, or (c) the item was on a properly posted agenda for a prior meeting of the Commission occurring not more than five (5) days prior to the meeting at which the action is taken.

Section 3.9 Field Trips. In cases where a view of the premises will assist the Commission in making a decision, a field trip may be arranged prior to the meeting at which time that case shall be heard.

Section 3.10 Reading of the Minutes. Unless the reading of the minutes of a previous Commission meeting is requested by a member of the Commission, such minutes may be approved without reading if the Secretary has previously furnished each member of the Commission with a copy thereof.

ARTICLE IV.

OFFICERS
Section 4.1 Enumerated. The officers of the Commission shall be:

A Chairperson, whose duties shall be to preside at all meetings and call special meetings; and
A Vice-Chairperson, who shall, in the absence of the Chairperson, perform the duties of the Chairperson.

If both are absent, a Chairperson, Pro tempore, shall be elected by the Commissioners present at a given meeting.

Section 4.2 Election of Officers. As soon as practical following the first day of January of each year, the Commission shall elect a Chairperson and Vice-Chairperson.

ARTICLE V.

PROCEDURES, POWERS, DUTIES, AND STAFF
Section 5.1 Designated. The provisions of the Municipal Code of the City of Modesto pertaining to procedures, powers, duties, and staff shall prevail. The City Manager shall designate staff to serve as Secretary to the Commission. The Secretary shall keep a written record of all business transacted by the Commission, notify Commission members of meetings, and keep the official records of the Commission. Upon the direction of the Commission, the Secretary shall perform such other secretarial duties as the Commission may require. #7..
- 46 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
4 ARTICLE VI.

PARLIAMENTARY PROCEDURE
Section 6.1 Rules of Order. Except as otherwise provided in these rules and regulations, all meetings of the Commission shall be conducted in accordance with the City’s Rules of Order as contained in Section 2-1.10 of the Modesto Municipal Code.

ARTICLE VII.

COMMITTEES
Section 7.1 Special Committees. There shall be such special committees as the Commission may establish from time to time.

ARTICLE VIII.

PUBLIC HEARINGS
Section 8.1 Public Hearing Procedures. The following rules shall govern the conduct of public hearings.
(a) All hearings will be recorded by mechanical means. If a court reporter is desired for a verbatim transcript, the fee or fees of such court reporter shall be paid by the party requesting the services.
(b) The real parties in interest, including the applicant or any party having a substantial interest in the hearing, may be represented by counsel or a spokesperson. (c) At the opening of the hearing, a report prepared in advance of the hearing by the staff will be presented by a member of the staff. As a part of this presentation, suitable large-scale plot plans, photos and other graphics of the project may be identified and placed in view of the Commission and all persons attending the hearing. (d) At the conclusion of the presentation by the staff, the applicant and then the proponents may make a presentation, including calling witnesses and presenting any material exhibits, documents or other physical evidence. Reading at length from books and other written material will not be permitted.
(e) At the conclusion of the presentation by the applicant and proponents, any persons who oppose the application may make a presentation, including calling witnesses and presenting any material exhibits, documents or other physical evidence. Reading at length from books and other written material will not be permitted. #7..
- 47 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
5 (f) All exhibits, documents or other physical evidence used by applicant or other interested parties during the hearings, will become part of the record and retained by the Secretary until the decision becomes final.
(g) Witnesses shall not be required to be sworn. Each witness will be required to approach the microphone and give their full name for the record before making a presentation.
(h) The right to question the witnesses shall be afforded, if requested.

However, the Chairperson may require that such questions be addressed through the Chairperson for resubmission to the witness.
(i) The reading of details of letters and petitions by the persons submitting them will not be permitted. Such documents may be filed with the Secretary and the Secretary shall mark them as having been received for the limited purpose of showing the names of the persons protesting or supporting the application.
(j) While it is desirable in a democratic process to permit every person an unlimited right to speak, such a right may unduly prolong a public hearing and cloud the basic issue if the comments presented are merely cumulative and repetitious. Therefore, whenever necessary, the Chairperson will state that cumulative and repetitious comments are to be avoided and may limit the time allocated for persons who wish to speak. Similarly, testimony and comments which are incompetent, irrelevant or immaterial shall be foreclosed by the Chairperson. If, because of the informality of the hearing, such improper comments are received, it shall not be considered by the Commission in reaching its decision. (k) The Commission may establish special rules for individual meetings, establishing time limits for presentations and requiring presentations to be made through spokespersons, if possible.
(l) After those in favor and opposed to an application have been heard, the Chairperson will ask for the recommendation of the staff and the reasons for such recommendation. After such recommendation, one spokesperson for the applicant and one spokesperson for the opponents shall be given a limited amount of time to summarize their position or respond to the recommendation, after which the Chairperson shall close the public portion of the hearing.
(m) The Commission should discuss the issues involved and make its decision only after hearing the evidence presented at the public hearing. Discussion of the matter by Commission members should be delayed until after the public hearing is closed and the matter is presented to the Commission for discussion and decision. (n) The Commission may take a field trip to view the property involved in the public hearing. All field trips shall be taken as part of a regular, adjourned regular, or special meeting of the Commission and all interested persons will be afforded the opportunity to #7..
- 48 -
Rules and Regulations of
Landmark Preservation Commission
City of Modesto
February 27, 2017
6 be present to hear any reports or comments. A complete record of such field trip will be entered into the minutes so the record will indicate that the field trip was taken into consideration as evidence. If a Commissioner has personal knowledge of the property or area, the Commissioner should make a statement to that effect at the time of the hearing so the record will reflect everything being taken into consideration in making the final decision. (o) Commissioners are responsible for ensuring that the public hearing is conducted in a fair and impartial manner. If a Commissioner receives a significant personal contact or telephone call outside of the public hearing which concerns a matter pending before or of interest to the Landmark Preservation Commission, he or she shall disclose the substance and nature of the contact or call at the public hearing. If written materials are presented to the Commission by an applicant or member of the public, a copy should be made available for public review by filing the materials with the Secretary at least three (3) days in advance of the meeting at which the item or matter is scheduled to be considered or at the time the materials are provided to any Commissioner, whichever is earliest. (p) Summary of Procedure for Conduct of Public Hearings by the Modesto Landmark Preservation Commission:

1. Opening of public hearing

2. Staff report

3. Applicant’s presentation

4. Presentation by those in favor

5. Presentation by those opposed

6. Staff recommendation

7. Summation by one spokesperson for the applicant and one spokesperson for the opposition

8. Close of public portion of hearing

9. Discussion and decision by the Commission
#7..
- 49 -

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: June 12, 2024
TO: Mayor and City Council
THROUGH: Joseph P. Lopez, City Manager
FROM: Jeremy Rogers, Director of Parks, Recreation and Neighborhoods SUBJECT: Appointments to the Golf Courses Advisory Committee CONTACT: Jessica Franco, Administrative Analyst II, [email protected], 209-577-5278
DESCRIPTION:

Consider approving the appointments of Evan Yoshino as a Member-At-Large for a four-year term from January 1, 2024, to December 31, 2027 and Martin Montez as a Youth Member-AtLarge for a one-year term from July 1, 2024 to June 30, 2025, on the City of Modesto Golf Courses Advisory Committee. (Funding Source: Not Applicable) STRATEGIC PLAN ELEMENT:

BACKGROUND:

The Golf Courses Advisory Committee (GCAC) serves as an advisory board for and among organized golf clubs and the City of Modesto. It is comprised of six (6) Member-at-Large representatives (including one (1) – Youth Member-at-large) and one (1) representative each from the SIRS Golf Club, Dryden Park Women’s Club, Creekside Golf Club, Muni-Niners Club, and Modesto Golf Club.

Ten (10) members are appointed by the City Council for a four (4)-year term starting January 1st and ending December 31st and one (1) Youth member is appointed for a one-year term.

Section 11021 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions with the recommendation of the City’s Appointments Committee.
1 https://library.municode.com/ca/modesto/codes/code_of_ordinances?nodeId=CHTR_ARTXIAPBOCO_S1102APTE #8..
- 50 -
City Council, July 9, 2024
Appointments to the Golf Courses Advisory Committee

Page 2 of 3 ends

DISCUSSION:

Currently, there are a total of two vacancies on the Committee:

Organization Status
Member-At-Large VACANT
Member-At-Large (Youth) VACANT
These vacancies are to be filled by prospective candidates, subject to review by the Appointments Committee, as required by Council policy, and final approval by the City Council.

Advertising for the Golf Courses Advisory Committee vacancies included posting the vacancies in the Modesto Bee, posts on Social Media channels, and outreach by current committee members.

Two (2) new applicants were received for consideration:

Evan Yoshino is a current member on the Board of Building Appeals and is an avid golfer who plays several times a month. He has experience playing on the City’s Golf Courses and is familiar with the local golf community.

Martin Montez is a student at Gregori High School and is a member of the City’s Youth Commission. He has played golf growing up and is interested in bringing ideas to engage youth to play golf.

These applicants meet the minimum requirements of the Committee, which include being a resident of Modesto, to not hold any paid office or employment, nor is a contractor with the City of Modesto.

FISCAL IMPACT:

There is no fiscal impact related to this action.

COMMITTEE RECOMMENDATION:

Appointments were considered by the Appointments Committee on June 5, 2024 and recommended to forward to Council for approval.

RECOMMENDED COUNCIL ACTION:

Staff Recommendations:

Resolution approving the appointments of Evan Yoshino as a Member-At-Large for a fouryear term from January 1, 2024, to December 31, 2027 and Martin Montez as a Youth Member-At-Large for a one-year term from July 1, 2024 to June 30, 2025, on the City of Modesto Golf Courses Advisory Committee.

Approved by:

Jeremy Rogers, Director of Parks, Recreation and
Neighborhoods
Joseph P. Lopez, City Manager
#8..
- 51 -
City Council, July 9, 2024
Appointments to the Golf Courses Advisory Committee

Page 3 of 3 ends

Attachments:

1. Resolution

2. Golf Courses Advisory Committee Bylaws

3. Applications
#8..
- 52 -
07/09/2024/PRN/JFranco/Item ? 1 2024-?

MODESTO CITY COUNCIL
RESOLUTION NO. 2024-

RESOLUTION APPROVING THE APPOINTMENTS OF EVAN YOSHINO AS A MEMBER-AT-LARGE FOR A FOUR-YEAR TERM FROM JANUARY 1, 2024, TO DECEMBER 31, 2027 AND MARTIN MONTEZ AS A YOUTH MEMBERAT-LARGE FOR A ONE-YEAR TERM FROM JULY 1, 2024 TO JUNE 30, 2025,

ON THE CITY OF MODESTO GOLF COURSES ADVISORY COMMITTEE
WHEREAS, Section 1102 of the Charter of the City of Modesto authorizes the City Council to appoint members to various Boards and Commissions, and WHEREAS, the Golf Courses Advisory Committee is comprised of five members representing local golf organizations: SIRS Golf Club, Muni-Niners Golf Club, Modesto Golf Club, Creekside Golf Club, and Dryden Women’s Golf Club, and six Members-AtLarge, including one Youth Member-At-Large, and WHEREAS, there currently exists two vacancies on the Committee- one Member-At-Large, and one Youth Member-At-Large, and
WHEREAS, the Committee, after performing outreach to advertise the vacancies, received two applications; and
WHEREAS, Evan Yoshino is qualified to serve as a Member-At-Large for a fouryear term from January 1, 2024 through December 31, 2027, and WHEREAS, Martin Montez is qualified to serve as a Youth Member-At-Large for a one-year term from July 1, 2024 through June 30, 2025, and WHEREAS, on June 5, 2024, the Appointments Committee recommended the appointment of Evan Yoshino as a Member-At-Large, and the appointment of Martin Montez as a Youth Member-At-Large.

NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Modesto that it hereby approves the appointments of Evan Yoshino as a Member-At-Large for a #8..
- 53 -
07/09/2024/PRN/JFranco/Item ? 2 2024-?
four-year term from January 1, 2024, to December 31, 2027 and Martin Montez as a Youth Member-At-Large for a one-year term from July 1, 2024 to June 30, 2025, on the City of Modesto Golf Courses Advisory Committee.

BE IT FURTHER RESOLVED that the City Clerk is hereby directed to transmit a copy of this resolution to the appointed members of the Golf Courses Advisory Committee, and the Secretary, thereof.
#8..
- 54 -
07/09/2024/PRN/JFranco/Item ? 3 2024-?
The foregoing resolution was introduced at a regular meeting of the Council of the City of Modesto held on the 9th day of July 2024, by Councilmember ?, who moved its adoption, which motion being duly seconded by Councilmember ?, was upon roll call carried and the resolution adopted by the following vote:

AYES: Councilmembers:

NOES: Councilmembers:

ABSENT: Councilmembers:

ATTEST:

DIANE NAYARES-PEREZ, CMC,
City Clerk
(SEAL)
APPROVED AS TO FORM:

BY: _______________________________
JOSE M. SANCHEZ, City Attorney
#8..
- 55 -

Page 1 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

CITY OF MODESTO GOLF COURSES COMMITTEE

CONSTITUTION AND BYLAWS
#8..
- 56 -

Page 2 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE I

DEFINITIONS
Section 1 There is created a Committee to be known and designated as the City of Modesto Golf Courses Committee.

Section 2 As used in these Bylaws, unless a different meaning clearly appears from the context:

A. "Member" shall mean a member of the Modesto Golf Courses Committee.

B. "Modesto Golf Courses Committee" and "Committee" shall mean the City of Modesto Golf Courses Committee.

C. "Modesto golf courses" shall mean Dryden Park Golf Course and Creekside Golf Course.

D. "Regular meeting" shall mean the bi-monthly Committee meetings.

Section 3 The fiscal year shall coincide with the City's fiscal year, July 1 to June 30. #8..
- 57 -

Page 3 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE II

OBJECTIVES
Section 1 The Committee shall be responsible for promotion of the game of golf in the Modesto area.

Section 2 The Committee shall operate as an advisory body for and among organized golf clubs and the general golfing public of the City of Modesto golf courses.

Section 3 The Committee shall act as liaison between the general golfing public, golf clubs, and the City of Modesto Parks, Recreation and Neighborhoods Department, and A. Shall receive and consider all proposals for innovations or material changes in established procedures or the modification of the golf courses.

B. Endorse participation in golf through the Player Development Programs and Tournament activities with a special emphasis on Junior, Senior and Disabled golf.

Section 4 The Committee shall encourage, promote and maintain a high standard of sportsmanship among golfers.

Section 5 The Committee shall consider the annual budget for the Golf Enterprise Fund during the process of its preparation and make recommendations to the Director of Parks, Recreation and Neighborhoods concerning the annual budget of the Golf Enterprise Fund, including the fees and rates to be charged for the use of golf course facilities.

Section 6 The Committee shall perform such other duties relating to the Modesto Golf Courses as may be assigned by the Director of Parks, Recreation and Neighborhoods.

Section 7 Nothing in this article shall be deemed to invest the Committee with any supervisory powers over the actions and duties of City employees, or of any Lessee of the City, engaged in work relating to the construction, improvement, repair, maintenance or operations of the Modesto golf courses.
#8..
- 58 -

Page 4 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE III

MEMBERSHIP
Section 1 The City of Modesto Golf Courses Committee shall consist of eleven (11) Members.

Section 2 The Members of the Committee shall reside within the city limits of the City of Modesto at the time of appointment and must maintain residence within the City at all times during their service on the Committee.

Section 3 None of the members shall hold any paid office or employment or shall be currently a contractor with the City of Modesto.

Section 4 Five (5) members of the Committee shall represent organized golf clubs at the municipal golf courses, one from each of the following clubs: Muni Niners; SIRS; Modesto Golf Club; Dryden Park Women's Club; and Creekside Golf Club. Five(5) members shall be appointed at large One (1) youth member, between 16 and 25 years of age, shall be appointed at large.

Section 5 The membership of each organized golf club shall recommend one member to represent their respective clubs, with the remaining six (6) at-large members to be approved by a majority vote of the City Council.

Section 6 The Director of Parks, Recreation and Neighborhoods, or his/her designee, will serve as staff to the Committee and represent the City of Modesto, within the limits dictated by fiscal constraints.
#8..
- 59 -

Page 5 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE IV

TERMS OF OFFICE
Section 1 The term of office shall be effective as of the first of January.

Section 2 The terms of office shall be as follows:

A. Four (4) years for each Member of the Committee. Members may be re-appointed after their initial term, but in no event shall any person who has served two (2) consecutive terms on the Committee be eligible for re-appointment to the Committee.

Committee members are eligible for reappointment to the Committee after a two- (2) year absence from the Committee has transpired.

B. One (1) year for each youth member appointed at large. Youth members may be reappointed after their initial term, but in no event shall any youth member who has served two (2) consecutive terms on the Committee be eligible for reappointment to the Committee.

Section 3 Serving any portion of an unexpired term shall not be counted as service of one term.

Members not eligible for reappointment may continue to serve until their successors are appointed and meet all of the qualifications outlined in Article III Membership of these bylaws. No member shall serve more than a maximum of eight (8) consecutive years.

Section 4 The terms of office for the inaugural Committee will be two (2) years for five (5) members of the Committee, and four (4) years for the remaining six (6) members. Each member's term of office shall terminate on December 31 of their respective year.

Section 5 The Members of the Committee shall receive no compensation for the performance of their official duties.

Section 6 Appointments to fill vacancies on the Committee shall be handled in the same manner as original appointments. When a vacancy occurs during a term, the appointment to fill such vacancy shall be for the unexpired portion of the term.

Section 7 Members of the Committee may be removed by a majority vote of the City Council after a recommendation by the Director of Parks, Recreation and Neighborhoods and a majority vote of the Committee. Examples of reasons for removal of a Committee Member from the Committee are:

A. Incompetence, malfeasance, misfeasance, neglect of duty, or conviction of a crime involving moral turpitude.

B. Refusal to resign from the Committee when no longer a resident of the City of Modesto.

C. Automatic removal from the Committee will be required when a member is absent from three (3) meetings within a twelve- (12) month period without official permission expressed in the official minutes.
#8..
- 60 -

Page 6 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE V

ATTENDANCE AT MEETINGS
Section 1 It shall be the responsibility of each Member to know the dates and times of all regular meetings of the Committee. If a Member knows he or she will not be able to attend a regularly scheduled meeting, it shall be his or her responsibility to notify the Committee Chair or Staff Liaison at least forty-eight hours (48 hours) before the meeting, in order for the absence to be recorded as an excused absence.

Section 2 The Recording Secretary will document when any Committee Member is late arriving for a meeting or when a Committee Member leaves a meeting before adjournment. The minutes of each meeting will list those Members in attendance, those who are excused and those who are unexcused.
#8..
- 61 -

Page 7 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE VI

OFFICERS AND THEIR DUTIES
Section 1 Officers shall consist of Chair and Vice-chair, elected by a majority vote of the Members of the Committee. Officers shall serve a one- (1) year term commencing on January 1. The election shall be held at the January meeting, or the first meeting of the year.

Section 2 All officers shall exercise all privileges of membership, including the making of motions, seconding and debate.

Section 3 The Chair may serve consecutive terms. The Vice-Chair may serve consecutive terms.

Section 4 The Chair shall preside at all meetings and appoint all sub-committees of the Committee and shall ensure that the bylaws, rules and regulations as adopted by the Committee are properly enforced. The Chair shall be an ex-officio member of all sub-committees.

Section 5 The Vice-Chair shall assist the Chair in his/her duties and in the absence of the Chair shall perform all duties usually performed by the Chair.

Section 6 The Parks, Recreation and Neighborhoods Department shall provide a staff member to serve as Recroding Secretary. He/she shall keep a record of the minutes of all meetings, reports of sub-committees and such other duties as are usually performed by a secretary.

He/she shall supply the Members of the Committee and any sub-committees and the Director of Parks, Recreation and Neighborhoods and his/her designee(s) with copies of all records taken within three (3) weeks after a meeting takes place. He/she shall also assist in publicity releases concerning Committee activities.
#8..
- 62 -

Page 8 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE VII

MEETINGS
Section 1 Regular meetings of the Committee shall be held at such times and places as from time to time may be designated by a majority vote of the Committee.

Section 2 In the event that a regular meeting falls on a holiday, the meeting shall be scheduled by a vote of the Committee. Special meetings shall be called by the Chair as necessary.

Section 3 Notices of all meetings, including an agenda, shall be given to all members of the Committee, to the City Clerk, to the City Manager, to the Director of Parks, Recreation and Neighborhoods and to all others as provided by law. All such notices shall be furnished to the Committee in writing at least seventy-two hours (72 hours) prior to the time of such meeting.

Section 4 All meeting agendas will be posted at Tenth Street Place and will be available at the following public facilities: Tenth Street Place, the Main Branch of the Stanislaus County Free Library and at City of Modesto golf courses.

Section 5 All meetings shall comply with the requirements of the Ralph M. Brown Act.

Section 6 A quorum is necessary for the Committee to transact any business. A quorum shall be defined as a simple majority of active Committee members.

Section 7 All meetings of the Committee, or its standing or special sub-committees, shall be open to the public and shall be held at a public facility which is accessible in accordance with the regulations of the Americans with Disabilities Act.
#8..
- 63 -

Page 9 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE VIII

ORDER OF PROCEEDINGS
Section 1 Sturgis' Standard Code of Parliamentary Procedure shall be the guide for parliamentary procedures in the conduct of Committee meetings.

Section 2 The order of proceedings of all meetings shall be as follows, subject to majority vote of the Members present:

A. Call to Order
B. Approval of Minutes
C. Written Communications
D. Old Business
E. New Business
F. Oral Communications
G. Matters Too Late for the Agenda
H. Adjournment
Section 3 Members of the public shall not speak unless recognized by the Chair and shall state their names and addresses before making any statement, which shall become a part of the public record. The Chair may remove any person who refuses to follow these rules or the decision of the Chair.
#8..
- 64 -

Page 10 ends

Amended by City Council Resolution No. 2022-023
January 11, 2022

ARTICLE IX

AMENDMENTS
Section 1 The Constitution and Bylaws may be recommended for amendment at a regularly scheduled meeting of the Committee. A written notice containing the proposed changes shall be provided to each member at least sixty (60) days prior to the meeting. When all other conditions are met, an amendment requires a simple majority vote of the active members of the Committee.

Section 2 The Constitution and Bylaws and any future amendments shall be subject to the final approval of the City Council and shall not and are not intended to go beyond any of the powers and duties given to the Committee by the City Council. #8..
- 65 -
1 Jessica Franco
From: Diane Sheatsley
Sent: Tuesday, April 30, 2024 11:42 AM
To: Jessica Franco
Subject: FW: Online Form Submission #46316 for Boards, Commissions & Committees Application
Categories: Golf Category
From: [email protected] <[email protected]>
Sent: Tuesday, April 30, 2024 10:51 AM
To: Optimize <[email protected]>; Diane Sheatsley <[email protected]>; Breanne Villarreal (DiCiano) <[email protected]>
Subject: Online Form Submission #46316 for Boards, Commissions & Committees Application External Email: Please use caution when clicking links and/or opening attachments.

Apply To: Golf Courses Advisory Committee
First Name Evan
Last Name Yoshino
Address
City Modesto
State CA
Zip Code 95354-0523
Home Phone
Work Phone Field not completed.
#8..
- 66 -
2 Email Address
Occupation General Contractor
Employer / Business Field not completed.

Business Address Field not completed.

City Field not completed.

State Field not completed.

Zip Code Field not completed.

Education Field not completed.
(Section Break)
Qualifications:

I've been an avid golfer for 25 years and play primarily in Modesto.

How did you learn about
the board for which you
are applying?
Other (Please specify)
If other, please specify: City Website
Describe your
involvement in
community activities
and civic organizations.
(Do not list partisan
political parties.)
I'm on the Board of Building Appeals at the City
What is it about this
position that interests
you?
I am applying for the Golf Courses Advisory Committee
because I am passionate about golf and I want to contribute to the growth of the game in our community. My love of the game, my experience as a golfer, and my knowledge of the game's history and traditions would be a valuable asset to the committee. I play golf several times a month. I am aware of the challenges facing golf courses today and I believe that I can #8..
- 68 -
4 contribute to the committee's efforts to address those challenges. I am excited about the opportunity to serve on the Golf Courses Advisory Committee and I look forward to
contributing to the success of the committee and the golf courses in our community.

What qualities,
experience, and
expertise would you
bring to it?
My experience as a local golfer, as well as my familiarity with the local golf community, would make me a valuable member of the Golf Courses Advisory Committee. I have played golf in the Modesto area for over 20 years and have a deep
understanding of the local golf courses. My children also play golf in the Modesto area, and I have a good understanding of the challenges they face as young golfers. I am passionate about golf and believe that I can make a significant contribution to the Golf Courses Advisory Committee.
(Section Break)
Demographics
City of Modesto invites all applicants to voluntarily self-identify their gender, race/ethnicity, veteran status and disability. Submission of this information is voluntary and refusal to provide will not affect the application process. The information will be kept confidential and will only be used in accordance with the provisions of applicable laws, executive orders and regulations, including those that require the information to be summarized and reported to the federal government for civil rights enforcement.

Gender
Ethnicity
Are you currently, or
have you ever, served in
the Armed Forces?
Do you consider
yourself disabled?
(Section Break)
Email not displaying correctly? View it in your browser. #8..
- 69 -
1 Jessica Franco
From: Diane Sheatsley
Sent: Tuesday, April 30, 2024 4:12 PM
To: Jessica Franco
Subject: FW: Online Form Submission #46324 for Boards, Commissions & Committees Application
Follow Up Flag: Follow up
Flag Status: Flagged
Categories: Golf Category

From: [email protected] <[email protected]>
Sent: Tuesday, April 30, 2024 4:02 PM
To: Optimize <[email protected]>; Diane Sheatsley <[email protected]>; Breanne Villarreal (DiCiano) <[email protected]>
Subject: Online Form Submission #46324 for Boards, Commissions & Committees Application External Email: Please use caution when clicking links and/or opening attachments.

Apply To: Golf Courses Advisory Committee
First Name martin
Last Name montez
Address
City Modesto
State California
Zip Code 95355
#8..
- 70 -
2 Home Phone
Work Phone
Email Address
Occupation student
Employer / Business
Business Address
City Modesto
State California
Zip Code 95356
Education I am current a sophomore going into junior year in the fall. (Section Break)
Qualifications:

Are you a member from
a bona fide local
nonpartisan political
organization, with taxexempt status under
Section 501(c)(3) of the
Internal Revenue Code,
dedicated to
encouraging informed
and active participation
in government?
No
Are you a member from
a former Civil Grand Jury
who has served in that
role within in the
previous five years?
No
Are you a Modesto
resident?
Yes
If yes, what was the date
of residency?
12/6/2007
#8..
- 71 -
3 Are you a registered
voter in the City of
Modesto?
No
Are you a registered
voter in Stanislaus
County?
No
Are you now or have you
ever been employed by
the City of Modesto?
Yes
If yes, in what capacity? Member of Youth Commission
Inclusive dates: 11/8/2023 - 6/12/2024
Do you have relatives or
a member of your
household who are
employed by the City of
Modesto, or who are
currently serving on the
City Council, or who are
Board members or
Commissioners?
No
List relevant
employment, training,
and experience,
certificates of training,
licenses, and
professional
registration.

I have been in Youth Commission as well as Park Youth
Committee, a youth group held by Tuolomne River Trust for achieving park equity. I also have done golf for over ten years.

How did you learn about
the board for which you
are applying?
Place of Employment
Describe your
involvement in
community activities
and civic organizations.
(Do not list partisan
political parties.)
I love to volunteer wherever I can, which is usually at schools, churches, and local events such as the Cinco De Mayo event and Love Modesto.

What is it about this
position that interests
you?
I have always loved golf, and I feel as though growing up with it know how to appeal to the youth getting into golf.
#8..
- 72 -
4 What qualities,
experience, and
expertise would you
bring to it?
I would bring ideas of how to get the youth more engaged by providing a personal experience of how it worked for me, as well as using my time with golf to further connect with neighboring golf areas.
(Section Break)
Demographics
City of Modesto invites all applicants to voluntarily self-identify their gender, race/ethnicity, veteran status and disability. Submission of this information is voluntary and refusal to provide will not affect the application process. The information will be kept confidential and will only be used in accordance with the provisions of applicable laws, executive orders and regulations, including those that require the information to be summarized and reported to the federal government for civil rights enforcement.

Gender
Ethnicity
Are you currently, or
have you ever, served in
the Armed Forces?
Do you consider
yourself disabled?
(Section Break)
Email not displaying correctly? View it in your browser. #8..
- 73 -
- 1 -
6/11/2024 5:30:00 PM
*Via Teleconference
Councilmember Escutia-Braaton
Atlanta Marriott Marquis Hotel
265 Peachtree Center Avenue, NE
Atlanta, GA. 30303

MODESTO CITY COUNCIL
www.modestogov.com

MINUTES
City of Modesto

CITY COUNCIL MEETING
Chambers, Basement Level
Tenth Street Place, 1010 10th Street
Modesto, California
Tuesday, June 25, 2024 at 5:30 PM
Roll Call – Present: Councilmembers Alvarez, Bavaro, *Escutia-Braaton, Ricci, Williams, Wright, Mayor Zwahlen
Pledge of Allegiance to the Flag
Invocation: Carlos Gonzalez, City Ministry Network
City Clerk’s Announcements
Declaration of Conflicts of Interest: Item 21 - Councilmember Bavaro recused himself due to a conflict.

Reports from Closed Session: No reportable action.

ACKNOWLEDGEMENTS AND PRESENTATIONS

1. Poem by outgoing Poet Laureate Sal Salerno. (Funding Source: Not Applicable) PRN; Diane Sheatsley, 209-577-5418, [email protected] ACTION: Poet Laureate Sal Salerno presented his outgoing poem.

2. Youth Commission Presentation (Funding Source: Not Applicable) PRN; Valerie Garcia, 209-571-5576, [email protected] ACTION: Youth Commission gave a presentation of their activities. #9..
- 74 -
- 2 -
6/11/2024 5:30:00 PM

MISCELLANEOUS

3. Consider approving the appointments for David Harter, Huelon “Herk” Usrey, and Jesse Wiggins to the Board of Building Appeals for a four-year term with a term expiration of January 01, 2027. (Funding Source: Not Applicable) Staff Recommendation:
 Resolution approving the appointments of David Harter, Huelon “Herk” Usrey, and Jesse Wiggins to the City of Modesto Board of Building Appeals to a fouryear term, with a term expiration of January 01, 2027.

CED; Oscar Diaz, 209-577-5232, [email protected]
ACTION: (Wright/Alvarez; 7/0) Resolution 2024-226 approving the appointments of David Harter, Huelon “Herk” Usrey, and Jesse Wiggins to the City of Modesto Board of Building Appeals to a four-year term, with a term expiration of January 01, 2027.

4. Consider approving the appointments of Craig Lewis and Tim Ragsdale to the Citizen’s Transportation Sales Tax Commission for a four-year term with a term from July 1, 2024 to June 30, 2028. (Funding Source: Not Applicable) Staff Recommendation:
 Resolution approving the appointments of Craig Lewis and Tim Ragsdale to the Citizen’s Transportation Sales Tax Commission for a four-year term with a term from July 1, 2024 to June 30, 2028.

ENGINEERING SERVICES; Toby Wells, 209-571-5542, [email protected] ACTION: (Ricci/Wright; 7/0) Resolution 2024-227 approving the appointments of Craig Lewis and Tim Ragsdale to the Citizen’s Transportation Sales Tax Commission for a four-year term with a term from July 1, 2024 to June 30, 2028.

PUBLIC COMMENT IN PERSON
 Deanna Washington voiced concerns about a dispensary that was in their neighborhood, urging businesses like dispensaries to locate away from homes and schools to protect children and improve the neighborhood's image.
 Diane Kroeze expressed concern for homeless individuals not receiving adequate support and invited others to join in advocating for better solutions.  Kevin McClarty voiced concerns about the ACE Train Project delay due to gas line issues, and asked about accountability, feasibility study oversight, relocation timeline and costs, and funding for a temporary station. He urged the Council to commit to ensuring Modesto residents do not have to travel elsewhere for train access.  Sebastian Jones spoke about discrimination at the King Kennedy Center, urging an investigation into the center's reservations. He highlighted efforts to rename the center #9..
- 75 -
- 3 -
6/11/2024 5:30:00 PM
solely after Dr. King, proposed renaming a different park for Kennedy, and stressed the importance of honoring Dr. King's legacy properly.
 Sarah Bland Johnson congratulated the youth and suggested reinstating the Upper Bound program in schools. She spoke of the lack of access to the King Kennedy Memorial Center during a hot event at Martin Luther King Park, highlighting the need for better facilities and accommodations for people with disabilities.  Zeff criticizes the Council for failing to address homelessness and for not using $3 million set aside for bridge housing. He notes that advocates have given up on the Council and highlights an increase in homelessness, urging the Council to consider their legacy and missed opportunities.
 Doctor Karen Clark criticized the King Kennedy Center for abruptly denying their event space three days before their anti-stigma event in Stanislaus County. She urged the Mayor to investigate, highlighting their aim to address racism, mental health, and homelessness through community resources. Clark emphasized the need for inclusivity and equitable access for all residents, regardless of background.  Kirk Usher urged the Council to stop approving what they call "dope dens" in Modesto, referring to recent $16 million allocations for homeless facilities. Usher criticized the effectiveness of current aid programs for homeless adults and expressed concern over increased crime affecting local businesses. The speaker called on Councilmembers to visit locations like the Kansas house, review police reports, and prioritize community safety before funding similar projects.

CONSENT ITEMS – ROLL CALL VOTE REQUIRED
ACTION CONSENT ITEMS: 5-20, 22 (Wright/Williams; 7/0)

CONSENT
Consent

5. Consider approving the minutes for the June 11, 2024 Council Meeting. (Funding Source: Not Applicable)
 Motion approving the minutes for the June 11, 2024 Council Meeting.

CITY CLERK; Diane Nayares-Perez, 209-577-5396, [email protected] ACTION: (Wright/Williams; 7/0) Motion approving the minutes for the June 11, 2024 Council Meeting.

Consent

6. Consider approving the State of California Homekey Resolution authorizing a joint application to and participation in the Homekey program for the development at 710 N. 9th Street. (Funding Source: Homekey 3 Funds)
#9..
- 76 -
- 4 -
6/11/2024 5:30:00 PM
 Resolution of the Governing Body of the City of Modesto authorizing joint application to and participation in the Homekey Program for the development at 710 N. 9th Street.

CED; Edgar Garcia, 209-577-5211, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-228 of the Governing Body of the City of Modesto authorizing joint application to and participation in the Homekey Program for the development at 710 N. 9th Street.

Consent

7. Consider approving the Second Amendment increasing the Agreement amount with 4- LEAF, Inc. for Professional Services for Plan Review and Inspection Services for a total amount not to exceed $642,000 over five years for the Rental Housing Safety Program. (Funding Source: Measure H)
 Resolution approving the Second Amendment to the Professional Services Agreement with 4-LEAF, Inc. for Inspection Services by $30,000 from $53,000 to $83,000 for the fifth year with a revised total amount not to exceed $642,000 from $612,000 over five years and authorizing the City Manager, or his designee, to execute the Amendment.

CED; Oscar Diaz, 209-571-5885, [email protected]
ACTION: (Wright/Williams; 7/0) Resolution 2024-229 approving the Second Amendment to the Professional Services Agreement with 4-LEAF, Inc. for Inspection Services by $30,000 from $53,000 to $83,000 for the fifth year with a revised total amount not to exceed $642,000 from $612,000 over five years and authorizing the City Manager, or his designee, to execute the Amendment.

Consent

8. Consider approving a Modesto Forward Grant Agreement with Stanislaus Community Foundation, to support in-home childcare entrepreneurship, for a total amount not to exceed $156,758. (Funding Source: American Rescue Plan Act Funds)  Resolution approving a Modesto Forward Grant Agreement with Stanislaus Community Foundation to support in home childcare entrepreneurship for a total amount not to exceed $156,758; and authorizing the City Manager, or his designee, to execute the Agreement.

CED; Trevin Barber, 209-571-5566, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-230 approving a Modesto Forward Grant Agreement with Stanislaus Community Foundation to support in home childcare entrepreneurship for a total amount not to exceed $156,758; and authorizing the City Manager, or his designee, to execute the Agreement.

Consent

9. Consider approving a Modesto Forward Grant Agreement with United Way of San Joaquin County for the implementation a Workforce Development Program by HealthForce Partners Northern San Joaquin Valley, for a total amount not to exceed #9..
- 77 -
- 5 -
6/11/2024 5:30:00 PM
$500,000 over two and a half years. (Funding Source: American Rescue Plan Act Funds)
 Resolution approving a Modesto Forward Grant Agreement with United Way of San Joaquin County for the implementation of a Workforce Development Program by HealthForce Partners Northern San Joaquin Valley, for a total amount not to exceed $500,000 over two and a half years, and authorizing the City Manager, or his designee to execute the Agreement.

CED; Trevin Barber, 209-571-5566, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-231 approving a Modesto Forward Grant Agreement with United Way of San Joaquin County for the implementation of a Workforce Development Program by HealthForce Partners Northern San Joaquin Valley, for a total amount not to exceed $500,000 over two and a half years, and authorizing the City Manager, or his designee to execute the Agreement.

Consent

10. Consider approving the summary vacation of an existing 60 feet wide by approximately 192 feet long (11,505.95 square feet) road right-of-way located at APN 033-089-037. (Funding Source: Not Applicable)
 Resolution approving the summary vacation of an existing 60 feet wide by approximately 192 feet long (11,505.95 square feet) road right-of-way located at APN 033-089-037.

ENGINEERING SERVICES; Jaspreet Mangat, 209-577-5253,
[email protected]
ACTION: (Wright/Williams; 7/0) Resolution 20024-232 approving the summary vacation of an existing 60 feet wide by approximately 192 feet long (11,505.95 square feet) road right-of-way located at APN 033-089-037.

Consent

11. Consider accepting the Jennings Command Center and Hahn Lift Station Restroom Project as complete, releasing securities, releasing payments totaling $568,374 to Harris Builders, Inc., of Hilmar, CA, and authorizing the City Clerk to file a Notice of Completion (Funding Source: Wastewater Fund)
 Resolution accepting the Jennings Command Center and Hahn Lift Station Restroom Project as complete, releasing securities, releasing payments totaling $568,374 to Harris Builders, Inc., of Hilmar, CA., and authorizing the City Clerk to file a Notice of Completion.

ENGINEERING SERVICES; Peter Kambel, 209-577-5444, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-233 accepting the Jennings Command Center and Hahn Lift Station Restroom Project as complete, releasing securities, releasing payments totaling $568,374 to Harris Builders, Inc., of Hilmar, CA., and authorizing the City Clerk to file a Notice of Completion. #9..
- 78 -
- 6 -
6/11/2024 5:30:00 PM
Consent

12. Consider approving the updates to the City’s Debt Management Policy. (Funding Source: Not Applicable)
 Resolution approving the updates to the City’s Debt Management Policy.

FINANCE DEPARTMENT; Calogero Maniscalco, 209-577-5219,
[email protected]
ACTION: (Wright/Williams; 7/0) Resolution 2024-234 approving the updates to the City’s Debt Management Policy.

Consent

13. Consider approving the updates to the City’s Investment Policy. (Funding Source: Not Applicable)
 Resolution approving the updates to the City’s Investment Policy.

FINANCE DEPARTMENT; Calogero Maniscalco, 209-577-5219,
[email protected]
ACTION: (Wright/Williams; 7/0) Resolution 2024-235 approving the updates to the City’s Investment Policy.

Consent

14. Consider accepting the Monthly Investment Report for April 2024. (Funding Source:

Various Funds)
 Motion accepting the Monthly Investment Report for April 2024.

FINANCE DEPARTMENT; Calogero Maniscalco, 209-577-5219,
[email protected]
ACTION: (Wright/Williams; 7/0) Motion accepting the Monthly Investment Report for April 2024.

Consent

15. Consider accepting an informational report on the March and April 2024 grant applications and awards (Funding Source: Not Applicable)  Motion accepting an informational report for the March and April 2024, grant applications and awards.

FINANCE DEPARTMENT; Maria Garnica, 209-577-5249,
[email protected]
ACTION: (Wright/Williams; 7/0) Motion accepting an informational report for the March and April 2024, grant applications and awards.

Consent

16. Consider accepting an informational report for the May 2024 Accounts Payable Payment Register and Void Report. (Funding Source: Not Applicable)  Motion accepting an informational report for the May 2024 Accounts Payable Payment Register and Void Report.
#9..
- 79 -
- 7 -
6/11/2024 5:30:00 PM
FINANCE DEPARTMENT; Maria Garnica, 209-577-5249,
[email protected]
ACTION: (Wright/Williams; 7/0) Motion accepting an informational report for the May 2024 Accounts Payable Payment Register and Void Report.

Consent

17. Consider approving an Automatic Aid Agreement with Woodland Avenue Fire Protection District (WFPD) for Modesto Fire Department (MFD) to provide firerelated emergency response to County "Islands" surrounded by the Modesto City limits. (Funding Source: General Fund)
 Resolution approving an Automatic Aid Agreement with Woodland Avenue Fire Protection District (WFPD) for Modesto Fire Department (MFD) to provide fire-related emergency response to County "Islands" surrounded by the Modesto City limits and authorizing the City Manager, or his designee, to execute the Agreement.

FIRE DEPARTMENT; Kevin Wise, 209-572-9590, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-236 approving an Automatic Aid Agreement with Woodland Avenue Fire Protection District (WFPD) for Modesto Fire Department (MFD) to provide fire-related emergency response to County "Islands" surrounded by the Modesto City limits and authorizing the City Manager, or his designee, to execute the Agreement.

Consent

18. Consider approving the proposed Bylaw Amendments for the City of Modesto Youth Commission to increase Commission Members from nine to seventeen and extend the appointment term from one year to two years. (Funding Source: Not Applicable)  Resolution approving the proposed Bylaw Amendments for the City of Modesto Youth Commission to increase Commission Members from nine to seventeen and extend the appointment term from one year to two years.

PRN; Jeremy Rogers, 209-577-5347, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-237 approving the proposed Bylaw Amendments for the City of Modesto Youth Commission to increase Commission Members from nine to seventeen and extend the appointment term from one year to two years.

Consent

19. Consider approving the First Amendment with Adamson Police Products, Los Alamitos, CA, for Ballistic Vests increasing the Agreement amount by $113,416 and extending the term of the Agreement from June 30, 2024, to June 30, 2025. (Funding Source: General Fund)
 Resolution approving the First Amendment with Adamson Police Products, for Ballistic Vests, increasing the Agreement amount by $113,416 to a new total amount of $427,416 and extending the term of the Agreement from June 30, #9..
- 80 -
- 8 -
6/11/2024 5:30:00 PM
2024, to June 30, 2025; and authorizing the City Manager, or his designee to execute the Amendment.

POLICE DEPARTMENT; Jessica Smart, 209-572-9500, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-238 approving the First Amendment with Adamson Police Products, for Ballistic Vests, increasing the Agreement amount by $113,416 to a new total amount of $427,416 and extending the term of the Agreement from June 30, 2024, to June 30, 2025; and authorizing the City Manager, or his designee to execute the Amendment.

Consent

20. Consider approving two Engineering Services Agreements with Carollo Engineers, of Walnut Creek, CA, for the Downtown Sewer Trunk Rehabilitation and the Santa Rosa Sewer Trunk Rehabilitation Projects, in the amount of $935,326, plus $93,534 in additional services, if needed, for a combined amount not to exceed $1,028,860. (Funding Source: Wastewater Fund)
 Resolution approving an Engineering Services Agreement with Carollo Engineers, of Walnut Creek, CA, for the Downtown Sewer Trunk Rehabilitation Project in the amount of $497,892, plus $49,790 in additional services, if needed, for an Agreement total amount not to exceed $547,682; and authorizing the City Manager, or his designee, to execute the Agreement.  Resolution approving an Engineering Services Agreement with Carollo Engineers, of Walnut Creek, CA, for the Santa Rosa Sewer Trunk Rehabilitation Project in the amount of $437,434, plus $43,744 in additional services, if needed, for an Agreement total amount not to exceed $481,178; and authorizing the City Manager, or his designee, to execute the Agreement.  Resolution approving an amendment to the Fiscal Year 2023-24 Multi-Year Program Budget in the amount of $8,431,782 from Wastewater Reserves to fund the Downtown Sewer Trunk Rehabilitation and Santa Rosa Sewer Trunk Rehabilitation Projects.

UTILITIES; Cristian Ciotau, 209-577-5260, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-239 approving an Engineering Services Agreement with Carollo Engineers, of Walnut Creek, CA, for the Downtown Sewer Trunk Rehabilitation Project in the amount of $497,892, plus $49,790 in additional services, if needed, for an Agreement total amount not to exceed $547,682; and authorizing the City Manager, or his designee, to execute the Agreement.

ACTION: (Wright/Williams; 7/0) Resolution 2024-240 approving an Engineering Services Agreement with Carollo Engineers, of Walnut Creek, CA, for the Santa Rosa Sewer Trunk Rehabilitation Project in the amount of $437,434, plus $43,744 in additional services, if needed, for an Agreement total amount not to exceed $481,178; and authorizing the City Manager, or his designee, to execute the Agreement.

ACTION: (Wright/Williams; 7/0) Resolution 2024-241 approving an amendment to the Fiscal Year 2023-24 Multi-Year Program Budget in the amount of $8,431,782 from #9..
- 81 -
- 9 -
6/11/2024 5:30:00 PM
Wastewater Reserves to fund the Downtown Sewer Trunk Rehabilitation and Santa Rosa Sewer Trunk Rehabilitation Projects.

Removed from Consent - Councilmember Bavaro recused
Consent

21. Consider approving an On-Call Electrical Engineering Design Services Agreement with Pezzoni Engineering, Inc, of Modesto, CA for a total amount not to exceed $300,000 over three years, and an On-Call Architectural Design Services Agreement with Red Inc. Architects, of Modesto, CA, for a total amount not to exceed $300,000 over three years. (Funding Source: Various Capital Improvement Program Projects)  Resolution approving an On-Call Electrical Engineering Design Services Agreement with Pezzoni Engineering, Inc., of Modesto, CA for a one-year Agreement with two one-year extension options, for an annual estimated amount of $100,000, and a total amount not to exceed $300,000 over three years; and authorizing the City Manager, or his designee, to execute the Agreement.
 Resolution approving an On-Call Architectural Design Services Agreement with Red Inc. Architects, of Modesto, CA for a one-year Agreement with two one-year extension options, for an annual estimated amount of $100,000, and a total amount not to exceed $300,000 over three years; and authorizing the City Manager, or his designee, to execute the Agreement.

UTILITIES; Edgar Vargas, 209-577-5424, [email protected] ACTION: (Wright/Ricci; 6/0; Bavaro Recused) Resolution 2024-242 approving an On-Call Electrical Engineering Design Services Agreement with Pezzoni Engineering, Inc., of Modesto, CA for a one-year Agreement with two one-year extension options, for an annual estimated amount of $100,000, and a total amount not to exceed $300,000 over three years; and authorizing the City Manager, or his designee, to execute the Agreement.

ACTION: (Wright/Ricci; 6/0; Bavaro Recused) Resolution 2024-243 approving an On-Call Architectural Design Services Agreement with Red Inc. Architects, of Modesto, CA for a one-year Agreement with two one-year extension options, for an annual estimated amount of $100,000, and a total amount not to exceed $300,000 over three years; and authorizing the City Manager, or his designee, to execute the Agreement.

Consent

22. Consider approving an Agreement with Hach Company, Loveland, CO, for Field Services and Parts for a total amount not to exceed $389,405 over three years. (Funding Source: Sewer Operations Fund)
 Resolution approving the Sole Source Agreement with Hach Company, Loveland, CO, for Field Services and Parts for a three year Agreement, for an estimated annual amount of $123,134, and a total amount not to exceed $389,405 over three years and authorizing the Director of Finance, or her designee, the ability to add parts based on the department’s needs, ensuring the #9..
- 82 -
- 10 -
6/11/2024 5:30:00 PM
total amount does not exceed the authorized total; and authorizing the City Manager, or his designee, to execute the Agreement
UTILITIES; Jeff Daniels, 209-577-6255, [email protected] ACTION: (Wright/Williams; 7/0) Resolution 2024-244 approving the Sole Source Agreement with Hach Company, Loveland, CO, for Field Services and Parts for a three year Agreement, for an estimated annual amount of $123,134, and a total amount not to exceed $389,405 over three years and authorizing the Director of Finance, or her designee, the ability to add parts based on the department’s needs, ensuring the total amount does not exceed the authorized total; and authorizing the City Manager, or his designee, to execute the Agreement

COUNCIL COMMENTS & REPORTS
Vice-Mayor Alvarez responded to concerns raised about issues at the King-Kennedy Center, expressing gratitude to those who brought the matter forward. Alvarez promised to investigate the issue personally, acknowledging their connection to the district.

Alvarez stated he would follow up with the individuals affected and appreciates their engagement on the issue.

Councilmember Williams acknowledged not being aware of the issues at the KingKennedy Center earlier and apologized for the inconvenience caused. Williams proceeded to discuss upcoming community events including Juneteenth celebrations and a retirement event for George Garner from the Modesto Symphony Orchestra. Williams invited participation in the upcoming 4th of July parade, highlighting the theme "Red, White and Bloom" and honoring the Modesto Garden Club as Grand Marshal. He also mentioned other community figures and events, and concluded with a moment of silence for the late Bob Gallo, a significant community member.

Councilmember Ricci expressed agreement with fellow Councilmembers Alvarez and Williams regarding the accessibility issues at recent events held at the King-Kennedy Center. He advocates for better access to community groups at the facility. Ricci then discussed a proposed lowrider building program involving local clubs, businesses, and law enforcement, aiming to engage youth and strengthen community-police relations. He also addressed issues at Enslen Park, applauding police efforts and discussing plans for revitalization. Finally, Ricci raised concerns about smoke shops selling contraband substances and calls for continued enforcement to ensure neighborhood safety.

Councilmember Escutia-Braaton greeted from Atlanta, Georgia, where she attended the National Association of Regional Councils annual conference. She highlighted learning best practices to bring back to Modesto and addresses the severe fire season affecting the region, encouraging proactive measures to safeguard against poor air quality. She promoted resources from the Valley Air District and discussed upcoming Independence Day celebrations, emphasizing safe alternatives like drone fireworks funded by a Valley Air Board grant.
#9..
- 83 -
- 11 -
6/11/2024 5:30:00 PM
Councilmember Bavaro acknowledged attending Fire Chief Wise's swearing-in ceremony, marking his 13th year as Fire Chief in Modesto, and congratulated him. He reported on productive neighborhood meetings in Lakewood and Lincoln Estates, discussing community concerns about Measure H funding and public safety. Bavaro also noted ongoing efforts to improve parks in District Four and echoes concerns about local smoke shops, concluding with a proud mention of his cousin's election as the first female Councilmember in Battito, Italy.

Councilmember Wright expressed gratitude for attending the Juneteenth Freedom Day March with Councilmember Williams, highlighting the importance of the event and lamenting the low turnout while celebrating the meaningful conversations held at the Masonic Temple afterward. He warmly welcomed Chief Wise as the new Fire Chief overseeing multiple cities and the county, expressing confidence in his leadership and the fire department's capabilities.

Mayor Zwahlen acknowledged the passing of Bob Gallo, highlighting his and his wife Marie's significant contributions to the community and expressing gratitude for Modesto's acceptance of their family. Mayor Zwahlen mentioned Dos Rios Park, Modesto's latest state park, as a serene natural retreat just 17 minutes from City Hall. The Mayor also celebrated attending a Khmer student graduation and the One Valley Many Stories event at Prospect Theater, emphasizing the diversity and richness of Modesto's community. Finally, Mayor Zwahlen warmly welcomed Chief Wise as the new Fire Chief, noting his recent oath of office and expressing optimism for future city improvements under his leadership.

CITY MANAGER COMMENTS & REPORTS
None.

Recessed: 6:52 p.m.

Reconvened: 6:57 p.m.

NEW BUSINESS

23. Consider approving a Right of Entry Agreement with DignityMoves for the development of a 42-unit bridge housing project on a City-owned parcel located on the corner of 9th and E Street and approving a three-year Lease Agreement with Modesto BHBH LP in the amount of $1 per year for the operation of the Bridge Housing project. (Funding Source: Stanislaus County Funds)
 Resolution approving a Right of Access Agreement with DignityMoves for the development of a 42-unit bridge housing project on a City-owned parcel located on the corner of 9th and E Street and authorizing the City Manager, or his designee, to negotiate and execute the Agreement.
 Resolution approving a three-year lease with Modesto BHBH, LP in the amount of $1 per year for the operations of a 42-unit bridge housing project on #9..
- 84 -
- 12 -
6/11/2024 5:30:00 PM
a City-owned parcel located on the corner of 9th and E Street and authorizing the City Manager, or his designee, to negotiate and execute the Agreement.

CED; Edgar Garcia, 209-577-5211, [email protected] ACTION: (Bavaro/Alvarez; 7/0) Resolution 2024-245 approving a Right of Access Agreement with DignityMoves for the development of a 42-unit bridge housing project on a City-owned parcel located on the corner of 9th and E Street and authorizing the City Manager, or his designee, to negotiate and execute the Agreement.

ACTION: (Bavaro/Alvarez; 7/0) Resolution 2024-246 approving a three-year lease with Modesto BHBH, LP in the amount of $1 per year for the operations of a 42-unit bridge housing project on a City-owned parcel located on the corner of 9th and E Street and authorizing the City Manager, or his designee, to negotiate and execute the Agreement.

MATTERS TOO LATE FOR THE AGENDA
None.

ADJOURNMENT
This meeting adjourned at 7:20 P.M.

All Closed Session matters heard prior to the meeting.

CLOSED SESSION

1. Consider appointing Real Property Negotiator Joseph P. Lopez, City Manager for Properties: APN: 102-012-001 and 102-012-004 Motion appointing Real Property Negotiator Joseph P. Lopez, City Manager for Properties: APN: 102-012-001 and 102-012-004
City Attorney, Jose M. Sanchez, 577-5284, [email protected] ACTION: (Wright/Alvarez; 5/0; Williams, Escutia-Braaton Absent) Motion appointing Real Property Negotiator Joseph P. Lopez, City Manager for Properties: APN: 102-012-001 and 102-012-004
CONFERENCE WITH REAL PROPERTY NEGOTIATORS:
(Pursuant to Section 54956.8 of the Government Code)
Property: 601 Neece Dr., Modesto, CA 95351; APN: 102-012-001 and 102-012-004
Property Owners: City of Modesto
#9..
- 85 -
- 13 -
6/11/2024 5:30:00 PM
Negotiating Parties:

For City: Joseph P. Lopez, City Manager
For Lessee: The Baseball Club of Modesto, LLC
Under Negotiation: Price and Terms of Lease
Attest:____________________________
Diane Nayares-Perez, City Clerk
#9..
- 86 -

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: July 1, 2024
TO: Mayor and City Council
FROM: Colleen Rozillis, City Auditor
SUBJECT: Approval of the Internal Controls Review Report.

CONTACT: Colleen Rozillis, City Auditor, [email protected], 206-302-6795 DESCRIPTION:

Consider accepting the 2024 Citywide Internal Controls Review Report. Funding Source: (Not Applicable)
STRATEGIC PLAN ELEMENT:

The recommended action supports the following 2020-2025 City of Modesto Strategic Plan Initiatives: Goal J: Build a high-performance organization.

BACKGROUND:

The City Council approved a citywide Internal Controls review as a part of the FY23-24 Internal Audit work plan.

DISCUSSION:

As part of the FY24-25 Internal Audit work plan, a citywide Internal Controls Review was conducted between December 2023 and March 2024. The review assessed select key controls in areas deemed to be important to protecting the City’s assets and resources, as well as processing and reporting timely financial information. Controls across most sections were generally designed well and property implemented. There are opportunities to better document the processes and controls in place via policy and procedure documents.

FISCAL IMPACT:

None.

COMMITTEE RECOMMENDATION:

This item was considered by the Audit Committee on April 24, 2024. The Audit Committee approved forwarding this to the City Council for approval.

RECOMMENDED COUNCIL ACTION:

Motion accepting the Internal Controls Review Report.
#10..
- 87 -
City Council, July 9, 2024
Internal Controls Review

Page 2 of 2 ends

Approved by:

Colleen Rozillis, City Auditor
Attachments:

1. City of Modesto Internal Controls Review Report, dated 4/15/2024 #10..
- 88 -
‘
CITY AUDITOR’S OFFICE

FINAL REPORT
City of Modesto

INTERNAL CONTROLS REVIEW
April 15, 2024
Moss Adams LLP
999 Third Avenue, Suite 2800
Seattle, WA 98104
(206) 302-6500
#10..
- 89 -
Internal Controls Review Report

FOR INTERNAL USE OF CITY OF MODESTO ONLY
Table of Contents
Executive Summary 1
Scope and Methodology 3
Internal Controls Review 5
#10..
- 90 -
Internal Controls Review Report | 1

FOR INTERNAL USE OF CITY OF MODESTO ONLY

EXECUTIVE SUMMARY
As part of the fiscal year 2023-2024 internal audit program, the City of Modesto (the City) requested that Moss Adams LLP (Moss Adams) conduct a review of the City’s internal controls framework. The internal controls review took place between December 2023 and March 2024 and focused on assessing select key controls in areas deemed important to protecting the City’s assets and resources as well as processing and reporting timely financial information.

We conducted this internal controls review in accordance with Generally Accepted Government Auditing Standards (GAGAS). Those standards require that we plan and perform the internal controls review to obtain sufficient, appropriate evidence to provide a reasonable basis for our findings and conclusions based on our objectives. We believe the evidence obtained provides a reasonable basis for our findings and conclusions based on our objectives. The internal controls review objectives, scope, methodology, and conclusions are included in the report body.

This internal controls review did not constitute an audit of financial statements in accordance with GAGAS. Moss Adams LLP was not engaged to and did not render an opinion on the City’s internal controls or over financial management systems.

Specific areas where controls were reviewed included:
• Accounts Receivable
• Cash Management
• Financial Reporting, Close, and Reconciliations
• Fixed Assets and Asset Management
• Inventory
• Information Technology (IT) General Controls
• Overall Control Environment
• Payroll and Timekeeping
• Purchasing and Accounts Payable
• Revenue and Billing
The City appeared to have internal controls developed for many functions, and the City was in the process of implementing internal controls for other functions. Some examples of commendable activities that, based on the review performed, appeared to have well-designed internal controls, include:
• Monitoring and reconciliation controls related to:
○ Accounts Receivable
○ Cash Management
○ Financial Reporting, Close, and Reconciliation
○ Overall Control Environment
• Performing occasional surprise cash audits across City departments • Performing timecard audits at the close of each pay period #10..
- 91 -
Internal Controls Review Report | 2

FOR INTERNAL USE OF CITY OF MODESTO ONLY
• Performing weekly blind inventory counts of Central Store inventory • Setting standards for a strong IT security environment • Establishing a strong foundation of accountability and segregation of duties by incorporating a number of review processes across financial-related functional areas Similar to most cities, there is an opportunity to strengthen controls, policies, procedures, and systems. Although minor gaps in internal controls of varying degrees were discovered across six of the ten functions reviewed, the City appears to have a strong internal control environment.

Suggested priorities to address over the next six to 12 months include, but are not limited to:
• Fixed Assets and Asset Management
○ Updating policies and procedures
○ Reconciling newly added fixed assets
• Inventory
○ Updating policies and procedures
○ Developing a process to ensure that an independent review and close-out occurs for Fleet work orders and parts requests
• IT General Controls
○ Confirming which IT assets are disposed of by third-party companies • Payroll and Timekeeping
○ Updating policies and procedures
○ Updating the paid-time-off (PTO) accrual rate change process ○ Reviewing and updating user access to payroll-related forms ○ Defining roles and responsibilities for ensuring that all documentation related to the annual negotiated salary increase is retained
• Purchasing and Accounts Payable
○ Verifying that procurement card (P-Card) users have signed the P-Card Agreement and completed the required training prior to receiving their P-Card #10..
- 92 -
Internal Controls Review Report | 3

FOR INTERNAL USE OF CITY OF MODESTO ONLY

SCOPE AND METHODOLOGY
The scope of our internal controls review included an evaluation of the City’s key internal controls to determine the general adequacy of internal controls and identify areas warranting more in-depth review in the future.

The scope of the internal controls review included the following functional areas:
• Accounts Receivable
• Cash Management
• Financial Reporting, Close, and Reconciliations
• Fixed Assets and Asset Management
• Inventory
• IT General Controls
• Overall Control Environment
• Payroll and Timekeeping
• Purchasing and Accounts Payable
• Revenue and Billing
For each functional area assessed, we conducted a review of key controls which included:
• Identifying control objectives in specific areas and controls that would satisfy each control objective
• Reviewing policies and procedures
• Examining relevant documentation in support of select key controls • Performing control walkthroughs to observe the design of key controls and understand workflow processes
• Obtaining an understanding of the characteristics of each relevant control activity (who performs it, how often it is designed to operate, whether it is designed to mitigate fraud, whether it is a manual or programmed (automated) control, and whether it is a preventive, detective, or corrective control)
• Assessing whether the controls in place would prevent or detect errors • Providing recommendations on key controls that need to be implemented or changed The work performed included interviews with employees involved in managing functions, processing key accounting transactions, and handling physical assets in the following departments:
• Finance
• Human Resources
• Technology Services
• Public Works
#10..
- 93 -
Internal Controls Review Report | 4

FOR INTERNAL USE OF CITY OF MODESTO ONLY
In support of the internal controls review, the matrix provided in Section III provides results by including the:
• Control objective
• Control issue
• Corresponding recommendation
• Likelihood of occurrence
• Impact of occurrence
Likelihood of occurrence is defined as the probability of a negative event occurring. Impact of occurrence is defined as the level of significance if a negative event occurs. Risk levels of low, moderate, or high were used to rate the likelihood of occurrence and impact of occurrence for each finding.

Beyond those controls that have been noted within this report as an issue, additional controls were reviewed without exception. It should be noted that many controls were reviewed multiple times in relevant, separate department reviews, but not all controls or departments were reviewed.

Departments were selected to provide a broad understanding of the City’s control environment. Key controls with exception conditions are reported in this document. #10..
- 94 -
Internal Controls Review Report | 5

FOR INTERNAL USE OF CITY OF MODESTO ONLY

INTERNAL CONTROLS REVIEW
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
A. Fixed Assets and Asset Management
1 The City performs
reconciliations of fixed
assets entered into the
Oracle system to
physically issued tag
numbers to ensure
accuracy and consistency
of fixed asset inventory
records.

The City was not completing a
reconciliation of the asset tag
numbers to the Oracle system
to ensure that all assets were
issued a tag and that the tag
numbers were appropriately
recorded in Oracle. Without this
reconciliation, the risk for asset
loss or theft increases because
assets may not be as easily
located or identified.

The City should develop a process
that would require City staff that are
responsible for overseeing fixed
asset inventory to complete a
monthly reconciliation that would
verify whether fixed assets entered
into Oracle that month were properly
tagged. The process should clearly
define:
● Who is responsible for
performing this reconciliation
● How they should perform and
document the reconciliation
● Where the reconciliation
documentation is maintained
● How they should investigate any
variances
● Who should review and approve
the reconciliation
High Moderate
#10..
- 95 -
Internal Controls Review Report | 6

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
2 The City’s Asset
Safeguarding Directive
includes specific controls
related to preventing asset
loss.

The City’s current Asset
Safeguarding Directive does not
include specific controls
describing the detailed
steps/actions that the City
deploys to prevent asset loss.

The City should update the current
Asset Safeguarding Directive to
include preventative steps relating to
asset loss, which might include:
● Conducting regular inventory
checks to ensure that assets are
accounted for and to identify any
missing or stolen assets
● Implementing access controls to
limit access to assets to
appropriate employees
● Installing surveillance systems to
monitor assets and deter theft or
vandalism
● Providing training to educate
employees about the importance
of safeguarding assets and the
policies in place to protect the
City’s assets
High Moderate
3 Monthly Mass Addition
reports are reviewed, and
evidence of the review is
documented via signature
and date.

Although there was evidence
that the Monthly Mass Addition
reports, which details all asset
additions across the City each
month, were being reviewed,
there was no evidence of who
completed the review and
when.

The City should develop a policy
and procedure around the review of
the Monthly Mass Addition reports
specifically addressing who
completes the review, what the
review is meant to achieve, and a
requirement for the City staff
members completing the review to
sign off and date the report as
evidence that the review was
completed. This formal signoff and
date should signify that the reviewer
believes the Monthly Mass Addition
is complete and accurate. This
review helps to support the financial
High Moderate
#10..
- 96 -
Internal Controls Review Report | 7

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
reporting and asset safeguarding
functions at the City.
4 The City's record retention
policy includes a retention
requirement for
documents/records
relating to asset auctions.

During our assessment of the
supporting documentation for a
recent City auction, the City
was able to provide the
supporting Equipment Auction
List; however, the email
correspondence from Accounts
Receivable, which provides
notification that the assets were
ready for auction, could not be
provided. The supporting email
is meant to ensure that the
correct assets are identified for,
and included in, the auction.

The City should review its record
retention policy to ensure that the
requirements for disposed asset
records are maintained for at least
six years after the disposal date
based on best practices set by
Generally Accepted Recordkeeping
Principles. The policy should
address what supporting
documentation must be maintained
to support auctioned assets. Making
these updates will help to promote
better accountability and reliability
that the correct assets are identified
for auction and are the same assets
that end up being auctioned.

High Moderate
B. Inventory
1 Fleet inventory counts are
performed in alignment
with regular inventory
blind counts.

During our preliminary
procedures, we found that the
last fleet inventory count was
performed approximately two
years ago. There are currently
no standards or guidance that
require the fleet inventory to be
a part of the City’s current
annual inventory blind count
procedures.

The City should update its current
inventory reconciliation and count
processes to include the fleet
inventory as part of the annual
inventory blind counts. An annual
count will give the City a more
reliable and accurate count of
inventory while also promoting the
proper safeguarding of assets. The
City should ensure to document the
results of the count each year along
with any variances that are observed
to best address any potential
inventory issues and mitigate
potential risks of loss or theft in the
future.

Moderate Moderate
#10..
- 97 -
Internal Controls Review Report | 8

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
2 Only Fleet Supervisors or
Crew Leads review and
close out work orders and
parts requests within the
AssetWorks system.

For three work orders
assessed, there was no
evidence that the Fleet
Supervisor or Crew Lead closed
out the related parts request.

We verified that the listed
employee on the parts request
was not a Fleet Supervisor or
Crew Lead via the Fleet Crew
Organizational Chart. Without
an independent supervisor
review, there is a risk that parts
could be misappropriated and
not be identified.

The City should develop a process
to ensure that only Fleet Supervisors
or Crew Leads are reviewing and
closing out work orders and parts
requests. The review and close-out
process should help to ensure that
the close-out records are complete.

Having an independent final review
and close-out of work orders and
parts requests will help to instill
segregation of duties, which will help
to protect against potential asset
loss or theft.

The City should consider whether it
can restrict access within the
AssetWorks system for only Fleet
Supervisors or Crew Leads to have
the ability to close work orders and
parts requests.

High Moderate
C. IT General Controls
1 IT assets are properly
disposed of.

The City provided a listing of
the IT assets that were
inventoried for destruction, and
the listing contained evidence
that the City documented the
date the items were picked up
by California Electronic Asset
Recovery (CEAR) for
destruction. However, there
was no corresponding
destruction receipt from CEAR,
which documents the specific IT
assets that were picked up and
subsequently destroyed.

For all IT asset destructions, the City
should request that CEAR provide a
listing of the specific assets that
were picked up and subsequently
destroyed. The destruction receipt
provides evidence that all identified
IT assets were picked up, and
subsequently destroyed, by CEAR
which helps increase accountability,
prevent misappropriation, and
ensure records of IT asset
destructions are complete. The City
should then designate an
independent employee to compare
the listing that was initially sent to
Moderate Moderate
#10..
- 98 -
Internal Controls Review Report | 9

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
CEAR prior to destruction and the
listing that CEAR provides to the
City after destruction to verify that
the listings reconcile (i.e., all IT
assets were provided to CEAR and
destroyed).
2 Daily activity log reviews
are completed, and a
confirmation of completion
is emailed to the IT
Supervisor.

The daily activity log reviews
are intended to identify any
security anomalies, such as an
unauthorized individual trying to
gain access to the City’s
network. Based on interviews,
the daily activity log reviews are
being conducted by IT;
however, there is no
documentation or evidence to
verify that it is being completed.

The City should develop a process
that requires the IT staff member
conducting the daily activity log
review to document its completion
by emailing a confirmation to the IT
Supervisor. The IT Supervisor
should expect this daily email and
contact the IT staff member with any
questions or concerns about that
day’s activity log.

High Low
D. Payroll and Timekeeping
1 Access to adjust paid time
off (PTO) accrual rates is
appropriately restricted
and adjustments to
accrual rates are properly
monitored. In addition,
there is not a defined
process for monitoring
PTO balance adjustments.

The City provides access to all
Payroll employees to change
PTO accrual rates, and there is
not a defined process for a
designated employee to monitor
PTO accrual rates, and
adjustments to those rates, to
ensure that they are
appropriate.

The City should designate a singular
Payroll employee and a secondary
Payroll employee as a backup, if the
employee is unavailable, to have
access to and be responsible for
changing PTO accrual rates.

Restricting access to change these
rates will help to prevent any
unauthorized changes. The City
should review these access levels
regularly, as needed but at least
annually, to ensure they are updated
based on personnel changes or
employee role changes that occur.

As an additional control, the City
should designate a separate
Moderate Low
#10..
- 99 -
Internal Controls Review Report | 10

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
employee to monitor PTO balance
adjustments to ensure that all PTO
changes are appropriate and
properly supported. This review
should be completed once a month
based on the number of PTO
balance adjustments made. The
employee should communicate any
unusual or unsupported PTO
balance adjustments to the HR
Director.
2 PTO accrual rate changes
are monitored and
reviewed by both the
Finance Director and HR
Department.

During our review of the email
correspondence for the Accrual
Rounding for 2024 - 27 Pay
Period, we noted that the HR
Department was not involved in
the correspondence, nor did
they provide a review and
approval of the changes. HR’s
review and approval helps to
ensure that the City is following
current labor regulations.

The City should review its current
PTO accrual change policies and
procedures to ensure that, along
with the Finance Director, the HR
Department is involved with the PTO
accrual change process based on
their extensive knowledge of labor
regulations. Including the HR
Department in these reviews will
help align the City with any changes
to labor regulations that may occur
throughout the year. The HR
Department should designate at
least one individual to monitor and
review PTO accrual rate changes
and document any decisions made
via email.

High Moderate
3 The annual negotiated
salary increase is properly
documented, reviewed,
and approved and the
overall process is
supported by standard
operating procedures
Based on interviews performed,
the HR Department does not
have documentation to
evidence that the annual
negotiated salary increase
review was completed, as this
was done via email and the
related emails were not
The City should update the Across
the Board Increase SOP to ensure
that evidence of this process is
documented and retained for no less
than four years based on the statute
of limitations for legal actions related
to wage and hour claims set by
California through California Labor
High Moderate
#10..
- 100 -
Internal Controls Review Report | 11

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
(SOP) that address
required documentation.
retained. Based on a review of
the City's Across the Board
Increase SOP, the annual
negotiated salary increase
review process must be
documented and that
documentation must be
retained.

Code section 1194. The HR
Department should also develop an
internal process, which includes
defined roles and responsibilities, for
ensuring that all email
correspondence related to the
annual negotiated salary increase
review process is retained. The City
could also consider documenting
this annual review in a form or
memo format, as opposed to email,
to better reduce the risk of
unauthorized changes or any
version control issues that might be
more difficult to address via email.

This form or memo should then be
signed by all parties involved in the
review process to document their
participation in the review and
approval of the resulting salary
increase.
4 Formal policies and
procedures for a City-wide
vacation request process
are well-documented and
current.

Time Off Request Forms are
required for employees
submitting vacation requests,
but there are no formal Citywide policies or procedures that departments are required to
follow to standardize the
process.

The City Manager should use the
Personnel Rules Number 13.4 to
establish a formal City-wide vacation
request policy and procedure for all
City departments that will outline a
formal vacation request process to
require employees to submit a Time
Off Request Form. This policy and
procedure should include:
● The timing of when employees
should submit these requests
(i.e., at least two weeks prior to
the requested time off)
● The preferred method that
employees should submit these
Moderate Low
#10..
- 101 -
Internal Controls Review Report | 12

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
forms to their supervisor (i.e., via
email)
● How the supervisor will review
and approve the forms
● Who will maintain these
approved forms and how they
should be maintained (in case
the Payroll Team or HR
Department requests to see the
approved forms)
5 Access to electronic
Payroll Team forms is
monitored, reviewed, and
updated as needed.

Based on a comparison of the
Payroll organization chart to the
employees listed within the
Electronic Payroll Form Access
List, there were some
employees who had access that
were not part of the Payroll
Team and should not have
access to these sensitive
payroll forms. Unauthorized
access to payroll forms, such as
salary information or other
personnel information, could
subject the City to data privacy
concerns.

The City should develop a process
to ensure that access permissions
for the electronic payroll forms is
reviewed regularly, at least annually
and when personnel changes occur.

The City should also remove any
unauthorized employees from
accessing these forms to ensure
that the electronic payroll forms are
only accessible by employees
whose job requires this access.

Moderate High
E. Purchasing and Accounts Payable
1 P-Card requestors
complete the mandatory
training and sign the PCard Agreement before
receiving access to a PCard.

In our assessment of the
supporting documentation for a
sample of P-Card holders, we
identified one employee that did
not have a signed P-Card
Agreement on file and did not
complete the required training,
but received their P-Card. The
required training ensures that
The City should develop SOPs
detailing how Administrative
Directive 7.27 Procurement Card
Policies and Procedures will be
enforced including a defined
process, and related roles and
responsibilities, for ensuring that all
employees complete the required
training and sign the P-Card
Moderate High
#10..
- 102 -
Internal Controls Review Report | 13

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
employees understand their
role, and related
responsibilities, in utilizing a
City-issued P-Card and the PCard Agreement documents the employee's understanding and
agreement to the terms of use.

Agreement Form prior to receiving a
City-issued P-Card.

The P-Card program administrators
should develop processes to
designate:
● Who will send out the P-Card
Agreement to the employee
● Who will track the incoming
signed agreements
● Who will retain signed
agreements and where they will
be retained
● Who will track which employees
have completed the required
training and how they will track
this
● Who will verify that the employee
has a signed agreement on file
and has completed the required
training prior to handing over the
P-Card
2 The annual review of an
Open Encumbrance
Report is signed and
dated by the Finance
Director, Budget Manager,
and City Manager.

The Finance Director, Budget
Manager, and City Manager will
review an Open Encumbrance
Report prior to year-end close
so that any issues with
purchase orders can be
resolved before the close of the
year. There was a meeting
invite showing that these three
employees met to discuss this
topic; however, there was no
documentation that the review
occurred and what procedures
were performed, such as
The City should develop a process
to document the annual Open
Encumbrance Report review that is
performed by the Finance Director,
Budget Manager, and City Manager.

Documentation should include when
the review was performed, who
participated in the review, any
research performed for identified
issues and the resolution of those
issues. Adding this formal
documentation of the review process
helps to verify that:

High Low
#10..
- 103 -
Internal Controls Review Report | 14

FOR INTERNAL USE OF CITY OF MODESTO ONLY
NO. CONTROL OBJECTIVE CONTROL ISSUE RECOMMENDATION

LIKELIHOOD OF

OCCURRENCE

IMPACT OF

OCCURRENCE
reviewing for purchase orders
that should be closed and
researching and resolving any
identified issues.
● This Open Encumbrance Report
review took place
● The Open Encumbrance Report
review was satisfactory
● Any action items from this review
can be carried out efficiently and
effectively
F. Revenue and Billing
1 Monthly accounts
receivable reconciliations
contain documentation of
who performed the
reconciliation and when it
was performed.

Based on a review of the
supporting documentation for
three monthly accounts
receivable reconciliations, it was
evident that the reconciliations
occurred; however, there was
no documentation of who
completed the reconciliation
and when it was performed.

The City should develop a process
that will require the employee
conducting the monthly accounts
receivable reconciliation to
document its completion, which
could be via system signoff, email to
their supervisor, or physical
signature. The employee should
also ensure to note the date that
they completed the reconciliation to
demonstrate that they completed the
reconciliation timely, which should
be within about 30 days of monthend.

The City should also ensure that the
appropriate supervisor reviews and
approves this monthly reconciliation.

Documentation of approval should
be made via system signoff, email,
or physical signature. This approval
signifies that the supervisor agrees
that the reconciliation is appropriate
and that any item warranting followup discussion have been addressed and documented within the
reconciliation.

High Low
#10..
- 104 -
#10..
- 105 -

CITY OF MODESTO

COUNCIL AGENDA REPORT
DATE OF MEETING:

July 9, 2024
Date: July 1, 2024
TO: Mayor and City Council
THROUGH: Joseph P. Lopez, City Manager
FROM: Scotty Douglass, Deputy City Manager
SUBJECT: Procurement of a Public Safety Computer Aided Dispatch (CAD) System CONTACT: Scotty Douglass, Deputy City Manager, [email protected], 209-577-9149
DESCRIPTION:

Consider approving the purchase of a Public Safety Computer Aided Dispatch (CAD) system and associated public safety mobile and workstation licenses from Central Square Technologies for a total amount not to exceed $2,977,904. (Funding Source: Measure H, Grant Funding) STRATEGIC PLAN ELEMENT:

The recommended action supports the following 2020-2025 City of Modesto Strategic Plan Initiatives: Goal A: Improve community safety and quality of life through a combination of prevention and intervention efforts that address safety and its underlying issues.

BACKGROUND:

The City of Modesto is responsible for providing public safety emergency response to the City’s residents, businesses, and contract agency jurisdictions. To support efficient and effective public safety response to the community, a Computer Aided Dispatch (CAD) system is used by 9-1-1 dispatchers to communicate with responding police and fire resources. The CAD system provides Geographical Information Services (GIS), captures 9-1-1 caller and response information, communicates call details, and provides key recommendations to the dispatcher to ensure proper and accurate resources are sent to emergency calls for service.

On September 1, 1999, the City of Modesto (City) and the County of Stanislaus (County) entered into a Joint Exercise of Powers Agreement (JPA) for Emergency Dispatch Services.

The JPA was established for the purpose of establishing and operating the Stanislaus Regional 911 (SR911) dispatch center that serves the public safety dispatch needs for the City of Modesto and surrounding Stanislaus County agencies. To facilitate the dispatching of emergency personnel and equipment, SR911 purchased a “Dispatch Now” CAD system from Positron, Inc. in 2007 and the CAD was placed into service in 2011. Since this time, “Dispatch Now” has changed owners five times, now owned by Central Square Technologies (Central Square).
#11..
- 106 -
City Council, July 9, 2024
Procurement of a Public Safety Computer Aided Dispatch (CAD) System

Page 2 of 5 ends

In October of 2022, SR911 received a letter from Central Square stating that the “Dispatch Now” CAD system was scheduled to be retired on November 1, 2023. Furthermore, Central Square advised that beginning November 1, 2022, Central Square would only support critical system functionality on the existing “Dispatch Now” system, and that after November 1, 2023, no support would be provided.

Because SR911 and other U.S.-based users of “Dispatch Now” expressed serious concern over the timing of this notice, Central Square rescinded the letter and stated they would extend critical functionality support for a limited time to allow agencies to transition to a new CAD platform. While support for the “Dispatch Now” product continues, it is important to note that the software is two major versions behind, and there is no option to update the current CAD software. The technology is obsolete and the potential for future system failure exists.

Additionally, the current CAD system is unable to support critical technical functionality that is offered by modern CAD systems. Services such as live streaming video, picture and file sharing, advanced Geographical Information Services (GIS) data sharing, cloud-based data sharing, connections to new third-party applications, and advanced database query are not able to connect to the current CAD system. Additionally, the current CAD system is not able to integrate with modern real-time crime center (RTCC) technology.

On November 3, 2023, Kasey Young, Interim Director of SR911, sent the following update to the Consolidated Emergency Dispatch Agency Commission (CEDAC) regarding the current health of the “Dispatch Now” CAD system, reinforcing the need to select a new CAD system immediately.
 SR911 is unable to add more CAD terminals.
 SR911 is unable to add more mobile terminals.
 Reports are not working correctly due to an update needed for an agency change request.
 Most modern applications are unable to be connected due to the old architecture of the current system.
 The CAD system is currently running on unsupported hardware.  The CAD system is running on an unsupported Windows Operating System.  The CAD system is not currently replicated off-site.
 Dispatch CAD workstations are locking up and require rebooting twice a day. The PD01 workstation station has been replaced to minimize lockups.  SR911 is unable to use Google Maps with the current CAD system.  Units are locking up periodically, requiring the dispatcher to employ workarounds while attempting to free locked units.

On March 3, 2024, Modesto Police Department (MPD) Chief Gillespie lobbied several elected officials to support an initiative to integrate smart technologies into an emergency public safety communication platform. At the core of the technology needed was the implementation of a modern CAD system that would connect smart public safety systems to MPD’s RTCC that would result in improved public safety, reducing the need for dangerous high-speed chases, enhancing crime prevention, and enabling the City to increase assistance to the most vulnerable residents in a time of need. As a result, U.S. Congressman Duarte and the late U.S. Senator Feinstein cosponsored an earmark of federal funds to support the procurement of a new CAD system and other necessary infrastructure that would support the future delivery of public safety #11..
- 107 -
City Council, July 9, 2024
Procurement of a Public Safety Computer Aided Dispatch (CAD) System

Page 3 of 5 ends

service to the City of Modesto in the amount of $3.53 million. While these funds have been earmarked, the City of Modesto is still required to submit a grant application for the guaranteed funds. Therefore, the City of Modesto submitted the grant application on June 29, 2024.

DISCUSSION:

On February 7, 2023, the City Manager authorized the Purchasing Manager to solicit the procurement for Computer Aided Dispatch (CAD) System. On December 12, 2019, the City of Glendale, Ca issued a Request for Proposal (RFP)# 121818 for Integrated Public Safety Solution on their vendor-notification portal and the Criminal Justice Information Systems (CJIS) Group distributed procurement documents to all CJIS providers. On January 30, 2019, proposals were opened virtually at The Atlas: Market Edge formerly known as CJIS Group and City of Glendale Vendor-notification portal. Three (3) Bids were received and based on the evaluation process of the quantitative and qualitative criteria outlined in the RFP one (1) contract was awarded for this commodity which includes Computer Aided Dispatch (CAD) system. Based on the responsive and responsible proposer offering the Integrated Public Safety Solution as evaluated by the City of Glendale, City staff recommends to award to Central Square, Lake Mary, FL to purchase the CAD System and other components for an amount not to exceed $2,977,904.

Through a strict evaluation process, SR911, in partnership with SR911’s key stakeholders, including the City of Modesto, selected Central Square’s “Enterprise” CAD as the clear modern CAD system to replace “Dispatch Now”. The “Enterprise” CAD system allows for state-of-theart interfaces and streamlines interoperability between agencies, allowing connectivity from several surrounding local government 9-1-1 and medical dispatch centers. Additionally, City of Modesto staff identified a cooperative purchasing agreement to procure the Central Square “Enterprise” CAD system.

On June 26, 2024, the CEDAC approved the replacement of SR911’s “Dispatch Now” CAD system with the state-of-the-art “Enterprise” CAD system. Additionally, the SR911 Interim Executive Director, Kasey Young, was given authority to work with City of Modesto staff to procure the CAD system through the City using Federal Grant funds. As noted, it is critical to replace the current “Dispatch Now” CAD system, and it is recommended and supported by both the City staff and the SR911 CEDAC to procure the “Enterprise” CAD system from Central Square using earmarked Federal Grant funds. To ensure continuity of regional dispatch services, it will be important for the City to establish long-term use agreements with the County of Stanislaus, SR911 and other public safety user agencies dispatched through the regional dispatch center.

If approved, the City Manager would enter into negotiations with Central Square to procure the “Enterprise” CAD system utilizing Measure H funds that would be significantly reimbursable by grant funds in October of 2024. Upon notice to proceed to Central Square Technologies, it is estimated that a standard implementation would take approximately 12 months to complete.

Modesto Municipal Code Section 8-3.203 generally requires all purchases that meet or exceed $100,000 for material, equipment or contractual services to be formally bid. However, exceptions to the formal bidding process are granted in MMC 8-3.204(d) “Where the Purchasing Manager, in her discretion, determines that a process other than the formal bid procedure set for in Section 8-3.203 will result in a procurement for the City at the lowest possible cost #11..
- 108 -
City Council, July 9, 2024
Procurement of a Public Safety Computer Aided Dispatch (CAD) System

Page 4 of 5 ends

commensurate with the desired quality.” In addition, MMC 8-3.202(h) encourages the Purchasing Manager to join with the State of California or other units of government in cooperative purchasing plans when the best cost savings interest of the City would be served.

By utilizing the City of Glendale, CA, the City is complying with the requirements defined under this code for Computer Aided Dispatch (CAD) System.

FISCAL IMPACT:

With the approval of earmarked Federal Grant funds, there is a financial means for the City of Modesto to procure a CAD system to meet the current and future public safety needs of the City. Because these funds would not be available until October of 2024, it is recommended to utilize Measure H designated funds allocated to the Dispatch Project to procure the “Enterprise” CAD system immediately. These funds would then be largely reimbursed by the Federal Grant funds. The remainder of the associated costs would be paid from designated Measure H funds as noted below.

The funds are to be spent as follows:

CentralSquare’s Public Safety Software Suite – Enterprise (CAD) Services $452,645 CAD Hardware, Interfaces, Disaster Recovery $1,292,614
CAD First Year License Fee $381,400
10% CAD Project Contingency $212,665
Subtotal $2,339,324
City of Modesto Public Safety Mobile/Workstation Licenses* $638,580 Grand Total $2,977,904
*City of Modesto specific licenses for mobile and workstations total $127,716 annually. This total represents 5 years of pre-paid software licensing for the City using the designated Public Safety Measure H funds as noted.

As noted above, $2,200,000 of the $3,530,000 is earmarked to purchase a modern CAD system. Accordingly, the City expects to receive the Federal grant funds in the amount of $3,530,000 in October of 2024. The remaining Federal grant funds will be utilized to fully set up and integrate the Realtime Crime Center (RTCC). Furthermore, a 10% contingency is recommended to support the overall CAD project in the amount of $212,665.

It is recommended to use $2,200,000 in grant funding to support the purchase and procurement of the CAD system, plus CAD workstation licenses for use in the dispatch center. The 10% contingency and 5 years of City of Modesto Public Safety Mobile and Workstation Licenses would be supported by Measure H funds designated in the Fiscal Year 2023-24 Measure H Spending Plan making the total amount $2,977,904.

Beyond year one CAD costs, the “Enterprise” CAD annual license fee of $381,400 would be distributed to all agencies supported by the CAD system through the development of long-term use agreements through the cost allocation model for dispatch services through SR911.

Additionally, each agency connecting to the CAD system will be responsible for their cost for workstation, mobile computer and/or smart device software licenses and equipment.

COMMITTEE RECOMMENDATION:

This item has not been presented to a committee or commission.

RECOMMENDED COUNCIL ACTION:
#11..
- 109 -
City Council, July 9, 2024
Procurement of a Public Safety Computer Aided Dispatch (CAD) System

Page 5 of 5 ends

Resolution approving the competitive bidding process from the City of Glendale with Central Square Technologies, Lake Mary, FL for the purchase of a Public Safety Computer Aided Dispatch (CAD) system and associated components with Central Square Technologies for a total amount not to exceed $2,977,904; authorizing the City Manager or his designee to negotiate and enter into an agreement with Central Square Technologies; to carry out any necessary budget adjustments to implement the approved funding for the purchase and negotiate and enter into agreements with the County of Stanislaus, Stanislaus Regional 9-1-1 (SR911) and those agencies dispatched by SR911, allowing the agencies to use the CAD system at their cost.

Approved by:

Scotty Douglass, Deputy City Manager
Joseph P. Lopez, City Manager
Attachments:

1. Resolution –

2. Central Square Technologies Quote for Enterprise CAD System

3. Letter from Congressman Duarte’s Office Supporting the City of Modesto’s Dispatch Project

4. City of Glendale RFP

5. RFP Proposal Submittal CentralSquare

6. RFP 121818 Scoring Abstract
#11..
- 110 -
07/092024/CMO/SDouglass/Item X 1 2024-___

MODESTO CITY COUNCIL
RESOLUTION NO. 2024-___

RESOLUTION APPROVING THE COMPETITIVE BIDDING PROCESS FROM

THE CITY OF GLENDALE WITH CENTRAL SQUARE TECHNOLOGIES,

LAKE MARY, FL FOR THE PURCHASE OF A PUBLIC SAFETY COMPUTER

AIDED DISPATCH (CAD) SYSTEM AND ASSOCIATED COMPONENTS WITH

CENTRAL SQUARE TECHNOLOGIES FOR A TOTAL AMOUNT NOT TO
EXCEED $2,977,904; AUTHORIZING THE CITY MANAGER OR HIS

DESIGNEE TO NEGOTIATE AND ENTER INTO AN AGREEMENT WITH

CENTRAL SQUARE TECHNOLOGIES, TO CARRY OUT ANY NECESSARY

BUDGET ADJUSTMENTS TO IMPLEMENT THE APPROVED FUNDING FOR

THE PURCHASE AND NEGOTIATE AND ENTER INTO AGREEMENTS
WITH THE COUNTY OF STANISLAUS, STANISLAUS REGIONAL 9-1-1 (SR911) AND THOSE AGENCIES DISPATCHED BY SR911, ALLOWING THE

AGENCIES TO USE THE CAD SYSTEM AT THEIR COST
WHEREAS, the City of Modesto is responsible for providing public safety emergency response to the City’s residents, businesses and contract agency jurisdictions; and
WHEREAS, a Computer Aided Dispatch (CAD) system is used by Stanislaus Regional 9-1-1 (SR911) dispatchers to communicate with responding police and fire resources to ensure proper and accurate resources are sent to emergency calls for service; and
WHEREAS, the current “Dispatch Now” CAD system has been sunset by Central Square Technologies as of November 1, 2023 and will no longer provide software enhancements or updates; and
WHEREAS, the “Dispatch Now” CAD technology is obsolete and the potential for future system failure exists and the current CAD system is unable to support critical technical functionality that is offered by modern CAD systems; and WHEREAS, the “Dispatch Now” CAD system is in need of immediate replacement; and
#11..
- 111 -
07/092024/CMO/SDouglass/Item X 2 2024-___
WHEREAS, on February 7, 2023, the City Manager authorized the Purchasing Manager to solicit the procurement for Computer Aided Dispatch (CAD) System. On December 12, 2019, the City of Glendale, CA issued a Request for Proposal (RFP)# 121818 for Integrated Public Safety Solution on their vendor-notification portal and the Criminal Justice Information Systems (CJIS) Group distributed procurement documents to all CJIS providers; and
WHEREAS, on January 30, 2019, proposals were opened virtually at The Atlas:

Market Edge formerly known as CJIS Group and City of Glendale Vendor-notification portal. Three (3) Bids were received and based on the evaluation process of the quantitative and qualitative criteria outlined in the RFP one (1) contract was awarded for this commodity which includes Computer Aided Dispatch (CAD) system; and WHEREAS, based on the responsive and responsible proposer offering the Integrated Public Safety Solution as evaluated by the City of Glendale, City staff recommends to award to Central Square Technologies, Lake Mary, FL to purchase the CAD System and other components for an amount not to exceed $2,977,904; and WHEREAS, in March of 2024, the City of Modesto received notice of earmarked Federal Grant Funding in the amount of $3,530,000 cosponsored by U.S. Congressman Duarte and the late U.S. Senator Feinstein, of which, $2,200,000 is designated to support the procurement of a modern CAD system to support the future delivery of public safety service to the City of Modesto residents; and
WHEREAS, the City of Modesto has submitted a grant application for the guaranteed funds on June 29, 2024 and expects the receive the funds in October of 2024; and
#11..
- 112 -
07/092024/CMO/SDouglass/Item X 3 2024-___
WHEREAS, SR911, in partnership with SR911’s key stakeholders, including the City of Modesto, selected Central Square Technology’s “Enterprise” CAD as the clear modern CAD system to replace “Dispatch Now”. The “Enterprise” CAD system allows for state-of-the-art interfaces and streamlines interoperability between agencies, allowing connectivity from several surrounding local government 9-1-1 and medical dispatch centers; and
WHEREAS, SR911’s Consolidated Emergency Dispatch Agency Commission (CEDAC) approved the replacement of SR911’s “Dispatch Now” CAD system with the state-of-the-art “Enterprise” CAD system, providing the SR911 Interim Executive Director, Kasey Young, the authority to work with City of Modesto staff to procure the CAD system through the City using Federal Grant funds; and WHEREAS, to ensure continuity of regional dispatch services, it will be important for the City to establish long-term use agreements with the County of Stanislaus, SR911 and other public safety user agencies dispatched through the regional dispatch center; and
WHEREAS, the City of Modesto designated $2,000,000 in Fiscal Year 2023-24 Measure H funds to improve public safety systems; and
WHEREAS, the City Manager would enter into negotiations and enter into an agreement with Central Square Technologies to procure their flagship “Enterprise” CAD system utilizing designated Measure H funds, of which, up to $2,200,000 would be reimbursed by grant funds in October of 2024, and
#11..
- 113 -
07/092024/CMO/SDouglass/Item X 4 2024-___
WHEREAS, a contingency of 10% is recommended in the amount of $212,665 funded by designated Measure H funds as noted above bringing the total not to exceed amount to $2,977,904; and
WHEREAS, Modesto Municipal Code Section 8-3.203 generally requires all purchases that meet or exceed $100,000 for material, equipment or contractual services to be formally bid. However, exceptions to the formal bidding process are granted in MMC 8-3.204(d) “Where the Purchasing Manager, in her discretion, determines that a process other than the formal bid procedure set for in Section 8-3.203 will result in a procurement for the City at the lowest possible cost commensurate with the desired quality.” In addition, MMC 8-3.202(h) encourages the Purchasing Manager to join with the State of California or other units of government in cooperative purchasing plans when the best cost savings interest of the City would be served. By utilizing the City of Glendale, CA, the City is complying with the requirements defined under this code for Computer Aided Dispatch (CAD) System.

NOW, THEREFORE, BE IT RESOLVED by the Council of the City of Modesto that it hereby approves the competitive bidding process from the City of Glendale with Central Square Technologies, Lake Mary, FL for the purchase of a Public Safety Computer Aided Dispatch (CAD) system and associated components with Central Square Technologies for a total amount not to exceed $2,977,904; authorizing the City Manager or his designee to negotiate and enter into an agreement with Central Square Technologies, in a form approved by the City Attorney; and to carry out any necessary budget adjustments to implement the approved funding for the purchase. #11..
- 114 -
07/092024/CMO/SDouglass/Item X 5 2024-___
BE IT FURTHER RESOLVED, that the City Manager or his designee are authorized to negotiate and enter into agreements with the County of Stanislaus, Stanislaus Regional 9-1-1 (SR911) and those agencies dispatched by SR911, allowing the agencies to use the CAD system at their cost in a form approved by the City Attorney.

The foregoing resolution was introduced at a regular meeting of the Council of the City of Modesto held on the 9th day of July, 2024, by Councilmember XXXX, who moved its adoption, which motion being duly seconded by Councilmember XXXX, was upon roll call carried and the resolution adopted by the following vote:

AYES: Councilmembers:

NOES: Councilmembers: None
ABSENT: Councilmembers: None
ATTEST: _____________________________

DIANE NAYARES-PEREZ, CMC,
City Clerk
(SEAL)
APPROVED AS TO FORM:

BY: ________________________________
JOSE M. SANCHEZ, City Attorney
#11..
- 115 -
#11..
- 116 -
#11..
- 117 -
#11..
- 118 -
#11..
- 119 -
#11..
- 120 -
#11..
- 121 -
#11..
- 122 -
#11..
- 123 -
#11..
- 124 -
#11..
- 125 -
#11..
- 126 -
#11..
- 127 -
#11..
- 128 -
#11..
- 129 -
#11..
- 130 -
#11..
- 131 -
#11..
- 132 -
#11..
- 133 -
#11..
- 134 -
#11..
- 135 -
#11..
- 136 -
#11..
- 137 -
#11..
- 138 -
#11..
- 139 -
#11..
- 140 -
#11..
- 141 -
#11..
- 142 -
#11..
- 143 -
#11..
- 144 -

REQUEST FOR PROPOSAL
For – Integrated Public Safety Solution
RFP NUMBER: 121818
ISSUED: 12/12/2018
DUE DATE/TIME: 1/30/2019 before 5:00 PM
City of Glendale
Police Department
131 N Isabel St
Glendale, CA 91206
#11..
- 145 -

CITY OF GLENDALE POLICE DEPARTMENT

REQUEST FOR PROPOSAL
FOR AN

INTEGRATED PUBLIC SAFETY SOLUTION
Chapter 1: Introduction and Rules of Preparation
Introduction and Overview ................................................................................................................ 1-1 Navigating This Request for Proposals .................................................................................. 1-1 Assumptions and Definitions ................................................................................................. 1-2 Term of Services and Contract .............................................................................................. 1-2 Rules of Preparation ........................................................................................................................... 1-3 Submission of Responses ....................................................................................................... 1-3 Vendor Inquiries .................................................................................................................... 1-3 Non-Mandatory Pre-Proposal Teleconference ....................................................................... 1-4 Modifications to the RFP ....................................................................................................... 1-4 Cost of Offer Preparation ....................................................................................................... 1-4 Confidentiality of Documents ................................................................................................ 1-4 Medium of Document ............................................................................................................ 1-5 Notification of Withdrawal of Proposal ................................................................................. 1-5 Contractual Obligations ......................................................................................................... 1-5 Conflict of Interest and Proposal Restrictions ....................................................................... 1-9 Proposal of Additional Services ........................................................................................... 1-10 News Releases ..................................................................................................................... 1-10 Collusion .............................................................................................................................. 1-10 Gratuities .............................................................................................................................. 1-10 Required Review and Waiver of Objections by Proposers .................................................. 1-10 Nondiscrimination................................................................................................................ 1-11 #11..
- 146 -

CITY OF GLENDALE POLICE DEPARTMENT

REQUEST FOR PROPOSAL
FOR AN

INTEGRATED PUBLIC SAFETY SOLUTION

CHAPTER PAGE
Proposal Errors .................................................................................................................... 1-11 Incorrect Proposal Information ............................................................................................ 1-11 Prohibition of Proposer Terms and Conditions.................................................................... 1-11 Assignment and Subcontracting .......................................................................................... 1-11 Right to Refuse Personnel .................................................................................................... 1-12 Right to Reject Offerings ..................................................................................................... 1-12 Evaluations ........................................................................................................................... 1-12 Rights of the City ................................................................................................................. 1-14 Exceptions to the RFP .......................................................................................................... 1-14 Key Events and Projected Dates .......................................................................................... 1-15 Chapter 2: Background and Vendor Response
Background ......................................................................................................................................... 2-1 About GPD ............................................................................................................................ 2-1 Current Environment ............................................................................................................. 2-1 NIBRS Compliance ............................................................................................................... 2-1 Current Tiburon Software and Subsystems ........................................................................... 2-2 Vendor Response................................................................................................................................ 2-3 Vendor Services Overview .................................................................................................... 2-4 References .............................................................................................................................. 2-9 Software ............................................................................................................................... 2-12 #11..
- 147 -

CITY OF GLENDALE POLICE DEPARTMENT

REQUEST FOR PROPOSAL
FOR AN

INTEGRATED PUBLIC SAFETY SOLUTION

CHAPTER PAGE
System Interfaces ................................................................................................................. 2-16 Licensing .............................................................................................................................. 2-18 Computer Hardware ............................................................................................................. 2-19 Implementation .................................................................................................................... 2-22 Training ................................................................................................................................ 2-24 Documentation ..................................................................................................................... 2-27 Warranty, Support and Maintenance ................................................................................... 2-29 Pricing Forms ....................................................................................................................... 2-34 Exceptions to Terms and Conditions ................................................................................... 2-41 Chapter 3: Technical and Functional Specifications
Instructions.......................................................................................................................................... 3-1 Glossary of Terms .............................................................................................................. 3-146 #11..
- 148 -
#11..
- 149 -
Chapter 1
Introduction and
Rules of Preparation
#11..
- 150 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-1
Introduction
Overview
The Glendale Police Department (GPD) invites your company to submit a written offer that details how your company would supply software and services to fulfill the department’s need for an integrated public safety solution, comprised of the following core technologies:
 Police Computer Aided Dispatch (CAD)
 Police Records Management System (RMS)
 Automated Field Reporting (AFR)
 Associated Hardware, Software, Interfaces, and Services GPD welcomes individual vendors, as well as integrated solution providers, to respond to this request for proposals (RFP). GPD may select a single vendor’s solution (to provide all of the core technologies listed above), or a “best of breed” solution (in which case, GPD will require a single vendor to act as the prime contractor, legally and financially responsible for all hardware, software and services).

Navigating This Request for Proposals
This written Request for Proposals (RFP) states the scope of system requirements and specifies the rules for preparing a response. The RFP includes three chapters, as follows:

Chapter 1 - The current chapter provides a project introduction, and describes the rules for preparing a response.

Chapter 2 - Contains information on the current environment, and presents questions regarding the proposing company's background, qualifications, proposed solution, services to be provided, and costs.

Chapter 3 - Includes functional and technical requirements, with instructions for completing responses to the requirements. Space is provided for the vendor to describe their ability to support each requirement.

The submitted offer must follow the rules stated within this section and the format established within this RFP. Adherence to these rules will ensure a fair and objective analysis of all responses.

Chapter
1 #11..
- 151 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-2
Assumptions and Definitions
The following assumptions and definitions were used in preparing this RFP, and should be adopted by the Proposer:
 The term RFP refers to this Request for Proposals and all of its attachments, including any materials from GPD and relevant third parties.  The terms Vendor, Proposer, and Offeror mean a firm submitting a Proposal in response to this Request for Proposal.
 The term Proposal refers to the materials submitted by the Proposer in response to this RFP.
 The term Consultant refers to term Proposer.
 The term Project refers to the labor, materials, equipment, and services that this RFP describes.
 The term Work refers to the services required by, and reasonably inferable from the Contract, whether completed or partially completed, and includes all other labor, materials, equipment, and services provided or to be provided by the Proposer to fulfill the Proposer’s obligations. The Work may constitute the whole or a part of the Project.
 This RFP is based on the best available information. Information not in this document, and not said to be forthcoming, should be assumed to be unavailable.
 Responding Proposals will be based on the business needs outlined in this RFP and on technical and operational trends in the industry.  Departure from the standards outlined in this RFP must be communicated via written notice to GPD.

Term of Services and Contract
The Project described in this RFP and in the proposed Contract will begin upon the effective date of the Professional Services Agreement and extend until the scope of work has been completed, but no later than December 31, 2020. Following the one-year warranty period, the Proposer will provide five (5) years of support (maintenance), and guarantee the provision of ongoing support for an additional five years.
#11..
- 152 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-3
Rules of Preparation
Submission of Responses
Vendors electing to submit a response to this RFP must prepare and submit a comprehensive response to all requested information. It is understood and agreed upon by the vendor in submitting a proposal that GPD has the right to withhold, until after contract award, all information regarding this procurement, including but not limited to:
the number of proposals received, competitive technical information, competing price information, and GPD evaluation concerns regarding competing proposals.

Number of Copies Required: GPD requires that proposing vendors submit one (1) signed original hardcopy, and one (1) electronic copy (CD, DVD, or portable USB drive).

The electronic copy must include the vendor’s response to Chapter 3 in Microsoft Excel.

In the event of any discrepancies between the electronic and paper copies, the paper copy will take precedence.

Due Date, Time and Delivery Address: Responses must be received by GPD no later than January 30, 2019 at 5:00 pm, addressed to:

Glendale Police Department
131 N Isabel Street
Glendale, CA 91206
Proposals received by GPD after the above date and time will not be considered.

Vendor Inquiries
Please direct all questions concerning this RFP to:

Bill Romesburg (Project Consultant)
[email protected]
PO Box 890513, Temecula, California 92589-0513
(951) 506-9851
(951) 695-4934 (Fax)
The deadline for submitting written questions and comments regarding this RFP is Friday, December 21, 2018 at 5:00pm. Please note that contact with any GPD employees #11..
- 153 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-4
regarding this RFP is expressly prohibited without prior consent. Vendors directly contacting GPD employees will risk elimination from further consideration.

Non-Mandatory Pre-Proposal Teleconference
A Non-Mandatory Pre-Proposal Teleconference will be held at 2:00 pm on Tuesday, December 18, 2018. To participate, vendors must request the GoToMeeting access code and online password from the project consultant via email (send requests to: [email protected]).

The teleconference voice number is:
+1 (571) 317-3112
The online meeting web address is:
https://global.gotomeeting.com/join/544412533
All proposers are strongly encouraged to attend. Written addenda or clarifications that stem from the conference will be issued to all proposing vendors. Notes or minutes of the conference will not be distributed.

Modifications to the RFP
Changes to this RFP shall be made only by formal written amendment(s) issued by GPD.

Any and all addenda issued by GPD shall be considered a part of the specifications submitted to the vendors for preparation of their proposals and should be addressed in the vendor response.

Cost of Offer Preparation
GPD will not pay the vendor any costs incurred in the preparation, printing, demonstration or negotiation process.

Confidentiality of Documents
All documents submitted as part of the vendor's offering will be deemed confidential during the evaluation process. Vendor offerings will not be available for review by anyone other than the GPD evaluation team or its designated technical and operational representatives. Following award of contract, all offerings become public documents and are available for public viewing upon written request.
#11..
- 154 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-5
Medium of Document
The RFP was prepared in Microsoft Word 2016, and Microsoft Excel 2016. The RFP files must be downloaded from the following website:
https://www.glendaleca.gov/government/departments/finance/purchasing/rfp-rfq-page Appropriate narrative clarification of answers is encouraged as needed. However, narrative should be provided on additional pages in order to preserve the original format and pagination (e.g., Exhibits, Attachments, etc.). Any omissions or errors in the submitted offerings are the responsibility of the submitting vendor. Any other duplication or use of this document is prohibited.

Notification of Withdrawal of Proposal
Proposals may be modified or withdrawn prior to the date and time specified for proposal submission by an authorized representative of the vendor with written notice. Proposals submitted will become the property of GPD after the proposal submission deadline.

Contractual Obligations
GPD will require certain contractual obligations (regardless of any current agreements between the vendor and GPD). These terms will include, but are not limited to, the following:

1. Requirement to Meet All Provisions - Each vendor submitting an offer shall meet all the terms and conditions of the RFP. By virtue of its submittal, the vendor acknowledges agreement with and acceptance of all provisions of the RFP specifications. By signing and submitting an original proposal in response to this RFP, the bidder agrees to the city’s standard conditions and terms (contained in Appendix A).

2. Inclusion of Offering - The offer submitted in response to this RFP will be included as part of the final contract with the selected vendor.

3. Accountability - The selected vendor will be required to attend, at a minimum, monthly project status meetings and submit monthly status reports covering such items as progress of work being performed, milestones attained, resources expended, problems encountered and corrective action taken.

4. Warranty - All equipment and software are to be under no-cost warranty for at least one year from the date of system acceptance. If the original warranty provided by the manufacturer is longer than one year, GPD shall receive the benefit of the additional warranty period. The warranty shall require the vendor to be responsible for all cost of parts, labor, field service, and pickup and delivery #11..
- 155 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-6
service charges related to repairs or corrections during the warranty period. There is to be no cost to GPD beyond those identified in the offering. Further information is provided under the “Warranty and Maintenance” subsection of this RFP.

5. Costs - All costs must be detailed specifically in the vendor cost summary section of the offering in US dollars (only); no additional charges (e.g., for transportation, installation, training, out-of-pocket expenses, etc.) will be allowed unless so specified in the offering. Vendors must fill out all appropriate cost pages (or replicas of these pages).

6. System Acceptance - The final contract with GPD will contain items such as performance guarantees for system availability, response time, loading capacity, functionality, along with system acceptance criteria. Some of the specific guarantees required are identified in the Chapter 2. The selected vendor should be prepared to include such items within the scope of services and pricing.

7. Ability to Perform - The selected vendor warrants that it possesses, or has arranged through subcontractors, all capital and other equipment, labor, materials, and licenses necessary to carry out and complete the work hereunder in compliance with any and all federal, state, and local ordinances and regulations.

8. Laws to be Observed - The selected vendor shall keep itself fully informed of and shall observe and comply with all applicable local, State, and Federal laws, regulations, adopted codes, and statutes and regulations regarding civil rights laws and equal opportunity employment during its performance of the work. Neither the contractor nor any subcontractors shall discriminate against any employee or applicant for employment, to be employed in the performance of such contract, with respect to the employee or applicant’s tenure, terms, conditions, or privileges of employment, because of his race, color, religion, sex, disability, or national origin. The selected vendor must comply with all vendor-required terms and conditions as defined by the most recent FBI CJIS Security Policy.

9. Payment of Taxes - The offering costs shall include full compensation for all taxes which the selected vendor is required to pay.

10. Permits and Licenses - The contractor shall procure and pay for all permits, licenses and approvals necessary for the execution of the contract. The contractor shall comply with all applicable local, state, and federal laws, ordinances, rules, orders and regulations related to the performance of the contract.

11. Selection and Award of Contract - The final award of a contract is subject to the approval of GPD and the City Council, which reserves the sole right to select the successful vendor, to reject any and all proposals as non-responsive or unsatisfactory, to award a contract to a vender on criteria other than lowest cost proposal, or to not award a contract at all as a result of the responses to this RFP.

12. Payment Schedule - GPD and the selected vendor will negotiate a payment schedule based on defined and measurable milestones and deliverables. Under no #11..
- 156 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-7
circumstances will payments be made in advance of work performed. GPD will require substantial holdback of contract monies until acceptable performance is demonstrated (a minimum of 10%).

13. Knowledge of Conditions - Before submitting an offering, vendors must carefully examine this RFP and inform themselves thoroughly as to all the difficulties involved in the completion of all work pursuant to the requirements of this document. Pleas of ignorance of conditions or difficulties that may be encountered in the execution of the work pursuant to this document as a result of a failure to make the necessary examinations or investigations shall not be accepted for any failures or omissions on the part of successful vendors to fulfill, nor shall they be accepted as a basis for any claims whatsoever for extra compensation or for the extension of time.

14. Training - GPD and the vendor will develop a mutually agreeable training schedule. Training will be conducted at GPD facilities and consist of both operational and administrative information. Training is a critical issue for GPD personnel. In preparing your response, be prepared to address the number of persons to be trained, estimated hours of training and the availability of training medium materials (including photocopies, electronic formats and video media).

15. Software Defects - The vendor shall promptly correct all software defects for which the vendor is responsible, within a time period agreed upon by GPD and the vendor.

16. Patents and Royalties - Vendor, without exception, shall indemnify and hold harmless GPD, its officers, officials, employees, designated volunteers (reserves) and agents from any liability of any nature or kind, including costs and expenses for or on account of trademark, copyrighted, patented, or non-patented invention, process or article manufactured or used in the performance of the contract, including its use by GPD. If the vendor uses any design, device or materials covered by patent, trademark or copyright, it shall be mutually understood and agreed without exception that the offering prices shall include all royalties or costs arising from the use of such design, device or materials in any way involved in the work.

17. Current Manufacture - Equipment furnished under this specification shall be standard products of manufacturers regularly engaged in the production of such equipment and shall be the manufacturer's latest design. All material and equipment offered shall be new and unused.

18. Prior Use - GPD reserves the right to use equipment and material furnished under this offering prior to final acceptance. Such use shall not constitute acceptance of the work or any part thereof by GPD.

19. Current Version - "Packaged" application and system software shall be the most current published or vendor's version in use, as of date of system delivery. #11..
- 157 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-8

20. Changes - No alteration in any of the terms, conditions, delivery, price, quality, or specifications of items ordered will be effective without the written consent of GPD.

21. Penalties - GPD may wish to include in the final contract penalty provisions for non-performance such as liquidated damages.

22. Unavailability of Funds - If funds are not available to GPD, this award will be postponed, canceled, or phased. GPD makes no guarantee by release of this RFP that any offerings will be selected and/or funded.

23. Background Checks - The successful vendor will be required to authorize the investigation of its personnel proposed to have access to non-public areas of GPD facilities. The scope of the background check is at the discretion of GPD. Proposed staff will be required to provide their full legal name, date of birth and social security number.

24. Notice to Proceed - Will be issued after GPD receives the fully executed contract.

25. Violation of Terms and Conditions - Violations of the terms and conditions contained in this RFP or any resultant contract, at any time before or after the award, shall be grounds for action by GPD which may include, but is not limited to, rejection of a bidder’s proposal.

26. Insurance - The vendor must comply with the insurance requirements located in Appendix A (Standard Agreement Form). The vendor shall not commence work under a resulting contract until he or she has obtained all the required insurance hereunder and has provided GPD with proof of insurance. The vendor shall not allow any subcontractor to commence work on his or her subcontract until all similar insurance required of the subcontractor has been obtained and provided proof of insurance.
a) Proof of the insurance submitted by the vendor to GPD shall not limit, relieve or decrease the liability of the vendor.
b) If by the terms of any insurance includes a mandatory deductible, or if the vendor elects to increase the mandatory deductible amount, the vendor shall be responsible for payment of the amount of the deductible in the event of a paid claim.
c) The vendor shall take out and maintain during the life of this Contract Commercial General Liability Insurance and Commercial Automobile Liability Insurance to protect vendor and any subcontractor performing work covered by this Contract from claims for damages for bodily injury, including death, as well as from claims for property damage, which may arise from operations under this Contract, whether such operation be by the Vendor or by any subcontractor or by anyone directly or indirectly employed by either of #11..
- 158 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-9
them, and the amounts of such insurance shall not be less than limits stated hereinafter.
d) The Commercial General Liability Insurance shall be written on an occurrence basis, and provide Premises/Operations, Products/Completed Operations, Independent Contractors, Personal Injury and Contractual Liability coverage.

The policy shall include GPD, and others as required by the Contract Documents, as an Additional Insured. This policy shall be primary, and any insurance or self-insurance carried by GPD shall be considered excess and non-contributory. The Commercial Automobile Liability Insurance shall be written to cover all Owned, Non-owned and Hired vehicles.

27. Workers’ Compensation - Workers’ Compensation and Employer's Liability Insurance for all of the vendor’s employees to be engaged in work on the project under this Contract and, in case any such work is sublet. The vendor shall require any subcontractor to similarly provide Worker's Compensation and Employer's Liability Insurance for the subcontractor’s employees who are intended to be engaged in such work.

28. Severability - If any provision of this RFP is declared by a court to be illegal or in conflict with any law, the validity of the remaining terms and provisions will not be affected; and, the rights and obligations of the City and Proposers will be construed and enforced as if the RFP did not contain the particular provision held to be invalid.

Conflict of Interest and Proposal Restrictions
By submitting a response to the RFP, the Proposer certifies that no amount will be paid directly or indirectly to an employee or official of the City as wages, compensation, or gifts in exchange for acting as an officer, agent, employee, subcontractor, or consultant to the Proposer in connection with the procurement under this RFP. Notwithstanding this restriction, nothing in this RFP will be construed to prohibit another governmental entity from making a proposal, being considered for award, or being awarded a contract under this RFP. Any individual, company, or other entity involved in assisting the City in the development, formulation, or drafting of this RFP or its scope of services will be considered to have been given information that would afford an unfair advantage over other Proposers, and said individual, company, or other entity may not submit a proposal in response to this RFP.
#11..
- 159 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-10
Proposal of Additional Services
If a Proposer indicates an offer of services in addition to those required by and described in this RFP, these additional services may be added to the contract before contract signing at the sole discretion of the City.

News Releases
News releases pertaining to this project shall not be made available to anyone without prior approval by GPD.

Collusion
By submitting a response to the RFP, each Proposer represents and warrants that its response is genuine and made in the interest of or on behalf of any person not named therein; that the Proposer has not directly induced or solicited any other person to submit a sham response or any other person to refrain from submitting a response; and that the Proposer has not in any manner sought collusion to secure any improper advantage over any other person submitting a response.

Gratuities
No person will offer, give or agree to give any City employee or its representatives any gratuity, discount or offer of employment in connection with the award of contract by the City. No City employee or its representatives will solicit, demand, accept or agree to accept from any other person a gratuity, discount or offer of employment in connection with a City contract.

Required Review and Waiver of Objections by Proposers
Proposers should carefully review this RFP and all attachments, including but not limited to the Standard Professional Services Agreement, for comments, questions, defects, objections, or any other matter requiring clarification or correction. Comments concerning RFP objections must be made in writing and received by the City no later than the Deadline for Written Questions and Comments. This will allow issuance of any necessary amendments and help prevent the opening of defective proposals upon which contract award could not be made. Protests based on any objection will be considered waived and invalid if these faults have not been brought to the attention of the City, in writing, by the Deadline for Written Questions and Comments. #11..
- 160 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-11
Nondiscrimination
No person will be excluded from participation in, be denied benefits of, be discriminated against in the admission or access to, or be discriminated against in treatment or employment in the City’s contracted programs or activities on the grounds of disability, age, race, color, religion, sex, national origin, or any other classification protected by federal or California State Constitutional or statutory law; nor will they be excluded from participation in, be denied benefits of, or be otherwise subjected to discrimination in the performance of contracts with the City or in the employment practices of the City’s contractors. Accordingly, all Proposers entering into contracts with the City will, upon request, be required to show proof of such nondiscrimination and to post in conspicuous places, available to all employees and applicants, notices of nondiscrimination.

Proposal Errors
Proposers are liable for all errors or omissions contained in their proposals. Proposers will not be allowed to alter proposal documents after the deadline for submitting a proposal.

Incorrect Proposal Information
If the City determines that a Proposer has provided, for consideration in the evaluation process or contract negotiations, incorrect information which the Proposer knew or should have known was materially incorrect, that proposal will be determined nonresponsive, and the proposal may be rejected.

Prohibition of Proposer Terms and Conditions
A Proposer may not submit the Proposer's own contract terms and conditions in a response to this RFP. If a proposal contains such terms and conditions, the City, at its sole discretion, may determine the proposal to be a nonresponsive counteroffer, and the proposal may be rejected.

Assignment and Subcontracting
The Contractor may not subcontract, transfer, or assign any portion of the contract without prior written approval from the City. Each subcontractor must be approved in writing by the City. The substitution of one subcontractor for another may be made only at the discretion of the City and with prior, written approval from the City. #11..
- 161 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-12
Notwithstanding the use of approved subcontractors, the Proposer, if awarded a contract under this RFP, will be the prime contractor and will be responsible for all work performed and will be responsible for all costs to subcontractors for services provided by the Proposer. The Proposer is prohibited from performing any work associated with this RFP or using contractors for any service associated with this RFP offshore (outside the United States).

Right to Refuse Personnel
The City reserves the right to refuse, at its sole discretion, any subcontractors or any personnel provided by the prime contractor or its subcontractors. The City reserves the right to interview and approve all Proposers’ staff. Proposer’s staff may be subject to the City’s background and drug testing processes at any time.

Right to Reject Offerings
GPD reserves the right to reject any and all offerings or any part of any offering, to waive minor defects or technicalities, or to solicit new offerings on the same project or on a modified project which may include portions of the originally proposed project as GPD may deem necessary in its interest.

GPD reserves the right to cancel the award of a contract at any time. In all matters relating to the cancellation of this RFP, GPD shall be the sole judge of its best interest and vendor compliance with terms and conditions.

Evaluations
An evaluation team comprised of GPD stakeholders and the consultant will evaluate proposals on a variety of quantitative and qualitative criteria. GPD will evaluate individual product proposals (i.e., RMS-only) as well as integrated solution offerings (i.e., all products). The criteria upon which the evaluation of the proposals will be based includes, but is not limited to, the following. The parentheses indicate the weighted percentage of importance:

1. Adherence of the proposal to the format specified herein; all required information must be provided as indicated herein (2).

2. Completeness of the proposal (5).

3. Quality and depth of references (5).
#11..
- 162 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-13

4. Level of service and responsiveness that the vendor commits to providing to GPD after implementation (5).

5. Financial stability and resources of the vendor (5).

6. Experience and technical expertise of staff (5).

7. Design, capability, and functionality of system and application software as determined by the evaluation team (15).

8. Current availability and ability to demonstrate installation of the proposed software applications required by GPD (5).

9. Level of integration between applications and demonstrated interfaces with external systems/devices (10).

10. Capability, design, reliability, warranty and expandability of proposed hardware (5).

11. Economic feasibility and justification of all costs (10).

12. Vendor willingness and ability to negotiate a contract, including ability to offer project financing and competitive finance terms (10).

13. Feasibility, timeliness and quality of software implementation schedule and conversion plans (5).

14. Level of assistance to be provided to GPD by the vendor during the implementation process as part of the contract (6).

15. The number of hours and extent of user training (5).

16. Quality and extent of the documentation to be provided (2).

Each proposal will be carefully reviewed by the evaluation team based on these 16 criteria. A quantitative score will be assigned to each proposal based on a scale of 100.

The top scoring vendors deemed qualified will be invited to provide an oral demonstration of their proposed solution or products. Following demonstrations, the evaluation team will refine their scoring and identify two semifinalist vendors, who will be invited to provide GPD with a best and final offer (BAFO). The evaluation team will review the BAFO’s and determine which offer best suits the organization. Proposers will provide, in a timely manner, any and all information which GPD deems necessary to make such a decision. GPD will identify a single finalist vendor to enter into contract #11..
- 163 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-14
negotiations. These negotiations could include all aspects of services and fees. If the finalist vendor does not execute a contract with the City within forty-five (45) calendar days after notification of selection, the City may give notice to the vendor of the City’s intent to select from the remaining Proposers or to call for new proposals, whichever the City deems appropriate.

Rights of the City
The City reserves the right to:
• Make the selection based on its sole discretion
• Reject any and all proposals
• Issue subsequent Requests for Proposals
• Postpone opening proposals, if necessary, for any reason • Remedy errors in the Request for Proposal process
• Approve or disapprove the use of particular subcontractors • Negotiate with any, all, or none of the Proposers
• Accept other than the lowest offer
• Waive informalities and irregularities in the proposals • Enter into an agreement with another Proposer in the event the originally selected Proposer defaults or fails to execute an agreement with the City An agreement will not be binding or valid with the City unless and until it is approved by the City Council and executed by authorized representatives of the City and of the Proposer.

Exceptions to the RFP
The format of the RFP must be followed and all requested information must be submitted as indicated. However, GPD is receptive to any additional suggestions pertaining to phasing and scheduling of application development, equipment installation and software implementation, additional related capabilities, and any alternative methods of obtaining any portion of the system requirements. Exceptions raised during contract negotiations that have not been previously declared in the proposal may be grounds for disqualification as deemed appropriate by GPD.
#11..
- 164 -
Glendale PD Integrated Public Safety Solution RFP
Chapter 1: Introduction and Rules of Preparation
1-15
Key Events and Projected Dates
Listed below are target dates by which GPD expects certain events to be complete:

Release of RFP to Vendors December 12, 2018
Non-Mandatory Pre-Proposal Conference (2:00 p.m.) December 18, 2018 Deadline for Written Questions and Comments December 21, 2018 Proposal Submission Deadline (5:00 p.m.) January 30, 2019 Demonstrations (expected) February 4-8, 2019
Finalist Identified February 19, 2019
Selection and Approval by City Council March 26, 2019
Implementation Begins April 1, 2019
#11..
- 165 -
Chapter 2
#11..
- 166 -
Background and
Vendor Response
#11..
- 167 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-1
Background and Vendor Response
Background
About GPD
The City of Glendale, California, is the fourth largest city in Los Angeles County with approximately 30 square miles and over 200,000 residents. GPD employs over 350 professionals, including 238 sworn officers distributed amongst five divisions:

Administrative Services, Field Services, Investigative Services, Support Services, and Office of the Chief. For more information on the organization, visit https://www.glendaleca.gov/government/departments/police-department Current Environment
For the past fifteen years, GPD has relied on a suite of public safety products acquired in 2003 from Tiburon, Inc (now CentralSquare), including: police dispatch, police records management, corrections management system, police automated reporting system, and associated interfaces and services. The Tiburon suite has been configured and customized to fulfill the functional and technical demands of GPD. Tiburon provides ongoing support and maintenance governed by a master support agreement. Due to the system’s age and architecture, there are intrinsic technical and functional limitations associated with the current solution.

NIBRS Compliance
GPD’s current Tiburon RMS/ARS is not a sustainable technology solution, capable of meeting NIBRS/CIBRS certification for the next decade and beyond. In 2018, GPD received a grant from the FBI/NCS-X program to fund the initiative. Therefore, GPD requires that the vendor’s RMS/AFR solution achieve NIBRS certification by January 1, 2021. The new RMS/AFR must be compliant with the technical specifications defined in the FBI’s 2019 NIBRS Technical Specifications, and supplemented by the State of California’s supplemental data elements (CIBRS), as published in May, 2018. The requirements are included in Chapter 3.

Chapter
2 #11..
- 168 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-2
Current Tiburon Software and Subsystems
GPD relies on the following core Tiburon products:

CAD/2000 Police computer aided dispatch
RMS/2000 Police records management system (also referred to as LawRecords) ARS/2000 Automated police reporting system
CMS/2000 Corrections management system
MDS Police mobile data system
Including the following Tiburon subsystems:

CARS Police CAD activity reporting system
GMS Geographic maintenance and support
WebQuery Tiburon’s ad hoc inquiry tool
#11..
- 169 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-3
Vendor Response
The following subsections provide the framework for vendors to supply information to GPD regarding their company, proposed solution and pricing. Vendors are required to respond to all questions in one of two ways:
(a) Provide information where requested directly in the spaces indicated; or (b) Provide information requested in an attachment clearly indicating the page number and item number to which responding.

Adherence to the format of the RFP is required. Vendors who omit responses may be deemed unresponsive and risk being eliminated.
#11..
- 170 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-4
Vendor Services Overview

1. Company Name:

Local Address Serving
GPD:

Headquarters Address:

Representative(s) – Please highlight the authorized negotiator:

Name Title Telephone Email
a. Company Information
(1) How many years has the company actively
participated in public safety software? ________ years
(2) How many employees does the company have?
Nationwide: ____ employees In local office: ____ employees (3) What was the prime vendor's annual gross revenue during the last previous three fiscal years?
Fiscal Year 2016 _________ 2017 _________ To Date __________ (4) Provide a copy of the company's financial statements for the last recorded year. Y/N___
(5) Provide Dun & Bradstreet number
#11..
- 171 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-5

2. Please fill in the appropriate company name in the column next to the product or service to be provided by that vendor.

Provided By
(Vendor Name)
a. Prime Contractor
b. CAD Software
c. Police RMS Software
d. AFR Software
e. CMS (or JMS) Software
f. Application Software Programs
g. Training (describe)
h. External System Interfaces
h. Other (describe)
#11..
- 172 -
2-9
References
Instructions: Complete the reference list as indicated for ten (10) sites that are currently using the proposed system(s). Provide total number of installed sites with similar configuration.

Provide a list of all reference sites (regardless of their stage of implementation). List attached? Y/N Name, Title, Email, Phone Configuration Installed
Approximate
Service
Population
Operational
Applications
Installation
Dates
(1)
(2)
(3)
#11..
- 173 -
2-10
Name, Title, Email, Phone Configuration Installed
Approximate
Service
Population
Operational
Applications
Installation
Dates
(4)
(5)
(6)
(7)
(8)
#11..
- 174 -
2-11
Name, Title, Email, Phone Configuration Installed
Approximate
Service
Population
Operational
Applications
Installation
Dates
(9)
(10)
#11..
- 175 -
GPD Integrated Law Enforcement Solution RFP
Chapter 2: Background and Vendor Response
2-12
Software

1. Does the system provide the ability to modify items, (e.g., fields, elements, objects) visible to user based upon security?
Y/N ______

2. Does the system have user definable fields?
Y/N ______

3. Does the system provide a mechanism for data entry validation? Y/N ______

4. Is the application configurable to enable the customer to create their own new fields without vendor intervention?
Y/N ______

5. Does the system allow for display or removal of data fields without customization?
Y/N ______

6. Describe, in detail, how configuration and/or customization changes are affected by subsequent releases.

7. In an attachment, provide a list of planned enhancements with associated target release dates:

Attached? Y/N ______

8. In an attachment, provide a one-year plan for product development.

Attached? Y/N ______

9. In an attachment, provide a complete list of all standard ad-hoc reports.

Attached? Y/N ______

10. In an attachment, describe how ad-hoc reports are user configurable.

Attached? Y/N ______
#11..
- 176 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-13

11. GPD requires the Offeror to provide Entity Relationship Diagrams (ERDs), data dictionaries, and other data documentation/schematics for the system. Identify whether this information will be provided with the system and summarize the contents that will be provided.

Attached? Y/N ______

12. Describe how the proposed system is in compliance with the current FBI Criminal Justice Information Security (CJIS) Policy and standard security practices, including a description of how the solution encrypts data transmissions (particularly NCIC).

Attached? Y/N ______

13. GPD prefers that the Offeror comply with GPD's security procedures when accessing the system, which include the use of individual user accounts instead of generic role accounts, obtaining access authorization for each access instance, using Virtual Private Networking (VPN) where applicable, and not sharing passwords or other access information. Please explain how you plan on supporting and maintaining the system while meeting these preferences? Attached? Y/N ______

14. GPD requires three system environments: testing, training, and production.

The testing environment will be used to test new versions, new data, and alternative configurations of the system both during implementation (i.e., for Functional Acceptance Tests). The system’s training environment will also be used both during implementation (e.g., to train system users) and post cutover to live operations. The system’s production environment must be fully tested and ready prior to cutover to live operations of the system and will be used as the main operational environment for the system. The three environments should be independent of each other, meaning that transactions occurring in one environment will not impact or modify data contained in the other environments nor impact their performance (i.e., system response times and system availability). Please fully describe the equipment and software contained in each environment, when each environment will be fully operational, and how system users and administrators will be able to access each of these environments.

Attached? Y/N ______

15. Please describe in detail the process of initially installing the system's client applications on fixed and mobile workstations, including all manually performed procedures.

Attached? Y/N ______
#11..
- 177 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-14

16. Please identify the minimum and recommended mobile/wireless workstation configurations necessary to effectively host the clients of the system.

Attached? Y/N ______

17. Offeror shall describe their standards, policies, and procedures for the following:
a. System software upgrades and updates
b. Change control
c. Configuration management
d. System testing and releasing of new system software versions and major patches
Attached? Y/N ______

18. GPD requires that Offerors include in their response to this RFP a "turnkey" system configuration consisting of all computer equipment, interface equipment, server-related communications equipment, server-related cabling, server-related terminals, server-related workstations, server-related printers, files, operating system software, application software, database management systems, databases, etc., necessary to meet the functional and operational requirements of this RFP.

Please explain how the proposed system complies with the specified “turnkey” requirements and identify any exceptions.

Attached? Y/N ______

19. Answer the following questions if your company is proposing a cloud-based solution:
a. Vendor agrees to provide a backup solution following the 3-2-1 rule (3 copies of data, 2 media types, 1 off-site)?
Y/N ______
b. Vendor provides local failover in the event of a local or regional internet outage?
Y/N ______
c. Define the solution’s recovery point objective (RFO). d. Define the solution’s recovery time objective (RTO). #11..
- 178 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-15
e. Define the solution’s bandwidth requirement and maximum latency.

Attached? Y/N ______
#11..
- 179 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-16
System Interfaces

1. Is there a seamless integration between the proposed CAD, RMS, AFR, and mobile devices?
Y/N ______

2. Has the vendor previously interfaced with the California Law Enforcement Telecommunications System (CLETS)?
Y/N ______

3. Has the vendor previously interfaced with the California Department of Justice for submitting criminal statistics (UCR and/or NIBRS)? If so, confirm that the vendor is certified by the State for such purposes.

Y/N ______

4. Has the vendor previously interfaced the CAD/RMS/ARS system with other third part systems? If so, please provide the list? Attachment Location______

5. Unless otherwise specified, GPD will collaboratively develop a single data exchange schema for each of the required data exchanges (interfaces). XMLbased, NIST, National Information Exchange Model (NIEM) conformant exchanges are preferred. Although not all of the data elements agreed upon for a specific data exchange (interface) will contain data in each exchange instance, GPD expects to maintain a set of consistent and valid data exchanges across all of the system’s interfaces. The intent is to keep the interfaces and data exchanges as simple and as standardized as possible. Please explain, in an attachment, how you will participate in this process?
Attachment location ______

6. GPD prefers that proposals conform to criminal justice standards including but not limited to Department of Justice's (DOJ) National Information Exchange Model (NIEM)1
, Global Justice Reference Architecture (JRA)2, and standards developed by the National Institute of Standards and Technology (NIST)3. In particular, the JRA provides a framework for decision making about information sharing solutions by defining highly adaptive justice system service oriented architecture (SOA). Please describe, in an attachment, how the proposed system will conform to these standards?
Attachment location ______

1 http://www.niem.gov/
2 http://it.ojp.gov/default.aspx?area=nationalInitiatives&page=1015 3 http://www.nist.gov/
#11..
- 180 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-17

7. GPD will be responsible for providing adequate network connectivity between the system and the external systems and databases interfaced to the system as described herein. Please identify in your response to this requirement, the bandwidth requirements between the system and externally interfaced systems and databases necessary to effectively accomplish the interfaces. Where the network requirements for a specific interface differ from the requirements identified in the response to this paragraph, the specific network requirements for the interface should be described in the response/explanation for that interface?

Attachment location ______

8. GPD prefers a system that performs any required data formatting and transformation for exchanging information (e.g., discrete data, data streams, files, images, etc.) between system databases and external systems and databases.

Please describe how the proposed system will provide this functionality? Attachment location ______

9. GPD desires a system that is able to notify users if access to an interface or interface network is unavailable. Please confirm that your solution provides such functionality?
Y/N ______

10. Currently, each GPD patrol vehicle is equipped with automatic license plate readers (ALPR). Describe your company’s experience and functional capabilities related to Vigilant Solution’s mobile ALPR, and include associated interface pricing in the pricing sheets at the end of Chapter 2.

Attachment location ______
Y/N ______

11. Currently, GPD is migrating from COBAN to Panasonic tablets. As part of the hardware migration, the department will implement a new in-car video system, with the ability to tag CAD calls (event/incident numbers) with related in-car video. Please describe your company’s experience and functional capabilities related to such functionality for each of the following three in-car video providers: Axon, Utility, WatchGuard. Please include associated interface pricing in the pricing sheets at the end of Chapter 2.

Attachment location ______
#11..
- 181 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-18
Licensing

1. GPD requires site licensing. Confirm that your proposal includes site licensing for the proposed products? If there are any limitations, describe them below:

Y/N ______
#11..
- 182 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-19
Computer Hardware
Although a complete "turnkey” system server configuration is required, GPD retains the right (i.e., option) to purchase any of the equipment, operating system software, databases, and third-party software included in the Offeror’s response to this RFP directly from suppliers.

Should GPD make such direct purchases, it will only acquire equipment and software meeting the Offeror’s specifications. Please describe any impacts in terms of support or costs stemming from GPD exercising this option.

Attached? Y/N ______

1. Server Equipment Requirements
Please provide the minimum required hardware configurations for each system component that will function as a server (e.g., application server, database server, file/print server, message switch).
a. System Information
(1) Vendor
(2) Model
b. CPU
(1) Type (Current/Projected)
(2) Speed (Current/Projected)
c. # CPU’s
(1) Minimum Required (Current/Projected)
(2) Recommended (Current/Projected)
d. Memory
(1) Minimum Required (Current/Projected)
(2) Recommended (Current/Projected)
e. Disk Space Capacity4
(1) Minimum Required (Current/Projected)
(2) Recommended (Current/Projected)
f. Number of Users Supported
g. Operating system
(1) Minimum Required (Current/Projected)

4 Retaining at least 36 months of detailed incident data for CAD servers. #11..
- 183 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-20
(2) Recommended (Current/Projected)
h. Indicate any additional servers in the same product line that represent fully software compatible systems for future growth and capacity.

2. CAD Workstation Requirements
Please provide both the minimum required and recommended configurations for CAD workstations that will allow for proper performance of all proposed application functionality.
a. CPU Type/Speed
(1) Minimum required
(2) Recommended
b. Memory
(1) Minimum required
(2) Recommended
c. Disk Space
(1) Minimum required
(2) Recommended
d. Display Resolution(s)
(1) Minimum required
(2) Recommended
(3) Supported
e. Other Hardware
(1) Required
(2) Recommended
f. Operating System(s)
(1) Recommended
(2) Supported
g. Additional Applications/Software
(1) Required
(2) Recommended
#11..
- 184 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-21

3. RMS/CMS Workstation Requirements – Desktops and Laptops/Mobile Devices Please provide both the minimum required and recommended configurations for laptops and/or mobile devices that will allow for proper performance of all proposed application functionality.
a. CPU Type/Speed
(1) Minimum required
(2) Recommended
b. Memory
(1) Minimum required
(2) Recommended
c. Disk Space
(1) Minimum required
(2) Recommended
d. Display resolution(s)
(1) Minimum required
(2) Recommended
(3) Supported
e. Support for touch screens
(1) Minimum required
(2) Recommended
(3) Supported
f. Other hardware
(1) Required
(2) Recommended
g. Operating System(s)
(1) Recommended
(2) Supported
h. Additional applications/software
(1) Required
(2) Recommended
#11..
- 185 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-22
Implementation

1. Methodology
a. Attach an implementation plan and schedule for a project of similar size and complexity that your company has completed with your offering response. b. Attach a Microsoft Project workplan to the offering that includes the following:
 Specific milestones and deliverables
 Identify assigned resources to each task
 Estimated milestone completion dates
 System design and implementation plan
 Software integration and installation plan
 Detailed test plan
 Detailed training plan
 Follow up and evaluation plan
c. What software modules are typically grouped and installed together? d. What amount of elapsed time in months is typically required to implement a project of this size and complexity?

2. Installation
a. Describe the software installation services included in this offering. b. Describe all customer installation responsibilities. #11..
- 186 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-23
c. Is software installation performed at the client site or at the vendor’s offices? Y/N ______
d. If software installation is performed at the client’s site, is vendor staff onsite to perform the installation, or is it accomplished remotely? e. Define the required GPD staff and related training during implementation, testing and recurring support of the proposed solution:
f. Upon completion of the system design, development, integration and installation, and prior to the start of the functional systems test, GPD requires that vendors conduct unit tests of all software to demonstrate to GPD that the system and its components meet all required functionality and adhere to the specifications and procedures incorporated in the RFP.

Describe any objections:

3. Certification, System and Acceptance Testing
a. The selected vendor is expected to jointly develop mutually agreeable system certification, acceptance and testing procedures. Please describe your approach to such procedures.

4. Implementation Team Resources
a. Describe how you propose to supplement GPD’s project team. Describe the project organization for implementation, including:
 Project organization chart clearly illustrating lines of authority.  Number of resources, the role of each individual, and the expected duration and cost of service for each individual.
 Identification of the (Prime) Vendor project manager responsible for day-to-day operations for the project and on-site activities.  Identification of the technical lead for the project, who will play the primary hands-on leadership role in all technical aspects of the project. b. Include a resume for each member of the proposed implementation team.

#11..
- 187 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-24
Training
Training shall be a combination of direct and “Train the Trainer” method and shall be provided to GPD personnel who shall be responsible for ongoing training of all GPD end users. In addition, supervisory levels will receive training tailored to their purposes, as will the systems staff responsible for administering and maintaining the system. Vendors may propose an alternate training configuration or approach, so long as the training goals are achieved.

1. In summary, describe the training courses, type (e.g., lead instructor, interactive CD), and associated hours which are included with the proposed system?

2. Please list the number of training hours required to reach functional competency for each of the following roles.

Dispatcher
Police Officer
Records Clerk
Detective
Jailer
Crime Analyst
System Administrator

3. Can training be scheduled to accommodate multiple shifts and alternative working hours?
Y/N ______
a. Is there an additional cost associated with this training approach? Y/N ______
#11..
- 188 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-25

4. Indicate the hardware and software training included in this offering. All training costs should be identified in the Pricing Forms section.

Recommended number of:

Hours
Course Description Persons On-Site Off-Site
System Administrator Hardware
operations and System
Management:

System Administrator System
Software and Utilities:

Direct Training to Dispatchers:

Help Desk Training:

Train-the-Trainer Training
(acceptable for RMS, AFR, and
JMS):
#11..
- 189 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-26
Recommended number of:

Hours
Course Description Persons On-Site Off-Site
Other:

Total
a. All data (i.e., incident codes) used in the training examples shall be the actual system and data developed for GPD by the vendor. Please note any objections:

5. Training materials include the following:
a. Instructor Manual(s) Y/N ______
b. Student Training Manual(s) Y/N ______
c. All manuals in MS Word format Y/N ______
d. All manuals in other media format (PDF) Y/N ______
e. Master videos or DVDs of recorded training Y/N ______ #11..
- 190 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-27
Documentation

1. Is the Information Model (e.g., data dictionaries and schema information) provided to clients for all databases? Y/N ______
If yes, describe how and in what form the Information Model is made available to users. That is, is it on CD, the web, hardcopy, etc.?

2. Ability to maintain on-line user-defined documentation and procedures:
a. Provide spell/grammar check capability Y/N
b. Searchable by key words Y/N
c. Download information from existing text files Y/N
d. Glossary of terms Y/N
e. Standard operating procedures Y/N
f. Policies Y/N
g. Statutes and codes Y/N

3. Ability to track User name and revision dates when on-line user documentation is revised/changed Y/N

4. A full set of user documentation should be available detailing the functionality of each application. User documentation should be in narrative form and should be understandable to non-technical users. Also, an on-line version of this documentation is desired to allow key word searching to facilitate location of the needed text.
a. On-line context-sensitive help functions Y/N
b. On-line user-friendly tutorial Y/N
c. Site-specific on-line documentation and user guide Y/N d. Keyboard templates Y/N
e. Field level help Y/N
f. Flyover messages Y/N
#11..
- 191 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-28

5. A full set of technical documentation describing systems design, operations, troubleshooting, and performance tuning should be made available to the system’s administrator.
a. Dispatcher’s Guide Y/N
b. System Manager’s Guide Y/N
c. Other (please describe)

6. GPD will require the selected vendor to place all source code in a third-party escrow account. The account must include all historic and current software releases, documentation for the duration of GPD’s ownership of the vendor supplied products and GPD must reserve unmitigated access to the source code for GPD-only usage.

Vendor Agreement: Y/N_______
#11..
- 192 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-29
Warranty, Support and Maintenance
Complete the warranty and maintenance matrix below based on your proposed approach. Complete one matrix per vendor offering warranty/maintenance services.

Vendor ____________
Proposed Services
System
Software
Application
Software
What is the length of the warranty (months)?
(Warranty must start at acceptance)
What are the hours of warranty coverage (e.g., M-F 0700-1800 PST)? What are the hours of maintenance coverage (after the warranty expires)?
Warranty/Maintenance Services:
• Telephone Support (Y/N)?
• Toll Free “800” number (Y/N)?
• Remote dial-up software diagnostics (Y/N)?
• Automatic monitoring of system (Y/N)?
• Updates, enhancements and bug fixes included (Y/N)?
• How often are enhancements provided?
• User group membership (Y/N)?
• Newsletter (Y/N)?
Service/Support Response Time (hours):
• Via telephone/modem
- Average?
- Guaranteed?
• On-site
- Average?
- Guaranteed?
On-Call “After Hours” Services (e.g., M-F 1800-0700):
• Hourly rate for service personnel?
• Minimum hours charged?
How many years will you guarantee support of the proposed software?
#11..
- 193 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-30

1. Please answer the following regarding the preceding matrix:

List any exceptions or limitations to your proposed warranty/maintenance services for the software as indicated within the matrix.

2. System Maintenance and Operation
a. What are GPD’s obligations following a new release/major redesign of an application?
b. GPD requires that backup, archiving, and patch deployment do not require system interruption. Confirm that your solution meets this requirement.

Y/N _____
c. Define a plan for daily, weekly, monthly backup and archiving:
d. Does the vendor mandate the installation of new releases? Y/N _____ (1) How soon? Months _____
(2) Is there an additional charge for the new release? Y/N _____ (3) Is conversion assistance provided, if necessary? Y/N _____ (4) Is new documentation supplied? Y/N _____
(5) Is additional training provided? Y/N _____
(6) Is maintenance continued for the old release? Y/N _____ (7) If yes, for how long? Months _____
e. Describe your policy and timing for terminating support of client operating system(s), server operating system(s) and database versions. f. Describe problem management and escalation procedures. #11..
- 194 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-31
g. Does the system provide knowledge base keyword search capability to facilitate a search of the knowledge base to facilitate problem resolution? Y/N ______
Describe the support knowledge base format (e.g., web site, distributed media).

3. Post Implementation Support
Support after the new software is introduced is as important to GPD as implementation assistance. Please describe post-implementation system support, including the following:
a. Transition from implementation team to another party? Months _____
b. Describe all parties with which GPD would be working. c. Response procedures for priority vs. non-priority calls d. Hours of service:
e. Remote site support:
#11..
- 195 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-32
f. GPD anticipates a comprehensive support agreement to be forged with the finalist vendor. Please identify your proposed recurring support plans:
g. In an attachment, please include copies of your standard maintenance agreement(s) with option plans shown. Location of attachment:__________ h. Describe how switching between versions of software will be handled:
i. Describe the procedures for trouble notification:
#11..
- 196 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-33
j. Describe the procedures for customer-initiated trouble reporting, status tracking and correction:
k. Describe the procedures for using the 24-hour hotline service:
l. Describe any software or hardware used to assist in technical troubleshooting (indicate any costs in the Pricing Forms):
#11..
- 197 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-34
Pricing Forms
This section requires a detailed price breakdown for the proposed systems. Vendors should provide all prices as firm fixed amounts, except where requested on a different basis. All prices must be detailed. No additional charges (e.g., for sales tax, transportation, container packing, installation, training, out-of-pocket expenses) will be allowed unless so specified. Vendors must complete all applicable price pages in this section or risk disqualification. This section includes the following pricing categories:

1. Total Solution Cost Summaries

2. Computer Hardware

3. Computer System Software

4. Application Software (Base Software and Options)

5. Other Implementation Costs

6. Additional Recommended Software/Services
#11..
- 198 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-35

1. Total Solution Cost Summaries
Provide a summary of costs associated with the proposed system. Any entries in this table should agree with the corresponding detail pages.

One-Time Costs
Description One-Time Price Applicable
Tax (9.50%5) Total Price
Computer Hardware
Computer System Software
Application Software
Other Implementation Costs
Additional Recommended
Software/Services

TOTAL PRICE
$ $ $
Recurring Costs
Description Recurring Price
Applicable
Tax (9.50%) Total Price
Computer Hardware
Computer System Software
Maintenance
Application Software Maintenance
Recurring Costs on Additional
Recommended Software/Services

TOTAL PRICE
$ $ $

5 10.50% effective January, 2019
#11..
- 199 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-36

2. Computer Hardware
List all of the hardware required. The TOTAL PRICE entries in this table should agree with the Computer Hardware Total Price in the Total Solution Cost Summaries tables.

Description Qty Price
Applicable
Tax (9.50%) Total Price
Annual
Maintenance
Expense
TOTAL PRICE $ $ $
#11..
- 200 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-37

3. Computer System Software6
List all of the system software required. The TOTAL PRICE entries in this table should agree with the Computer System Software Total Price in the Total Solution Cost Summaries tables.

Description Version# Qty Price
Applicable
Tax
(9.50%) Total Price
Annual
Maintenance
Expense

TOTAL PRICE
$ $ $ $

6 Any system utilities other than the operating system or database. #11..
- 201 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-38

3. Application Software (Base Software and Options)
List all the application software required. Also, indicate which modules are optional.

The TOTAL PRICE entries in this table should agree with the Application Software Total Price in Total Solution Cost Summaries tables.

Description Version# Qty Price
Applicable
Tax
(9.50%) Total Price
Annual
Maintenance
Expense

TOTAL PRICE
$ $ $ $
#11..
- 202 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-39

4. Other Implementation Costs
List all other costs associated with the system implementation. Prices not identified will not be accepted in a final contract. The TOTAL PRICE in this table should agree with the Other Implementation Costs Total Price in the One-time Costs table.

Description Price
Applicable Tax
(9.50%) Total Price
Software
Modification/Customization
Installation
Systems Integration
Project Management
User Training
Technical Training
Documentation
Data Conversion
Out-of-Pocket-Expenses
Photo-Related Hardware
Other
TOTAL PRICE $ $ $
#11..
- 203 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-40

5. Additional Recommended Software/Services
Provide information and pricing estimates for any additional optional software and services that vendor suggests GPD might consider as part of this procurement. The TOTAL PRICE entries in this table should agree with the Additional Recommended Software/Services Total Price in the Total Solution Cost Summaries tables.

Description Price Applicable Tax
(9.50%)
Total Price
Annual
Maintenance
Expense
(if any)
TOTAL PRICE $ $ $ $
a. Assumptions used to determine estimated optional prices are provided in an attachment?
Y/N ______
b. For any item or service not specified in this solicitation, what are your hourly rates?
Training $ Conversion $
Programming $ Installation $
Design $ Other $
#11..
- 204 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-41
Exceptions to Terms and Conditions
Please describe in detail any exceptions to RFP terms and conditions. #11..
- 205 -
GPD Integrated Public Safety Solution RFP
Chapter 2: Vendor Response
2-42
Chapter 3
Technical and
Functional Specifications
#11..
- 206 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3 -1
Technical and Functional Specifications
Instructions
GPD requires vendors to respond to the technical and functional specifications in electronic form, using the Microsoft Excel workbook available at:
https://www.glendaleca.gov/government/departments/finance/purchasing/rfp-rfqpage For each requirement, select a response from the "Vendor Response" column to inform GPD the degree to which your company will fulfill the requirement. The following defines what each of the six response codes represent in both definition as well as point value:

Vendor
Response Codes Definition
RFP
Point
Value
A Existing: The requirement will be met by proposed
existing software that is installed and operational at
other sites. An “A” response to any requirement
signifies that the proposed system meets the
requirement in a seamless manner. Indirect or implied
solutions will not be coded “A”, nor will functionality that is a configuration option for the client.
5 B Configuration: Requirement will be met by
configuring existing software. All configuration work
specified under this response code must be fulfilled
entirely by the vendor.
4 C Future Version: Requirement will be met by software that is currently under development or in Beta test.

Vendors must agree to have the developmental
functionality in productive use in another client site for at least six (6) months prior to installing the product in the GPD environment. All requirements marked by this
code must be provided to GPD no later than the
beginning of the Functional Test period for the product. 3 Chapter
3 #11..
- 207 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3 -2
D Third Party: Requirement will be met by the use of
proposed software tools, such as a report writer, query language or spreadsheet.
2 E Customization: Requirement will be met by major
modifications to existing software or by new custom
software programming.
1 F Not Available: Requirement cannot, and will not, be provided.
0 NOTE: While comments may be provided for clarification, they may not be used to limit the vendor’s response code selection. In the event it appears to GPD that a comment limits or changes the vendor’s response code selection, it may modify the response code accordingly.
#11..
- 208 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-3
File Number All Sections in This Workbook Contain Required Functionality, unless specifically noted as "OPTIONAL" Vendor Response Comments
A: Dispatch Business Functions
A.1.1 Call Taking Defined: Calls for service (CFS) initiate the CAD process. Callers include citizens or other agencies requesting services from GPD or giving notification of events or activities of concern. A CFS may come from many different points of origin, such as alarm systems, E911 systems, direct calls (7 or 10-digit numbers), walk-ins, stationary alarms, ring down alarms, CAD-to-CAD interfaces, or webbased systems. The service requested by callers will consist of both emergency and non-emergencies.

CAD will have the ability to record the origin of the CFS.

A.1.2 Call Taking Process: Call taking consists of receiving the call, obtaining sufficient and accurate information from the caller, determining whether the call is a duplicate of another call in progress, and recording or updating the CFS in the CAD system. The call taker will be given the ability to apply procedures and guidelines to verify, analyze, classify, and prioritize the call prior to routing the CFS to the dispatcher.

A.1.3 Remotely Create and Update CFS Data: CFS may be created and maintained by remote networked workstations and wireless mobile devices using the mobile data computer (MDC) interface.

A.1.4 Update CFS Data: Information related to an open call will be updated by call takers into the CAD as information becomes available from callers and over-the-air units. This supports reclassification and prioritization of the call. The call receiver or dispatcher is able to enter updated narrative data at any time prior to closing the CFS.

A.1.5 Re-Classify and Re-Prioritization CFS Data: CAD will have a method to allow a CFS to be reclassified and/or re-prioritized by a call taker while the call is open and in-progress. There will also be a method that allows re-classification and/or re-prioritization after the call has been closed. This method will be an assignable right by an administrator.

A.1.6 Assign Call Classification and Priority: Assign a nature code, which will include general classification and subtypes of the call, based upon GPD policy. The call will be prioritized based upon type, applying established guidelines and procedures, to determine the appropriate dispatch and response needs.

A.1.7 Check for Duplicate Calls: The system automatically evaluates the CFS location to determine whether a call is a potential duplicate. The call taker evaluates the information presented by the system with that obtained from the caller to make the final decision regarding duplicate calls. Calls for service are often received by many sources for the same CFS, such as a traffic accident witnessed by two or more #11..
- 209 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-4
people. The CAD will identify the potential duplicate calls, and present the call taker with an option to accept the creation of a duplicate call, or merge and cross reference the call with a pre-existing call (but not a closed call).

A.1.8 Ability to Reopen Calls: The CAD allows call takers to reopen a previously closed call for modification, subject to authorization, and provides audit tracking of any modifications made to the call.

A.1.9 Capture Caller Data: CAD must allow the call taker to enter information from the caller including the type of call (nature of complaint), location of call, and caller details (name, phone, address), as well as comments regarding the incident.

A.1.10 Minimum CFS Data for Dispatch: The minimum information required to open and initiate a CFS is type of call (nature of the complaint), priority, and location of the CFS. Depending upon the priority of the call, when the minimum information has been entered, the CFS will be routed by the CAD to the appropriate dispatcher for handling.

A.1.11 CFS Location Data: Ability to automatically provide the following information when address (full street address and city) is verified:

A.1.11.1 Nearest cross street, by lowest number
A.1.11.2 Geocode (beat or district)
A.1.11.3 Common place name
A.1.11.4 Reporting District (RD)
A.1.11.5 Jurisdiction
A.1.11.6 Premise warning(s)
A.1.11.7 Prior incidents (summary and full detail)
A.1.11.8 High/Low Cross Streets
A.1.12 ANI/ALI Data Population: The CAD will provide fields for all ANI/ALI data from Motorola VESTA, and will extract the ANI/ALI information from the source, and populate the ANI/ALI fields.

The ALI location will populate the CFS location. If the caller’s location (ALI) is not the location of the CFS, the call taker must be able to enter the correct CFS location and validate it.

A.1.13 Utilize Call Disposition:
#11..
- 210 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-5
A.1.13.1 A call taker has the option to close a CFS that does not require the dispatch of resources.

A.1.13.2 The dispatcher is notified by assigned units of their status change using voice or mobile data computer (MDC) transactions.

A.1.13.3 MDC transactions will update CAD to record the unit status and, prior to CFS closure, move the CFS into an “awaiting closure” queue.

A.1.13.4 The CFS will be classified with a specific disposition, generally provided by the primary unit (but every assigned unit will have the ability to add a disposition).

A.1.13.5 When a call is closed, information collected during the CFS will be transferred from the CAD system to the records management system (RMS) export utility. Any updates made by the CAD operators on reopened calls will be automatically transferred to the RMS export utility.

A.1.13.6 In instances where a duplicate call is identified, the dispatcher will be presented with a choice to retain duplicate calls, or have the CAD dispose of one with a cross-reference to the original CFS and the calls will be linked for future retrievability.

A.1.14 Verify Location: The CAD will check the caller's location against current address listings in the geofile system. Locations that are not verified by the geofile will cause the CAD to provide an indication to the call taker that information received may be inaccurate, providing additional information for the dispatcher to relay to the responder. The location format will be a street address (blockface address), intersection, or common place name. Location information for a common place, such as McDonalds, has a street address listing cross-reference that will provide the legal street address. Information will be contained in a geofile, which must include altitude, latitude and longitude. The calltaker will make a selection to verify the correct (intended) address, and the CAD will then populate the address location in the CFS with the location details stored in the geofile. If the caller has provided an address that is not valid in the geobase, but is a valid address, the call taker must be able to force the location by providing the correct city and response district information.

A.1.15 Geofile Capabilities: The geofile will, at a minimum:

A.1.15.1 Import the city’s ESRI map files without dispatch/police-department intervention.

A.1.15.2 Validate locations by x/y coordinates.

A.1.15.3 Discern between apartment buildings and individual apartment numbers (ie, Building 2, Apartment 2).

A.1.15.4 Validate that the location is an actual valid location in the service area. #11..
- 211 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-6
A.1.15.5 Resolve ambiguities while accounting for spelling variations and duplications.

A.1.15.6 Validate intersections.

A.1.15.7 Validate address range(s).

A.1.15.8 Relate common place names to actual addresses.

A.1.15.9 Relate x/y/ z coordinates to an actual address.

A.1.15.10 Transform latitude and longitude to map coordinates for display.

A.1.15.11 Translate call location to GPD reporting district and beat.

A.1.15.12 Translate alias names to actual street names.

A.1.16 Retrieve Person Information: When a person is entered into the CAD, the CAD will search through the CAD database, the RMS databases, CLETS and NCIC to obtain all history available from the automated systems, protection orders, warrants, mental or health issues, gang information, or sex offender registry information. As information is returned to the requestor, he/she will be presented with an option of importing the person information into the relevant CAD person fields.

A.1.16.1 Attach warrant returns to the CFS or event, at dispatcher discretion.

A.1.17 Retrieve Vehicle Information: The CAD will automatically execute an inquiry against any pertinent motor vehicle information (e.g., license plate, VIN) in the RMS database (after the unified RMS has been implemented), CLETS and NCIC when such information has been entered into the CAD as part of a transaction such as a car stop or vehicle check. It will then route any returned data into the incident record and bring the returned data to the attention of the individual who entered the query data.

A.1.18 Retrieve Premise Hazard and History: Relevant historical and tactical information about specific and neighboring premises is obtained from internal (CAD and RMS records) and/or external sources (GIS resources, CLETS, NCIC) for decision support. This information will include: information about previous calls for service at the premise, information on whether the premise has records of registered firearms, information on hazardous materials stored at the location, serious medical information concerning individuals residing at the premise, and other relevant information.

A.1.19 Create Call for Service: A new call for service is recorded in the CAD using information compiled to date. A unique call number is assigned to each CFS.
#11..
- 212 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-7
A.1.20 Correlate to beat: The CAD will retrieve and utilize the patrol area assignment in which the call is located.

A.1.21 Retrieve Alarm Location: Obtain the location of an electronically-generated call from the call source information.

Decision Support
A.1.22 Dispatch Decision Support: The dispatcher is presented with the recommended resources for the selected CFS, based upon preset criteria for the type and priority of the CFS (the vendor will provide sample priorities, types and criteria for GPD to accept or modify during installation). Further information will be considered, such as the history of the location, suspect, and the possibility that hazardous materials may be involved. The CAD recommendation may be overridden by the dispatcher, based on the additional information or by request from officers on the scene. The system may, at the discretion of the dispatcher, perform dispatch decision support, such as assigning an incident number without human intervention.

A.1.23 Review Call Background Information: The dispatcher will consider all information associated with the CFS for the incident type, location, persons involved, etc. to determine whether recommended resources are adequate. The dispatcher must have the option to override the resource response plan if it is determined that the recommendation is inadequate.

A.1.24 Dispatch Resource Decision: Recommended resources are assigned by CAD based on SOPs that factor workload and unit capability with regard to skills and equipment required for the CFS, unit availability, and the proximity of resources.

A.1.25 Retrieve CFS From Call Pending Queue: When a dispatcher selects a call from the pending queue, it will contain all information collected during the call up to the point it is retrieved. Additional information will continue to be added to the call by call takers and dispatchers while the CFS is open.

Calls in the queue are stacked by GPD-defined priority, often based on SOP. The CAD system must allow GPD to determine the sort order of the call pending queue.

A.1.25.1 Officer-Initiated Call Features: In the event of an officer-initiated call, the unit will initiate a call by reporting the event to the dispatcher, who creates a new CFS and places the officer on-scene at an initiated call using the Call Source Officer.

A.1.26 Retrieve Resource Recommendations: Resource recommendations are initially determined based on the call type, priority and location information, and other characteristics of the specific CFS. The call type and priority level are used based on GPD policy and procedure. The dispatcher must review resources recommended by the system. In selecting appropriate resources, the dispatcher will have the option to consider a number of factors, such as proximity to the call location, number of units available, special skills or equipment, and the number and type of other CFS to which officers are responding. #11..
- 213 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-8
A.1.27 Override Resource Requirement: The initial recommendation based upon known criteria will be able to be over-ridden upon receipt of additional information, such as learning that the suspect is known to be armed and dangerous. Override must be recorded in an audit trail.

A.1.28 Determine Resource Availability: On creation of a CFS, available resources are displayed to the dispatcher. The list includes both unassigned units and units that are currently on a call with a lower priority. The dispatcher must have the option to assign any combination of the listed units.

A.1.29 Determine Proximity of Resources: Resource proximity will be based on a closeness calculation, which will be calculated as distance or driving time. Proximity determination must be supported by the AVL interface.

A.1.29.1 Ability to estimate time of travel based on distance and driving time.

A.1.30 Dispatcher Assigned Area: CAD unit recommendation must be based, in part, on dispatcher spanof-control areas.

BOLO
A.1.31 BOLO (Be On The Lookout): CAD must be able to store and process BOLOs. They will be entered by a dispatcher or created by anyone who has been given the required security clearance to create or maintain the BOLO file. Both the RMS and the mobile data device interface must support the creation and transmission of a BOLO. A BOLO must be assigned an expiration date, either by the person who creates it or by the system, and it must be governed by GPD policy. A typical BOLO file would include the nature of the BOLO, priority, date, range of effectiveness, subject person and subject vehicle information, and contact information. There must be a mechanism to search the BOLO, to print it in a report and to purge BOLOs based on date range.

Dispatching Units
A.1.32 Dispatch Units: The units specifically recommended or selected for a CFS will be dispatched by CAD.

A.1.33 Record Unit Activity: The unit status will be updated by the CAD (upon a dispatcher's entry, or a mobile unit's self-assignment) to associate the dispatched unit or units with the CFS, including location and time.

A.1.34 Swap Units: When a unit is reassigned from one call to another (upon a dispatcher's entry, or a mobile unit's self-assignment), the CAD will automatically unassign the unit from the previous call and show him/her on the new call in a single transaction.

A.1.35 Record CFS Activity: The CFS record will be updated to associate the unit or units dispatched as responding units to the call.
#11..
- 214 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-9
A.1.36 Recognize Acknowledgement: The unit assigned to the call will respond to the dispatcher to confirm receipt of the dispatch information. This will be done by voice communication and updated in the CAD by the dispatcher or through mobile data computers.

A.1.37 Alert/Notify Units: The dispatcher will relay information pertaining to calls for service to the appropriate units. This notification has the purpose of informing and raising the awareness of nearby units, designated teams or all officers.

A.1.38 Assign Units: Assigned but available units may be pulled off of current assigned status based on priority levels and the resource needs of the CFS at the discretion of the dispatcher. If all the units are pulled off of a call, the call will be added back into the dispatch queue.

Unit Status Management
A.1.39 Unit Status: Unit status must be continually monitored, updated, and recorded by the dispatcher.

This information will be made available by voice communication and updated manually in CAD by the dispatcher, or through mobile data computers. CAD must record the unit status, destination, CFS number and time of action.

A.1.40 Display Unit Dispatch Status: The current status of units will be available at all times. The display will indicate the unit’s status and assigned calls for service (if any). The display also shows the location or last known location of the unit. In the absence of AVL, the location may be the current call location, the last call location, or the location entered by the dispatcher or MDC. In the case of assigned units, the display will show any alert timer, the CFS type, and priority. Examples include arrived on scene, available, unavailable, and unavailable but assignable. More status types will be configurable.

A.1.41 Record Arrival on Scene: Units responding to the scene communicate to dispatch that they have arrived at the location. This communication will occur through voice radio communication and updated manually in CAD by the dispatcher, or through an MDC transmission that will automatically update CAD to reflect the current status of the responding unit, including time of arrival on scene.

A.1.42 Transport Feature: The CAD application must record any change in unit location along with time stamps, including changes of location associated with the same CFS.

A.1.43 Reassign to Available: When a unit has cleared from the scene and is no longer assigned to the CFS, the unit will automatically be reassigned to an available status. Data received from MDC transmissions will update CAD and reflect the new status of the unit.

CFS and Case Management
A.1.44 Call Management: The call is managed by continually updating the CFS data with any additional information reported by callers or officers on scene. The resource recommendations may be revised based on additional information and may be added or reassigned at the discretion of the dispatcher. #11..
- 215 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-10
A.1.45 Display CFS Data: The CFS will need to be displayed and monitored through CAD. This includes activities such as additional call information and activities reported by the officers. Immediate access to all open calls (including unassigned) will be provided on the CFS status display. When a call is closed (by a dispatcher), it will automatically be removed from the call display.

A.1.46 Update Call Status: The status of the call is updated as new information is received. This will include updating the reported CFS type to the actual CFS type. For example, once the immediate incident is resolved, the responding unit will communicate to the dispatcher that the scene is secured.

A.1.47 Assign RMS incident Number: in addition to the CAD CFS number, an RMS incident number (case number) will be assigned before the call is transferred to the RMS system. The RMS number will be assigned from a data file of incident numbers maintained in the CAD system in coordination with the RMS system. GPD policies in this area must be supported by the CAD system.

A.1.48 Ability to assign case number by any user, recording the individual who requested the DR.

A.1.48.1 Ability to assign multiple DR numbers to a single CFS.

A.1.48.2 Ability to assign a previously-issued DR to a current CFS.

A.1.49 Transfer Basic Incident Data to RMS: Basic incident data must be transferred to RMS, including:

CFS number, RMS Incident (Case) Number, CAD call type, nature of call, date/time of call, location of incident, and persons and vehicles involved. Incident transfer is normally triggered and takes place automatically. The CAD systems will include a feature whereby administrative commands will be executed to transfer either a specific incident or a series of incidents based upon parameters.

A.1.49.1 Ability for agency defined triggers upon which CFS data is transferred to RMS.

A.1.50 CAD provides the ability to enter pursuit data, or Change of Location status updates from multiple workstations including mobile devices and AVL feeds concurrently (“pursuit mode”) Dispositions
A.1.51 Record Disposition: Record the disposition of the call for service. This may include a narrative in addition to the type of disposition.

Messaging Options
A.1.52 Database Inquiries: The CAD will format and send multiple internal (RMS), and external (e.g., CLETS), database inquires to the message switch initiated from one user action. (For example, the user enters a license plate on a form and selects RMS and CDL to query in one step). #11..
- 216 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-11
A.1.52.1 Ability to conduct "superquery" of all internal and external search databases.

A.1.53 Sending Messages to Any Logged-On User: The application will enable users to send text messages to any other logged-on user or unit.

A.1.54 Define Groups of Message Recipients: The proposed application defines groups of message recipients and aliases for groups of message recipients.

A.1.55 CAD Message Prioritization: The proposed application will allow users the ability to mark highpriority messages "to CAD workstation only".

A.1.56 Message Restriction: Except to display information that pertains to the immediate safety of an officer, the application will not automatically display dialog boxes or obscure the user's standard information display unless in response to a user initiated command. For example, if data inquiry return is received, the application will advise the user that it is waiting in a queue. The user must then invoke the display.

A.1.57 Automatic CLETS Return Scanning: System will automatically scan (without user intervention) CLETS returns for hits on any warnings, and provide an audio and visual alert (with agency-defined colors for “hit” words) when the message returns to the CAD workstation and the mobile workstation.

The user must then be able to pull up the results and view them.

A.1.57.1 Ability for all workstations to receive BOLO information based on returns.

A.1.58 Auto notification: The CAD system will notify designated users based on business rules (e.g., officers involved in prior events or conducting an investigation regarding the individual/vehicle/property) when a particular person, vehicle, location or phone number has been entered into an event.

A.1.59 Enterprise CAD Viewing: The system allows authorized users to view the enterprise CAD activity from any workstation (networked or wireless) including mobile devices, with automatic refreshing of real-time data.

A.1.60 Web-enabled Call Taking: CFS may be created and maintained using internet browser for offsite or remote dispatch.

A.1.61 GPD Specific CAD Command Support: The system provides the ability to use GPD-defined incident CAD commands of at least 100 characters in length.

A.1.62 GPD Specific CAD Code Support: The system provides the ability to use GPD-defined CAD activity codes.

A.1.63 CAD Command Recall: The system retains a history of the last twenty (20) commands or actions performed on the CAD workstation and allows the user to view the history of the commands.

A.1.64 Multi-Unit Command Support: The system accepts commands which affect more than a single unit (e.g., placing more than one unit on scene, in a single command). #11..
- 217 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-12
A.1.65 Integration of CAD Alerts/Cautions: The system integrates CAD alerts/cautions by notifying dispatchers when an alert/caution is required based on business rules.

A.1.66 CAD Workstation Configuration: Dispatchers may designate a workstation, or a group of workstations, for the purposes of dispatching, call taking or administrative functions, or any combination thereof.

A.1.67 CAD Multi-functionality: The application must allow the user to have multiple windows open simultaneously and allow the user to navigate between the open windows (e.g., invoke a license inquiry using a different “window” without losing the ability to navigate to the initial working screen).

A.1.68 Message Format and Sending Options: Users will have the option of formatting and sending messages and inquires from the command line.

Unit and Incident Status Monitoring
A.1.69 Ability to monitor real-time unit status on screen separate from incident entry and dispatch functions.

A.1.70 Dedicated status workstation or window will provide real-time continuous unit status and complaint status in a Windows format which is user-sizeable.

A.1.71 Ability to assign status conditions and a location of a unit - units are displayed on status workstation in agency-defined groupings.

A.1.72 Ability to display summary including:

A.1.72.1 Available units
A.1.72.2 Unit Designator
A.1.72.3 Current/Last Location
A.1.72.4 Special Skills or Equipment
A.1.72.5 Unavailable Unit (including reason and location) A.1.73 Ability to query and review calls for service and incidents by:

A.1.73.1 Incident Number
A.1.73.2 Priority
#11..
- 218 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-13
A.1.73.3 Incident Type
A.1.73.4 Unit Designator
A.1.73.5 Incident Location
A.1.73.6 Cross Street(s)
A.1.73.7 Commonplace Name
A.1.73.8 Date and Time Range
A.1.73.9 Vehicle Number (unit)
A.1.73.10 Personnel ID/Badge Number
A.1.73.11 Reporting District
A.1.73.12 Beat
A.1.73.13 Last Five Incidents
A.1.73.14 Case Number
A.1.74 Incident status display should contain the following information:

A.1.74.1 Call Number
A.1.74.2 Incident Type
A.1.74.3 Incident Location
A.1.74.4 Mobile Unit Number
#11..
- 219 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-14
A.1.74.5 Call Sign/Vehicle Number
A.1.74.6 Status
A.1.74.7 Number of minutes in present status
A.1.75 Pending incident queue and active incident list:

A.1.75.1 Display priority order by incident type, number, priority, beat, and CFS number.

A.1.75.2 Elapsed time since receipt of call
A.1.75.3 Ability to select any incident from queue
A.1.75.4 Pending incidents should be visually differentiated for each priority by color A.1.75.5 Display incident by incident and/or unit assigned A.1.76 Ability to cancel a pending event, and search upon them later A.1.77 Ability to append and display additional comments to unit status and CLETS returns A.1.78 User controlled audible and/or visual alerting to dispatchers A.1.78.1 Assigned units not en route within preset time A.1.78.2 Unit status unchanged past a preset time
A.1.78.3 Pending calls in queue over a preset time
A.1.79 Ability to generate incident report number (DR) while call is still open.

A.1.80 Ability to display unit status in colors as defined by users, including:
#11..
- 220 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-15
A.1.80.1 Unit designator
A.1.80.2 Current status
A.1.80.3 Incident Assigned/Report type – full info
A.1.80.4 Time since last status change
A.1.80.5 Location (Full address)
A.1.80.6 Special notation (Cellular phone number, contact phone number, pager number, training, etc.) A.1.80.7 Radio Channel
A.1.80.8 Radio Availability
A.1.81 Ability to prompt dispatcher if more incidents pending exist than are being displayed.

A.1.82 Priority listing of incident queue.

A.1.83 Ability to display incident information in color corresponding to incident priority.

A.1.84 Ability to display unit information in color corresponding to unit status.

A.1.85 Ability to designate any workstation a CAD display workstation with separate viewing areas for unit status and incident status.

A.1.86 Ability for dispatcher to configure both status and incident monitors as follows:

A.1.86.1 Define units to display (including non-City units, Police and/or Special Assignment units, etc.) A.1.86..2 Define order of display (for example, alphabetically, by unit type, area/beat, etc.) A.1.86.2 Display unit status and incidents pending simultaneously #11..
- 221 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-16
A.1.86..3 Display incidents pending in order by priority and time in priority queue A.1.87 Ability for dispatch personnel to log shift changes:

A.1.87.1 Team/organization number (assignment)
A.1.87.2 Personal ID number
A.1.87.3 Area/beat assigned
A.1.87.4 Vehicle ID
A.1.87.5 Radio ID
A.1.87.6 Radio
A.1.87.7 Date/time in
A.1.87.8 Date/time off
A.1.87.9 Mileage in/out
A.1.87.10 Special skills
A.1.87.11 Two-man units
A.1.88 Teams (3 or more), added to a vehicle
A.1.89 Ability to pre-program shift change information
A.1.90 Ability to identify or flag non-departmental units on status monitor A.1.91 Ability to identify units logged on
#11..
- 222 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-17
A.1.92 Ability to track individual (volunteer) responders to incidents (i.e., advised responding) A.1.93 Ability to have flexible area/district boundaries or a number of different area/district plans A.1.94 User-Defined Resource and Telephone List: The CAD will include user-defined and maintained telephone and resource lists (e.g., telephone lists for towing companies, social services, other referral agencies) which are specific to GPD and include:

A.1.94.1 Emergency contacts
A.1.94.2 Business/Agency Name and Type
A.1.94.3 Agency Directory
A.1.94.4 Comments
A.1.94.5 At least Five (5) Phone Number Slots
A.1.94.6 Coverage Area(s)
A.1.94.7 Address
A.1.94.8 Email Address
A.1.94.9 Website
A.1.94.10 Personnel Rosters and Skill Flags
A.1.94.11 Equipment and Supply Resources
A.1.94.12 Emergency Callouts (i.e., Ambulance, Other Agencies, etc.) A.1.94.13 Reverse Directories (MSAG)
A.1.95 Ability to create and maintain data files in support of dispatch operations including:
#11..
- 223 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-18
A.1.95.1 Street Closures
A.1.95.2 Special Equipment File
A.1.95.3 Telephone Number Lists
A.1.95.4 Policies and Procedures
A.1.95.5 Notification Lists
A.1.95.6 Public Agency Referral Lists
A.1.95.7 Special Resources Files
A.1.95.8 Hazardous Materials
A.1.95.9 DOT 90 Files - DOT placard content (49CFR)
A.1.95.10 Officer Hazards
A.1.95.11 Restraining Orders
A.1.95.12 Miscellaneous Narrative
Other Features
A.1.96 Ability to synchronize computer time stamp with logging recorder.

A.1.97 Daily rosters and assignments must be available to Dispatch.

A.1.98 Ability to direct inquiry results to local or remote printer, workstation or MDC.

A.1.99 Ability to track all CLETS/NCIC inquiries and responses for a minimum of twelve months (Searches of same to be controlled by supervisor)
#11..
- 224 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-19
A.1.100 Ability to utilize symbols or characters in unit status display to supplement unit status color A.1.101 Geofile (GIS) data elements allow the agency to control line weights and symbology for ad hoc agency-added content.

NextGen911 Functionality
A.1.102 NextGen911 Functionality: The system will deliver true NG9-1-1 functionality as envisioned by U.S.

Department Of Transportation (“USDOT”), NENA and others). GPD requires that the system be compliant with standards of industry associations, regulatory bodies, carriers and vendors. Vendor must describe how the system will comply with standards as they exist at the time of proposal for such core NG9-1-1 functions as:

A.1.102.1 Emergency Call Routing Function (ECRF)
A.1.102.2 Emergency Services Routing Proxy (ESRP)
A.1.102.3 Emergency Call Routing Proxy (ECRP)
A.1.102.4 Border Control Function (BCF)
A.1.103 NextGen911 Multimedia Requests for Assistance: The system architecture must support multimedia requests for assistance, other than simply voice. Vendor must describe how the system supports multimedia requests and describe industry testing for such requests including:

A.1.103.1 Traditional analog or digital telephone calls A.1.103.2 Wireless calls in compliance with the Federal Communications Commission (“FCC”) Phase I and Phase II mandate for full call integration
A.1.103.3 Voice Over IP (VoIP) in native (SIP) format in compliance with all currently adopted NG9-1-1 standards
A.1.103.4 Short Messaging System (“SMS”) messaging (Cellular Text), video and photo messaging services and other applicable technologies.

A.1.103.5 Instant Messaging (IM)
A.1.103.6 Voice Over IM
A.1.104 NextGen911 Management information Systems Reporting: The system must provide a comprehensive integrated MIS solution that allows GPD to report on real time as well as Historical statistics:
#11..
- 225 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-20
A.1.104.1 The system must provide the ability to customize standard canned reports to tailor the output as the PSAP requires as well as provide the ability to generate custom reports. Reports must be able to be saved and run again at a later time.

A.1.104.2 The system will also provide the ability to schedule reports to be run at specified times and have a method of auto delivery of scheduled reports via email.

A.1.104.3 The MIS solution must be user programmable to allow for partitioning of remote PSAP management information that is retrievable via a secure method by only the PSAP receiving the calls.

A.1.104.4 The MIS solution must support multiple customers.

A.1.105 CAD is compatible with any known NextGen911 applications made available to citizens on SmartPhones.

B. Dispatch System Administration
B.1.0 Geofile
B.1.1 Geofile: The Geofile contains the geographic information that is the basis for many decisions in a communications center. The creation of a comprehensive Geofile is a significant undertaking. The vendor's supplied Geofile will:

B.1.1.1
Validate and standardize location and address information.

B.1.1.2 Provide cross-reference addresses and locations with law enforcement-defined reporting areas, x/y/z coordinates, ZIP codes, and other identifiers.

B.1.1.3
Contain sufficient information to ensure that an address is valid.

B.1.1.4 Provide cross-references to addresses and locations using common place names (e.g., business names, parks, hospitals, and schools) and street aliases.

B.1.1.5 Include information such as direction of travel on particular streets and will identify the side of a street for a specific address.

B.1.1.6
Validate all addresses.

B.1.1.7 Allow GPD to enter and update all Geofile data, including the physical address and the x/y/z coordinates.

B.1.1.8
Support the creation and maintenance of the Geofile using an available mapping/GIS database.

B.1.1.9
Synchronize Geofile information in CAD and RMS, based on established parameters. #11..
- 226 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-21
B.1.2 Logging: CAD will log all actions, including security violations and attempted breeches, errors, changes, and updates. The read-only logs will be viewable and searchable by the system administrator and truncated to manage data storage space.

B.1.3 SOP Table Maintenance: The CAD will provide the following Standard Operating Procedures (SOP) related features:

B.1.3.1 The CAD system must allow the system setup to reflect the SOPs at the time the system is initially installed and to be changed when the GPD SOPs change.

B.1.3.2
SOPs are available for reference online as a CAD help file.

B.1.4 Communication Center Emergency Backup: The proposed CAD solution is capable of supporting a real-time, backup CAD in the event of an emergency that would disable the primary CAD environment.

B.1.5 Multi-Agency Event Coordination: The CAD is capable of supporting multi-agency event coordination during large scale events.

B.1.6 Add Agencies: The CAD provides the capacity to add additional agencies “on the fly” during an emergency operation (specific unit identifier defined by the agency, as well as their assigned dispatcharea).

B.1.7 CAD Catch-Up: in order to recover from an interruption of CAD services, the system must allow users to manually enter activity data that occurred during the service interruption. The dates of the activities must be manually entered and the records flagged as being manually entered.

B.1.8 CAD Catch-Up CFS/RMS Incident Numbering Integrity: The CAD system must provide the capability to ensure that the numbering integrity for CFS numbers and RMS incident numbers is maintained following an outage. Describe how your software handles this (e.g., reserving a block of numbers for catch up incidents).

B.2.0 BOLO Maintenance
B.2.1 BOLO Maintenance: BOLOs in CAD are created and maintained in a data file in CAD and includes the following features:

B.2.1.1 BOLO's may be entered by a dispatcher or may be created by anyone who has been given the required security clearance to create or maintain the file.

B.2.1.2 Both an RMS interface and the mobile data terminal interface will support the creation and transmission of a BOLO.

B.2.1.3 A BOLO will be assigned an expiration date, either by the person who creates it or by the system, based on GPD policy and available system resources.

B.2.1.4 BOLO files include the nature of the BOLO, priority, date, range of effectiveness, subject person and subject vehicle information, and contact information. #11..
- 227 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-22
B.2.1.5 There will be a mechanism to search the BOLO and to print it in a report and to purge the BOLOs out of the date range.

B.2.1.6
BOLO’s will automatically expire based on user-defined timeframes, but will not be deleted.

B.3.0 Supervision and Management Reporting
B.3.1 Dispatch Supervisor Support: The CAD system will provide the supervisor with the ability to monitor CAD activity on and dispatch workstation. If necessary, a supervisor can take direct control over a dispatch position remotely, without leaving the supervisor console.

B.3.2 CAD Management Reporting: CAD includes standard reports that will be run using flexible parameters and includes the following reports, at a minimum (by geographic area):

B.3.2.1
Daily log showing all calls received for the prior 24 Hours from time of printing B.3.2.2
Activity Analysis by specified geographical area and by time period B.3.2.3
CFS Summary by specified geographical area and by time period B.3.2.4
Activity Analysis by day of the week
B.3.2.5
Activity Analysis by hour of the day
B.3.2.6
Activity Analysis by day and Hour
B.3.2.7
Response Time Analysis by specified geographical area and by time period B.3.2.8
Response Time Analysis by call type
B.3.2.9
Time Consumed by call type by hour of the day
B.3.2.10
Workload Activity by resource
B.3.2.11
Workload Activity by group
B.3.2.12
Time Consumed by day of the week and hour of the day
#11..
- 228 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-23
B.3.2.13
Time Consumed by specified geographical area and by time period B.3.2.14
Attempted breaches in security
B.3.3 New Report Creation: New reports will be defined either through the CAD system or a third-party reporting tool and then be stored as a standard report available through the CAD system.

B.3.4 Cross Referencing Data: The CAD reports any data element by any other data element in the system.

B.3.5
Data Export: The CAD includes the ability to export data for use in third-party tools.

B.3.6
Wizards: Wizards are provided that allow for user-generated reports.

Dispatch Interfaces
(Note that all interfaces must be installed and operational on the TEST/TRAIN/PROD servers) C.1.0 Alphanumeric Paging (Paging means SMS text messaging, SMTP email, and alphanumeric paging service)
C.1.1
CLETS/NCIC (via JDIC)
C.1.2
Automatic Vehicle Location (AVL)
C.1.3
Logging and Recording
C.1.4
ESRI GIS/Mapping
C.1.5
Netclock or Network Timeserver
C.1.6
Coplink
C.1.7
Export of Fire CFS to Verdugo Fire Dispatch (Northrop Grumman CAD) E911 Interface Requirements:
#11..
- 229 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-24
C.2.0 In order to support E9-1-1 Interfaces, the CAD system:

C.2.0.1 Will enable incoming E9-1-1 ANI/ALI data to be automatically mapped to corresponding address and phone data fields based on the Master Street Address Guide (MSAG) standard in the CFS event entry form.

C.2.0.2 Will support all E9-1-1 ANI/ALI formats including wireline, WPH1 and WPH2, VoIP, and MultiLine Telephone Systems (MLTS).

C.2.0.3 Will enable the capture of additional fields captured in the CFS event, including ESN, call type (landline, wireless), and ANI/ALI tracking ID (if available).

C.2.0.4 Will use GIS data, if available, to extrapolate the closest geographical attribute (address, intersection, common place).

C.2.0.4.1 The radius used to extrapolate the closest geographical attribute will be a configurable item within the system.

C.2.0.4.2 If GIS data is used to create the caller location, then the offset used to determine the approximate location will be displayed.

C.2.0.5 CAD/Motorola Vesta: The CAD-E911 interface will provide a link between CAD and E911 ANI/ALI Controller. The interface will at minimum:

C.2.0.5.1 Provides a utility to establish a separate ALI E911 queue for each operator’s CAD workstation for calls answered by that telecommunicator.

C.2.0.5.2 Provide an ALI window on the dispatcher's CAD monitor to list the E911 calls that the dispatcher has answered.

C.2.0.5.3
Provide a click-to-enter the ALI fields into the fields of the CAD CFS entry mask.

C.2.0.5.4
Attach the ALI message to the incident record to eliminate paper call logs.

C.2.0.5.5 Meet all Federal/NENA/ATT Standards for E911, Wireless Phase 1 and Phase 2 for heartbeat and ACK/NAK.

C.2.0.5.6 Transmit Phase 1 and Phase 2 Wireless automatically on receipt of CAD call. Plot call on map prior to calls being answered at the CAD position.

All External Databases:

C.3.0 In order to support all of the External Database Interfaces, the CAD system:

C.3.0.1 Will provide configurable query forms and response displays and be able to be custom-built to accommodate different federal, state and local database protocols. #11..
- 230 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-25
C.3.0.2 Will provide authorization to perform various queries, and the ability to read responses definable by the individual agency and by role to the field level.

C.3.0.3 Will allow users to submit queries either with the query form or the command line (if applicable).

C.3.0.4 Will allow users to automatically submit queries for persons and vehicles as part of other data entry processes, such as CFS event creation.

C.3.0.5 Will enable the query request type and the database(s) to be queried to be specified from a predefined list, with automatic narrowing of pertinent databases based on user data input.

C.3.0.6 Will provide intelligent updating of the query forms based on other CAD forms that contain person or vehicle data.

C.3.0.7 Will provide a capability for entering new information into the selected external database(s) provided the external database(s) allow updating.

C.3.0.8 Will provide a method for multiple queries to be submitted through a single form or command. This is sometimes referred to as query spawning or cascading.

C.3.0.9 Will make query responses accessible either through the query response form or from the command line and will be associated with a query response type.

C.3.0.10 Will allow users to submit new queries based on data in the query response to logical links; and, will also reference attachments that are associated with the response, which can be downloaded and viewed. Ideally, CAD will provide the capability to view common industry-standard multimedia filetypes.

C.3.0.11 Will provide the capability to alert dispatchers, PSAP supervisors, and street-level supervisors of “Hot Hit” responses to queries made by units in the field, or data run that exists elsewhere in the CAD system (i.e. in a CFS event).

C.3.0.12 Will provide optional audible and visual alerts that can be configured by the system administrator.

C.3.0.13 Will log all queries and their responses (when permitted) for audit purposes.

C.3.0.14 Will provide the ability to configure alerts for queries run by unauthorized personnel or devices, as well as the ability to monitor multiple queries of the same data or specified data.

Messaging Subsystem:

C.4.0 In order to support the Messaging Subsystem interfaces, the CAD system:

C.4.0.1 Will enable incoming E9-1-1 ANI/ALI data to be automatically mapped to corresponding address and phone data fields based on the Master Street Address Guide (MSAG) standard in the CFS event entry form.
#11..
- 231 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-26
C.4.0.2 Is capable of TCP/IP communication, using industry-standard messaging protocols such as SMS and SMTP.

C.4.0.3 Provides the capability of pre-formatted messages, especially to paging and other handheld devices.

C.4.0.4 Automatically creates an alphanumeric page for selected CAD incidents.

C.4.0.5 Allows a dispatcher to initiate an alphanumeric page for any paging group.

C.4.0.5.1 The information sent in the page will be configurable by the agency and contain the following:

C.4.0.5.1.1 Incident number
C.4.0.5.1.2 Type of incident
C.4.0.5.1.3 Location of incident
C.4.0.6 Provides an administrative mechanism to define paging groups.

C.4.0.7 Includes multiple message types, including email, BOLOs, notifications, tactical command chat rooms, and others.

C.4.0.8 Provides a capability to format and send messages using just-in-time information, such as incident dispatch information, BOLOs or emergency weather alerts, and configurable triggers for these messages (e.g. incident type, assigned resources or location) for configurable recipients (i.e. send the chief a page when a specific incident type occurs at a specified location).

C.4.0.9 Ensures that messaging interfaces make use of the CAD address book.

C.4.0.9.1 The CAD address book allows for defining the types of devices recipients are able to receive messages on; and, has the ability to define a default device, as well as what devices (one, some or all) to receive messages on by day/time/response mode.

C.4.0.10 Provides the ability to include attachments associated with the message that can be downloaded and viewed by operators and recipients. Ideally, CAD should provide a capability to view common industrystandard multimedia file-types.

C.4.0.11 Includes an interface to public awareness messaging systems.

C.4.0.12 Includes an interface to reverse 9-1-1, emergency notification, community notification messaging, and other standalone systems available to be activated by the PSAP or through local emergency #11..
- 232 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-27
management.

C.4.0.13 The system maintains a list of all callers who have elected to be a part of this community alert system. An information message can be created. The system then calls, emails and texts every person on the list and plays or transmits the voice message. There is usually not an actual interface between the CAD system and the reverse 9-1-1 system unless the call list is maintained in the CAD database. A web interface is an option to provide citizens with the ability to add their name to the call list for noncritical incidents.

Additional Interfaces:

C.6.0 In order to support the additional interfaces, the CAD system:

C.6.0.1 Provides access to MDC functions authorized to the field level within each function by system administrators, down to the role level (i.e. an officer may not have access to some functions that a sergeant may have).

C.6.0.2 Is capable of providing silent dispatch orders to a mobile unit, in addition to providing the unit with details of the CFS event, pre-plan information, patient information, premises history information, and other types of relevant information.

C.6.0.3 Enables the mobile unit to, if authorized, self-initiate incidents, self-dispatch incidents from a queue, change its status, query CAD and RMS information, and query local and national databases, such as wanted-person checks.

C.6.0.4 Provides summary incident and resource monitoring capability.

C.6.0.5 Provides the ability for street supervisors in multi-agency, multi-jurisdictional environments to choose what agencies or areas within individual agencies they wish to monitor.

C.6.0.6 Provides the ability for CAD users to drill down into the details of summary incident and resource data, and have the ability to configure what data is displayed, as well as how it is displayed in terms of layout, font, font size, and colors.

C.6.0.7 Provides a day/night mode for mobile users.

C.6.0.8 Provides an integrated mobile mapping client.

C.6.0.9 Provides incident and resource management and monitoring capabilities through the in-car mapping solution.

C.6.0.10 Provides the ability to view real-time AVL data for user-selected units from the mobile client, and the ability to interact with the units identified on the map display. #11..
- 233 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-28
C.6.0.11 Includes messaging and other unit-related functionality.

C.6.0.12 Provides drive directions from the current location to a dispatched incident (or any selected location).

C.6.0.13 Provides mobile search capability for resources and personnel by type of vehicle, status and location.

C.6.0.14 Enables mobile users to search for incidents and locations.

Locational Systems:

C.7.0 In order to support Locational Systems, the CAD system:

C.7.0.1 Shall have a seamlessly integrated computerized map, which is a digitized map (GIS database) supporting Tactical Map Display (TMD).

C.7.0.2 Shall contain a map-centric TMD, in which the GIS/map is fully integrated with the CAD system, and:

C.7.0.2.1 In the case of a separate TMD application linked to the CAD system, the TMD supports the automatic display of units as derived from an AVL system.

C.7.0.3 Shall integrate with aerial imaging technologies to provide digital, oblique, aerial imaging.

C.7.0.4 Shall link high-resolution aerial photos to mapping systems; overlay shape files directly on top of both oblique and/orthogonal images; and, display vector data.

C.7.0.5 Shall enable users to obtain measurements such as distance, height, elevation, and area directly from the 3D imagery, as well as insert GIS content and other data.

C.7.0.6 Shall include geographic data to support, at a minimum, the following:

C.7.0.6.1
System and boundaries registered to the street centerline in the geofile C.7.0.6.2 Boundary assignments (i.e. determining the response zone for each incident) completed in real time by processing the incident’s X/Y/Z coordinates against the boundary files to determine the incident’s location and response zone
C.7.0.6.3 Parcel-level GIS information, in which the approximate location of the front door of all the parcels in the state are stored in the geofile
C.7.0.6.4
Address validation and to determine an incident’s location #11..
- 234 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-29
C.7.0.6.5
Bulk data uploading
C.7.0.6.6
Weekly data updates
C.7.0.6.7
Metadata
C.7.0.6.8 FGDC standard format feed, like XML (extensible Markup Language) and KML (Keyhole Markup Language).

GIS/GEOFILE:

C.8.0 In order to support the geofile system, the CAD system:

C.8.0.1 Shall provide geo-fencing, and add the capability to establish law enforcement on-the-fly response zones, street networks, and other geographical layers using typical mapping/GIS tools.

C.8.0.2 Shall support valid MSAG names and multiple “aliases” for street names, intersections, commonplace names, landmarks, and street or highway route numbers. Name changes are nondestructive.

C.8.0.3 Shall stem geographically sensitive hazards, dispatch policies, and other system functions from validated locations.

C.8.0.4 Shall initiate a location verification step to add the coordinates of the incident location to the event and display an incident icon on the TMD as the CFS event is created.

C.8.0.5 Shall make a duplicate event check based upon the location and/or coordinates of the event, during the CFS event creation process.

C.8.0.6 Shall notify the event entry position via a prompt and show a list of the potential duplicate(s) if, during event creation, a potential duplicate event in the area is found.

C.8.0.7 Shall have a parameter (modifiable by the system administrator) specifying the distance in number of feet or other unit of measurement, from the location of the incident for duplicate checking.

C.8.0.8 Shall define location databases such as hazards, general premises information, street closures, and other user definable databases.

C.8.0.9 Shall perform a distance search to identify the existence of location information (e.g. hazards) during the event creation process.

C.8.0.10 Shall support different search distance criteria for different types of locations.

C.8.0.11 Shall support coordinate-based operations; Be capable of full integration with a GPS-based AVL system; and, Be capable of accepting named standards driven GPS reporting devices, such as GPSenabled smartphones and portable radios. #11..
- 235 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-30
C.8.0.12 Shall allow the system administrator to be able to modify parameters.

AVL:

C.9.0 In order to support AVL, the CAD system:

C.9.0.1 Shall seamlessly integrate with the CAD system and provide detailed, accurate, real-time vehicle tracking.

C.9.0.2 Shall include the AVL ID (represented as an alias) for each unit user’s status.

C.9.0.3 Shall include the indication that AVL is enabled for each unit on the user’s status window. AVL can also be used for reporting, messaging, response and alerting functionalities.

C.9.0.4 Shall include a visual indication if units displaying on the map and in the queues are AVL equipped.

C.9.0.4.1 The visual indication if units displaying on the map and in the queues are AVL equipped is customizable by the system administrator.

C.9.0.5 Shall be able to play back a unit’s AVL travel history and see the unit icon move from location to location on a map window.

C.9.0.6 Shall be capable of integrating with the existing GIS database.

C.9.0.7 Shall have other interactive functionalities also available, such as the ability to create and view unlimited groups of vehicles.

C.9.0.8 Shall provide for an automated alert function.

C.9.0.9 Shall provide for an automated alert for when vehicle is out of service.

C.9.0.10 Shall provide the ability to determine and modify all such alerts.

C.9.0.11 Shall provide the following information on any unit suffering loss of GPS signal (e.g. vehicle stopped, vehicle shut off, loss of network signal, loss of GPS data):

C.9.0.11.1 Last known position
C.9.0.11.2 Time of signal loss
#11..
- 236 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-31
C.9.0.11.3 Time lapse since signal loss
C.9.0.12 Shall provide minimal AVL reports that include:

C.9.0.12.1 Complete activity detail for specific date range C.9.0.12.2 Vehicle last stop/end time for date range
C.9.0.12.3 Exception reports including all events that triggered an alert C.9.0.12.4 Vehicle first start/begin time for date range C.9.0.12.5 Miles per day, stops per day, average and summaries per vehicle C.9.0.13 Shall pass unit status information to the AVL system whenever unit status is changed.

C.9.0.14 Shall pass any changes in unit location information to the AVL system if unit location changes are generated within the proposed system (as opposed to the AVL navigation system).

C.9.0.15 Shall display AVL updates on the map within two seconds of their receipt from the AVL controller.

C.9.0.16 Shall should be able to dispatch the nearest appropriate unit based on its AVL location using an appropriate routing engine to make that determination.

Map and GIS Analysis:

C.10.0 In order to support map and GIS analysis systems, the CAD system:

C.10.0.1 Shall support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of automatic pin maps.

C.10.0.2 Shall support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of spatial data aggregation.

C.10.0.3 Shall support either directly or, through an easily invoked (i.e. seamless) third-party mapping tool, the creation of trend analysis.

Other Interface Requirements:
#11..
- 237 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-32
C.11.0 Shall allow GPD direct access to the underlying system information stored in the database (ODBC, FTP, web services) for future interface configuration, as well as appropriate database and system documentation to support this access.

C.11.1 Shall provide a capability to flag a CAD call for service as a Suspicious Activity and submit that call data to the appropriate intelligence/counterterrorism unit (fusion center). This interface must conform to the standards set forth by the NSI and contained in the Functional Standard (FS) Suspicious Activity Reporting (SAR) Ver. 1.5.

C.11.2 Shall interface with alarm monitoring companies using ASAP. This interface must conform to standards contained in the APCO/CSAA ANS 2.101.1-2008: Alarm Monitoring Company to Public Safety Answering Point (PSAP) Computer-Aided Dispatch (CAD) External Alarm Interface Exchange.

C.11.3 In order to support an Emergency Operations Center Interface, the CAD system:

C.11.3.1 Shall have an EOC viewable setting that can be initiated through a web viewer or license to allow the EOC to view incidents and units specific to the emergency event.

C.11.3.2 Shall allow for incident creation that is within the area of the incident but be limited to certain incident types depending on the type of disaster.

C.11.3.3 Shall allow for the allocation of certain apparatus/units that can be managed and dispatched out of EOC for a specific CFS (planned or unplanned) without negatively impacting the CAD system. It is also preferred that in this instance, none of the all activities will be manual (i.e. the system will keep track of all apparatus and personnel for both the agency wide response and the EOC response area).

RMS Business Functions
D.1.0 Master Name Index: The RMS Master Name Index (MNI) creates an individual master name record for every individual who is involved in, or associated with, the following:

D.1.1 Incident reports
D.1.2 Arrest reports
D.1.3 Field interviews
D.1.4 Collision reports
D.1.5 Citations
D.1.6 Warrants
#11..
- 238 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-33
D.1.7 Registrants/Known Offenders
D.1.8 Gangs
D.1.9 Jail Booking
D.2 MNI Correlation: The master name record is linked to all events for any given individual, so that by querying that one name, the system will produce a synopsis of all the involvements associated with that one person.

D.3 MNI Linkage: The MNI also facilitates the linking of additional names to an individual master name record (i.e., alias information and relationship data). In querying an individual MNI record, the user will be able to view all related records, as well as those associated with that individual.

D.4 Duplicate Correction and Correlation: When a record or report is added to RMS and a person is linked (i.e., indexed) to that event, the system will search for duplicate identities within the MNI. The user will be presented with a list of possible matches to the name so that the user has the option to link the records. Once the list of possible matches is provided, the user has the option to decide whether the information will be linked to an existing master name record or whether a new master name entry will be added. The RMS provides a matching algorithm that will provide the ability to search the name file by the following criteria:

D.4.1 Sound-alike searching
D.4.2 Phonetic replacement
D.4.3 Diminutive first names (e.g., James/Jim/Jimmy, Elizabeth/Beth/Betty, and Jack/John) D.4.4 Other static demographic information, such as age, sex, and race.

D.5 Master Vehicle Index (MVI): The system must provide a centralized source of vehicle information.

D.6 MVI Source Data: The master vehicle index will be populated with information from several sources including from CAD workstations, mobile devices, and interfaces to CLETS and NCIC.

D.7 MVI Entry and Matching: When a vehicle is entered into the system, the system must search for a match in the MVI. If a match is found, the system must display to the user a list of events to which the vehicle is linked. The user must be able to select from the list of events to see the details of a specific event or to see a summary of all events that involve the vehicle. If no match is found in the MVI (i.e., if the vehicle is not already in the MVI), the system must add the vehicle's information to the MVI and link #11..
- 239 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-34
it to the appropriate event(s).

D.8 MVI Data Elements: The system must store the following information in the MVI for each vehicle:

D.8.1 Vehicle Identification Number (VIN)
D.8.2 License plate number
D.8.3 License plate state
D.8.4 License plate year
D.8.5 Registered owner
D.8.6 Description (e.g., make, model, year, color, style, and attributes) D.9 Master Property Index (MPI): The system must provide a centralized repository for property information.

D.10 MPI Master Category: Each piece of property entered into the system must be associated by a master category or type of evidence such as drugs, weapons, electronic goods.

D.11 MPI Data Elements: Each piece of property entered into the system must be identified by: make, model, brand, description, distinguishing characteristics, and serial number.

D.12 MPI NCIC Compliance: The system must use NCIC property codes to correctly identify each property item.

D.13 MPI Entry and Matching: When a new piece of property is entered into the system, the system must identify existing records in the MPI that have the same or similar characteristics and present the list of potential matches to the user.

D.14 Master Location Index: (MLI) The Master Location Index (MLI) provides a means to aggregate information throughout RMS based on the following:

D.14.1 A specific address
D.14.2 A range of addresses
D.14.3 An area (i.e., as defined in the geofile)
#11..
- 240 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-35
D.14.4 Locations based on x/y/z coordinates
D.14.5 Registered owner
D.15 Master Organization Index: Many events involve organizations (i.e., gang, business, school, or shopping center). Information about these groups entered into RMS is contained in a Master Organization Index (MOI).

D.16 MOI General Searchability: The MOI provides PD with a detailed, searchable store of information about organizations.

D.17 MOI Data Element Searchability: PD will be able to search on a variety of data elements and obtain a listing of all records associated with an organization.

D.18 MOI Linkage: MOI also provides the linking of aliases to organizations (e.g., M&M Associates, doing business as Joe’s Pawn Shop).

D.19 Reserved
D.20 Service Report Functionality: The following calls for service reports must be provided. Reports must be compliant with Crystal Reports Report Designer:

D.20.1 Daily log showing all calls received for the prior 24 hours from prior printing of the daily log (by user defined department)
D.20.2 Activity analysis by specified geographical area and time period D.20.3 CFS summary, by specified geographical area and time period D.20.4 Activity analysis by day of week
D.20.5 Activity analysis by hour of day
D.20.6 Activity analysis by day and hour
D.20.7 Response time analysis by specified geographical area and time period (e.g., receipt of call, dispatch time, on-scene time, and time call cleared)
D.20.8 Response time analysis by call type
D.20.9 Time consumed by call type by hour of day
#11..
- 241 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-36
D.20.10 Workload activity by resource assigned
D.20.11 Workload activity by group assigned
D.20.12 Time consumed by day of the week and hour of the day D.20.13 Time consumed by specified geographical area and by time period D.20.14 Calls that result in the creation of an incident report D.21 Incident Reporting: The following incident-report-related reports must be provided:

D.21.1 All summary UCR/NIBRS reports
D.21.2 Total incident reports based on period of time, area or beat, and incident type D.21.3 Location code (e.g., geocode)
D.21.4 Initial call type
D.21.5 Offense type
D.21.6 Summary of incidents by a responsible officer
D.22 Data Exchange and Compliance: The RMS provides automatic data exchanges with the following external resources:

D.22.1 User defined export of UCR/NIBRS data to the State of California via eCARS and the National Data Exchange (N-DEx)
D.22.2 User defined export of UCR/NIBRS data to the USDOJ D.22.3 The vendor’s product is compliant with GJXML standards, enabling information sharing with external justice partners
D.23 Prepare Initial Incident Report: The incident report contains factual information pertaining to the incident, including the following:
#11..
- 242 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-37
D.23.1 Offense information
D.23.2 Suspect information
D.23.3 Case status
D.23.4 Information pertaining to suspect
D.23.5 Witnesses
D.23.6 Victims
D.23.7 Reporting parties
D.24 Compatibility: Reporting requirements mandate that the vendor’s product be capable of providing data entry points for all UCR/NIBRS-required data elements.

D.25 Free Fields: Incident reports have free-text fields, which allow the collection of a virtually unlimited amount of narrative information.

D.26 Searchability: The system provides the capability to search the narratives for a specific word or phrase.

D.27 Electronic Submission: Once completed, officers may submit the incident report to their supervisor for review, electronically, via the RMS.

D.28 Create Supplemental Report: The system provides supplemental reports that are linked to the original, including certificate of release and probable cause declaration.

D.29 Report Review: The incident report must be able to be locked from further edits at a point determined by the PD (although this does not preclude the viewing of the document by those with access permissions, but the ability to block access will be a capability of the system).

D.30 Supervisory Review: Supervisors review incident reports and supplemental reports for accuracy and quality prior to their permanent, non-editable storage in the local RMS database and/ or their distribution to PD records bureau; to other agencies; and to local, state and federal criminal information repositories.

D.31 Electronic Supervisor Review: RMS must allow supervisors to receive, review, and approve incident reports online and to electronically respond to submitting officers and investigators regarding report quality and accuracy issues.

D.32 Records Review: PD’s Standard Operating Procedures (SOP) also require that the records division complete an accuracy review for compliance to reporting requirements prior to adding the information to #11..
- 243 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-38
the database.

D.32.1 RMS notifies records technicians when report numbers are missing or out of sequence.

D.33 Report Locking: The system supports all required reviews and corrections prior to locking down the incident report.

D.34 Field Reporting: Incident reporting functionality has been optimized for in-field report writing, but includes all data entry and validation available in the networked version of RMS.

D.35 Related Forms: Many incident report types require multiple associated manual forms. Any data that is repeated across the requisite manual report forms that collectively make up the report type shall be entered once in a logical data record and printed out in a logical sequence on a dynamically built GPD incident report.

D.36 The RMS must include a Property and Evidence module that captures and maintains all property types, including:

D.36.1 Safe-keeping
D.36.2 Stolen
D.36.3 Lost
D.36.4 Recovered
D.36.5 Found
D.36.6 Destroyed
D.36.7 Sold
D.36.8 Seized
D.36.9 Held as Evidence
D.36.10 Stolen and Recovered
D.36.11 Stolen and Released
#11..
- 244 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-39
D.37 The Property and Evidence module must be fully integrated with property information entered on initial offense, supplemental, arrest and other reports, as well as with other RMS and data entry modules that contain or track property information.

D.38 All property and evidence entered into the RMS must only be entered once and carried through to all other RMS modules that utilize the information (including the Property and Evidence module).

D.39 Property information entered within other RMS modules (e.g., Offense and Supplemental Reports, Arrest, Field Reporting, etc.) must flow seamlessly to appropriate fields within the Property and Evidence module without requiring the re-entry of any information.

D.40 The Property and Evidence module allows for the entry and submission of articles prior to report approval or closure.

D.41 The Property and Evidence module allows multiple personnel to enter articles concurrently from different workstations (both networked and mobile).

D.42 Property information entered within the Property and Evidence module must flow seamlessly to appropriate fields within other RMS modules (e.g., Offense and Supplemental Reports, Arrest reports, etc.) without requiring the re-entry of any information.

D.43 The Property and Evidence module must automatically check the RMS's databases and interfaced databases (e.g., CLETS, NCIC) for entered property items and alert RMS users if the items have previously been reported stolen or missing.

D.44 Entry of information related to searchable (serial number, owner applied number, etc.) property that is recovered, found, or submitted as evidence must initiate an automatic query to the CLETS/NCIC stolen property databases and alert users of any hits.

D.45 The system provides data entry screens to allow users to enter information on property and evidence that has been received. The system must capture the following information for chain of evidence purposes: original Officer, receiving booking Officer, names of any persons who check in/out the article(s) for any reason; When a piece of evidence is entered into the system, the system must search the MPI to identify potential matches and must present the list of potential matches to the user. The system must search the following external databases to identify potential matches: CLETS/NCIC, RMS, National Data Exchange (N-DEx).

D.46 The system must provide data entry screens that allow the user to enter vehicle information for vessels, cars, motorcycles, For each vehicle, the system must capture the identifying information appropriate for the vehicle type (e.g., vessels, cars, motorcycles), the reason for impound, the impound location, and link the vehicle information to the appropriate event.

D.47 The RMS includes safeguards to ensure that procedures and laws governing the release, sale, or destruction of property are followed.

D.48 The system will use automated messaging for specific property/evidence-related events that require notification (for release, destruction, adjudication).
#11..
- 245 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-40
D.49 The system provides a means to store digital images of the item prior to the disposition.

D.50 The system will generate automatic alerts to pre-defined email addresses when property is eligible for release or sale.

D.51 The Property and Evidence module must store, display, and enable the editing of information pertaining to property and evidence items including, at a minimum: date, time, location of the property event; officer(s) involved; description of the property; the quantity and value (estimated or known) of the property; serial numbers and other identification information (including owner-applied numbers); associated case numbers and case offense/crime type; item number; owner's name and contact information; release to owner date; property type and category or article codes; number of days held; destruction/disposal date; brand names; manufacturer; models; and colors.

D.51.1 GPD is able to define certain data entry fields as “mandatory" (to prevent booking officers from submitting incomplete items).

D.52 The Property and Evidence module must support the capture, storage, and display of a (practically) unlimited number of photographs/images of property items.

D.53 At a minimum, the Property and Evidence module must be able to track and provide data entry fields for all of the property and evidence data elements tracked by NCIC, UCR, and NIBRS.

D.54 The Property and Evidence module must support the association of a single property item to multiple cases and reports.

D.55 The data fields within the Property and Evidence module must initially use NCIC, NIBRS, and UCR codes for validation of non-text property data entered into the RMS.

D.56 Trained and authorized RMS Administrators must be able to modify the validation codes used to validate property items entered into the Property and Evidence module without requiring any assistance from the RMS vendor.

D.57 Trained and authorized RMS Administrators must be able to modify the NCIC, NIBRS, and UCR code tables as needed to add specific property types and link them to the correct NCIC, NIBRS, and UCR code.

D.58 The Property and Evidence module must store, display, and enable the editing of at least the following information pertaining to property items checked into the property room: department, property room name and ID, property's storage location (i.e., room, wall, shelf, package number, item number, and bin ID), barcode label ID, free format (narrative) description, any identifying numbers, next action to be taken, date to be taken, current status, last transaction date, last transaction type, and the full name and ID of the person performing the last transaction.

D.59 The Property and Evidence module must be able to use bar coding technologies to identify and track property and evidence items maintained in the RMS. Vendor must provide a list of bar coding hardware that are compatible with their software.
#11..
- 246 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-41
D.60 The system prints bar coding labels using label sheets.

D.61 The Property and Evidence module must be able to use RFID technologies to identify and track property and evidence items maintained in the RMS. Vendor must provide a list of RFID hardware that are compatible with their software.

D.62 The Property and Evidence module must support portable bar code readers that enable wireless remote capture, identification, and storage of bar code information where property and evidence is stored.

D.63 The Property and Evidence module must support the scanning of a storage location in order to automatically enter the property item's location.

D.64 Authorized RMS users (e.g., officers) completing initial offense, supplemental, arrest and other RMS reports that contain property must be able to print property tags/barcodes directly from their reports and affix the tags to the entered property items prior to their storage in a property room.

D.65 Authorized RMS users (e.g., property room custodians and clerks) checking property items into a property room must be able to print and affix property tags/barcodes to the checked-in property items prior to their storage in the property room.

D.66 The Property and Evidence module must automatically fill in previously entered information that is known to the RMS, but allow authorized RMS users to update any previously entered information. For example, it must not be necessary to indicate the person completing the last transaction if the RMS already knows the name and ID of the person completing the transaction.

D.67 The property room name and ID where property items are stored must default to the location of the workstations completing the transaction (if booking in the field, end-users may set the default).

D.68 Authorized RMS users must be able to query the Property and Evidence module database by case number, bar code ID, item ID, invoice number, current disposition, next action type, next action date, partial and full serial number, partial and full owner applied number, all master indices, officer involved, property description, date and time range, and various combinations of all of these search criteria.

D.69 Authorized RMS users must be able to determine the property room status and location of property items associated with a case directly from the various reports comprising the case.

D.70 Authorized RMS users must be able to determine the property room status and location of property items associated with a case directly from query results listing reports and cases that have property that was entered into a Property and Evidence module database.

D.71 The Property and Evidence module must be able to alert appropriate RMS users and groups of users prior to the time that the statute of limitations is exceeded for disposal of the property.

D.72 The Property and Evidence module must support automatic disposition notification of certain property by notifying specific RMS users or groups of users when property is eligible for disposition based upon the type of item, the type of associated case and the statute of limitations associated with the #11..
- 247 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-42
charges in the case, and elapsed time since the case was adjudicated.

D.73 The Property and Evidence module must be able to create lists of property to be sold at auction or otherwise disposed. The data collected in this module must include what auction vendor took the item, who bought the item at auction, the price they paid, and all associated item dispositions.

D.74 Provides the ability to process items for disposal or auction in bulk with a single disposition that will apply to all impacted articles (i.e., all eligible narcotics can be processed for destruction at once).

D.75 The Property and Evidence module must support the entry of case disposition, which then triggers property status/disposition changes for property associated with the case. The module must send a notification for approval to release when the case disposition allows, unless the property is linked to another case.

D.76 The Property and Evidence module must be able to automatically generate letters to property owners to pick up their stored property and automatically record/store the date that the letter was sent.

Letters must be 100% configurable by the agency without vendor assistance.

D.77 The Property and Evidence module must automatically change the status of property whose owners have been notified, but have not picked up their property within a specified time interval.

D.78 The Property and Evidence module generates property notification letters for ready-to-release items.

D.79 Trained and authorized RMS Administrators must be able to set up and maintain, without requiring any assistance from the RMS vendor, the elapsed time from owner notification that their property is available for pickup and the change in status of the affected property items if the owner does not pick up the property within the specified time.

D.80 Prior to the disposition of a property item stored within a Property and Evidence module database, the RMS must automatically check to ensure there are no holds or other cases pending where this property is required. The module must send notifications for approval for release.

D.81 The Property and Evidence module must be able to generate receipts for property that is going to be disposed, transported to a different facility, and other appropriate Property and Evidence module transactions.

D.82 The Property and Evidence module must be able to capture electronic signatures from individuals picking up property for various reasons including disposal, claimed by owner, and transfer to a different facility.

D.83 The Property and Evidence module must provide tools to expedite completing property room and storage facility inventories.

D.84 Authorized RMS users must be able to display and print property room inventory lists that identify all items stored in the entire or a user specified subarea of a property room along with user specified information about each items contained in the specified area. #11..
- 248 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-43
D.84.1 Whenever an article is scanned/recorded, the system depicts all prior scans and locations, along with associated article(s).

D.85 RMS automatically updates historic location information when rooms, bins, or shelf numbers are changed since the original scan (i.e., Article 123 was originally scanned and placed on shelf 7Y in 2006, but shelf 7Y was renamed D01 in 2017 – when users view the scan audit, the system will depict the original scan location as D01 not 7Y).

D.86 The Property and Evidence module must maintain "chain-of-custody" information for all property and evidence stored in the RMS as property moves between the property room and various other locations such as labs, prosecutor's office, courts, etc. When an article is moved, the system captures the date, time, ID of the person who moved it, and the purpose of the movement.

D.86.1 The system must provide a complete audit trail for all item movements, generated ondemand or automatically at user-defined intervals.

D.87 The system automatically generates random article numbers (on-demand or automatically at userdefined intervals) within a user-defined property/evidence article type (i.e., guns) for the purpose of conducting randomized and routine audits.

D.88 The Property and Evidence module must provide the capability to "split" quantity-based items (fluids, powders, etc.) and then to track the split portions of the original quantity recorded.

D.89 The Property and Evidence module must be relationally cross-referenced to the MNI, MLI, MPI, and MVI master indexes and to the Offense and Supplemental Reports, Arrest, and other appropriate RMS modules.

D.89.1 The RMS displays all property and/or evidence articles associated with an MNI.

D.90 The Property and Evidence module must contain reporting capability that includes staff productivity, storage capacity/space availability, inventory and a monthly/quarterly property conversion report.

D.91 The Property and Evidence module must send alerts to officers of any case related vehicle impound still active after 72 hours without a scientific analysis request or hold.

D.92 The Property and Evidence module must contain fields to record lab results, ballistic results and subpoena tracking information.

D.93 The Property and Evidence module must allow the ability for officers/detectives to notify the property technician that they are in route to property and evidence to pick up items and what items they need.

D.94.2 The following Property and Evidence management reports must be provided:

D.94.3 Chain of custody
#11..
- 249 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-44
D.94.4 Property summary report
D.94.5 Property item detail
D.94.6 Released property report
D.94.7 Property inventory report
D.94.8 Property disposition reports
D.94.9 Form letter to inform the property owner of the pending disposition of property with instructions for filing a claim
D.94.10 Vehicle impound forfeiture report
D.94.11 Evidence location summary report
D.94.12 Audit report
D.94.13 Safekeeping report
D.94.14 Safekeeping Release Report
D.94.15 Evidence Out to Court
D.94.16 Evidence Out to Lab
D.94.17 Requests for Evidence to be Sent to Lab (with fulfilled and unfulfilled requests displayed) D.94.18 Evidence Out to Investigator
D.94.19 Evidence Out to Others (user-defined)
D.95 Bar Code Technology: The system interfaces with bar code scanners to read/input bar codes that uniquely identify a piece of property/evidence (note that the Department uses ten separate property/evidence entry points in four zones; all of which require bar code technology). #11..
- 250 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-45
D.96 Bar Code Printing: The system prints bar coding labels using label sheets.

D.97 Collect Property and Evidence: The module must capture the following property and evidence elements:

D.97.1 Case Number (DR)
D.97.2 Officer Booking
D.97.3 Receiving Booking Officer
D.97.4 Property Status (Evidence, Stolen/Theft, Recovered, Lost, Found, Damaged etc.) D.97.5 Property Category
D.97.6 Property Description
D.97.7 Article
D.97.8 Brand
D.97.9 Model
D.97.10 Color (Allow for two tone)
D.97.11 Size
D.97.12 Caliber
D.97.13 Drug Weight
D.97.14 Drug Test Type
D.97.15 Drug Test Results (Y/N)
#11..
- 251 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-46
D.97.16 Quantity (Formatted)
D.97.17 Quantity Type/Units
D.97.18 Owner Applied Number (OAN)
D.97.19 Serial Number
D.97.19.1 Obliterated (As it relates to Serial Number)
D.97.20 Value (Formatted)
D.97.21 Search Warrant Number
D.97.22 Related to Previous Booked Evidence (Y/N)
D.97.23 Date Original Evidence Taken into Custody
D.97.24 If Firearm, Automated Checks: AFS (Y/N), NCIC (Y/N) D.97.25 Special Marks (Text)
D.97.26 Condition
D.97.27 Reporting District
D.97.28 Probable Crime (Offense Class)
D.97.29 Offense Type (Library: Felony, Misdemeanor, Infraction) D.97.30 Investigative Unit
D.97.31 Property Booked at Location
#11..
- 252 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-47
D.97.32 Notifications (Person ID and Division)
D.97.33 Associated Reports (Report Type and DR Number)
D.97.34 Description Narrative of Property (Text)
D.97.35 Preliminary Drug Test -Supervising Officer ID, Witnessing Officer ID D.97.36 Search Warrant Date
D.97.37 Search Warrant Issued by Judge
D.97.38 Court Number
D.97.39 Items Seized Pursuant to Warrant
D.97.40 Vehicle (Master Vehicle Searched)
D.97.41 Attempt to Locate Owner
D.97.42 Total # of Latent Prints Lifted?
D.97.43 Total # of Latent Prints Photographed?
D.97.44 Total # of Latent Prints AFIS Quality for Palms? D.97.45 Total # of Latent Prints AFIS Quality for Fingers? D.97.46 AFIS Evaluated by Serial Number
D.97.47 AFIS Evaluated by Date
D.97.48 Sent to Lab (Y/N)
#11..
- 253 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-48
D.97.49 Stolen Value
D.97.50 Date Reported Stolen
D.97.51 Link Owner Last Name (Link from Names entered for Incident) D.97.52 Owner First Name
D.97.53 Owner Middle Name
D.97.54 Recovered Value
D.97.55 Date Recovered
D.97.56 Recovery Type
D.97.57 Estimated Damaged Arson/Vandalism
D.97.58 Other Jurisdiction
D.97.59 Recoveries from Other Agencies - Case Number
D.97.60 Recoveries from Other Agencies - Recovered Value D.97.61 Recoveries from Other Agencies - Recovered Date D.97.62 Tracking Number
D.97.63 Status
D.97.64 Disposition of Property
D.97.65 Location Property Stored as Evidence
#11..
- 254 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-49
D.97.66 Hold For Type
D.97.67 Hold For Period Date
D.97.68 Supervisor Approval ID (Personnel)
D.97.69 Other GPD Report Forms (check off) Issued (Y/N) D.97.70 Narrative/Comments (Text)
D.98 Validation Upon Entry: When an article is entered, the system must search the MPI and CLETS to identify potential matches and present the list of potential matches to the user for import (to eliminate redundant data entry).

D.99 Like Articles: For like-articles (i.e. multiple pieces of the same property category), the system shall allow the user to enter an unlimited number of property records and as each new like article is entered, the user may choose to duplicate the entered record and then update the data elements that may be unique.

D.100 Vehicle Impound: The system must provide data entry screens that allow the user to enter vehicle information for vessels, cars, motorcycles which mirror state-mandated forms (including, but not limited to, CHP 180 and 555). For each vehicle, the system must capture the identifying information appropriate for the vehicle type (e.g., vessels, cars, motorcycles), the reason for impound, the impound location, and link the vehicle information to the appropriate event.

D.101 Property and Evidence Storage: The system must provide a check-in/check-out log to allow property movement to be tracked. The check-in/check-out log must integrate with the bar-code scanners to quickly identify a specific piece of equipment/property.

D.102 Property and Evidence Disposition: The RMS includes safeguards to ensure that procedures and laws governing the release, sale, or destruction of property are followed.

D.103 Disposition Event Messaging: The system will use automated messaging for specific property/evidence-related events that require notification (for release, destruction, adjudication).

D.104 Property Imaging: The system provides a means to store digital images of the item prior to the disposition.

D.105 Property Disposition Alerts: The system will generate automatic alerts to pre-defined email addresses when property is eligible for release or sale.

D.106 Arrest Reports: The following arrest reports must be provided:
#11..
- 255 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-50
D.106.1 Daily arrests, by day and time, date range and geographic areas D.106.2 Arrest report and/or affidavit
D.106.3 Arrests by location and time period
D.106.4 Arrest log by time, and geographic area
D.107 DUI Arrest: All relevant information regarding the results from the PD field sobriety tests (See Forms Appendix for the form) and subsequent alcohol blood content are gathered and recorded to supplement the report in RMS.

D.108 Booking Forms: The following booking forms and reports must be provided:

D.108.1 Booking form which contains all required PD fields (See Forms Appendix for the form) D.108.2 Booking summary, based on varying search criteria D.108.3 Property received receipt
D.108.4 Property released receipt
D.108.5 Booking activity (e.g., intakes, releases, and transfers) by time period and location D.109 Juvenile Reporting: The following juvenile related reports must be provided:

D.109.1 Juvenile custody
D.109.2 Juvenile contact report
D.109.3 Name listing for juveniles separate from adults, based on varying search criteria D.110 Juvenile Contact: RMS provides data fields for juvenile contacts, including: the youth’s full name, age, address, contact (i.e., family) information, physical description, gender, and name of school he or she attends, as well as information about the incident/contact.

D.111 Juvenile Contact Archiving: RMS includes the capability to automatically archive juvenile contacts after a requisite period of time (as governed by state law) has passed since the entry or when the #11..
- 256 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-51
subject turns 18 years of age (whichever occurs first). The RMS keeps juvenile information separate, physically, from adult data.

D.112 Juvenile Contact Segregation: The RMS keeps juvenile information separate, physically, from adult data.

D.113 Traffic and Vessel Reporting: The following traffic and vessel related reports must be provided:

D.113.1 California CHP Standard Traffic Accident Report Forms D.113.2 California CHP Standard Vehicle Impound Forms
D.113.3 Accidents by location
D.113.4 Accidents by time of day and day of week
D.113.5 Accidents by violation
D.113.6 Accidents by severity
D.113.7 Accidents by driver demographic
D.113.8 Statistical summary by intersection
D.113.9 Statistics by area (e.g., beat, precinct), day, and time D.114 Collision Reporting: The system must provide drawing or diagramming tools to allow the RMS users to diagram accident report data. The system must allow the user attach accident diagrams and photographs to a specific event and report. The system must provide a data entry screen to allow the user to enter traffic accident data including weather, visibility, and road surface conditions at the time of the accident; and location information.

D.115 Citation Reporting: The following citation-related reports must be provided:

D.115.1 Citation and warnings summary based on varying search criteria D.115.2 Citation by location
#11..
- 257 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-52
D.115.3 Citations and warnings by demographic data
D.115.4 Citation audit (e.g., missing/voided numbers)
D.116 Issue Citation: Citation information is stored and tracked in RMS. Officers will enter information about a violation or charge, as well as relevant court information, into automated citation issuance devices (TurboData for parking citations, and Brazos for all others), which will be uploaded into RMS.

The citation information should be capable of being sent, electronically, to the appropriate court. The officer issuing the citation needs to query state and local databases that contain information regarding previously issued citations and warnings. The query also checks for any outstanding warrants or alerts.

RMS must track warnings, as well as citations. Both must be linked to the subject’s master name record.

D.116.1 Barcode Citation Book Inventory: System allows records to scan-out a citation book to a particular officer and then be able to view in RMS who was assigned that book and which citation numbers are missing from within it.

D.117 Field Interview Reports: The following Field Interview-related reports must be provided:

D.117.1 PD Field Interview Form (for both RMS and MDS)
D.117.2 Field Interview summary, based on varying search criteria D.118 Document Field Interview: The system must provide a data entry screen to allow the user to document a Field Interview. The system will provide Field Interview templates to capture pertinent information for the following types of contacts:

D.118.1 A parked car in an area and at a time normally vacant of cars D.118.2 One or more people in an area and at a time normally vacant of people D.118.3 One or more people loitering in a vulnerable area D.118.4 People and vehicles that appear to be out of place for any particular reason D.119 Field Interview Targeting: Specific areas may be targeted for Field Interview based on departmental policy. Such targeting may be for high-crime areas or in potentially sensitive areas. The information collected includes:

D.119.1 Location and time
#11..
- 258 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-53
D.119.2 General circumstances
D.119.3 Names and descriptions of persons
D.119.4 Identifying information on vehicles or other property D.120 Protection Orders and Restraints: The following protection orders and restraints related reports and forms must be provided:

D.120.1 Expired/soon-to-expire orders
D.120.2 Active orders
D.120.3 Orders that have been served
D.120.4 Orders received, by source
D.120.5 Cancelled orders
D.120.6 No trespass order
D.121 Protection Order and Restraint Recording: The system must provide an alerts feature to remind the user of specific activities to be performed. The alerts may be based on a selected date/time or a type of event or system action. The system must allow the user to create, modify and remove alerts for a specific individual. They system must support expiration dates for projection orders and restraints.

D.122 Crime Analysis: RMS has a variety of reporting functions attached to their Analytical Support modules and allows presentation of information in a variety of formats, such as bar graphs, pie charts, and line graphs. Reports must be compliant with Crystal Reports Report Designer.

D.123 Crime Analysis Features: RMS supports the ability to aggregate data on the various indicators, such as:

D.123.1 Current period vs. previous period
D.123.2 Current period vs. historical average
D.124 Percentage of Total Crime Reports: Percentage of total crimes for period by:
#11..
- 259 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-54
D.124.1 Reporting departments
D.124.2 Areas/beats/zones
D.124.3 Teams/shifts
D.124.4 Percentage change from prior periods (i.e., trend) D.125 Crime Distribution: RMS contains the ability to conduct crime distribution analysis based on a number of criteria, including:

D.125.1 By area/beat or reporting department (i.e., ZIP codes) D.125.2 By time, date, and day of week
D.125.3 Frequency of occurrence
D.125.4 Citation
D.125.5 Crime/incident report number
D.125.6 Field interview data
D.125.7 Search warrant data
D.125.8 Vehicle information
D.125.9 Type of offense (e.g., residential, auto, or business) D.126 Additional Crime Analysis Reports: The Crime Analysis module provides the following reports:

D.126.1 General offense activity
D.126.2 Offense activity by day of week
#11..
- 260 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-55
D.126.3 Offense activity by beat
D.127 Crime Analysis Searchability: Every field of operational data in RMS (i.e., data entered by the user in any form, not configuration or system control data) will be searchable, including narrative (e.g., text or memo) fields. This is accomplished by using query interfaces that are part of the application or, at a minimum, using third-party tools that can access the operational database via Open Data Base Connectivity (ODBC)
D.128 Crime Analysis Alerting: RMS includes an alert function related to analytical support to provide for the immediate transmission of information to law enforcement officers in the field.

D.129 Crime Analysis Data Elements Provide Time-Related Metrics: The Crime Analysis module contains complete data elements that relate to time (such as the day, time of day, week, date, month, and year).

D.130 Geovalidated Data: RMS includes a locally determined and previously validated geographic reference.

D.131 Correlation: RMS supports crime/suspect correlations to show a relationship between a suspect and an offense. The correlations may be made by using any number of selected criteria in which unique and distinguishing characteristics, physical identifiers, modus operandi, and various other common traits of offenders are known. These identifiers are captured as a part of multiple different business functions, including incident, field interview, arrest, accident, citation, MNI, MVI, MLI, and MOI.

D.132 Standard RMS Reporting: Law enforcement personnel must be able to generate standardized reports and aggregate reports, as well as query RMS to produce ad hoc reports from the RMS reports module. Examples of standardized reports from RMS business functions are:

D.132.1 Incident reports
D.132.2 Accident/collision reports
D.132.3 Property/evidence reports
D.132.4 Citation reports
D.132.5 Field interview reports
D.132.6 Uniform Crime Reports (UCR)
D.132.7 National Incident-Based Reporting System (NIBRS) #11..
- 261 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-56
D.133 Case management reports
D.134 Billing reports
D.135 Summary reports for warrants, citations, CFS, accidents, and employees D.136 DUI Billing from Traffic
D.137 Alarm Billing
D.138 Jail Booking Fees, Recovery, and Bonds (via treasurer) D.139 Aggregate Reporting: Aggregate, agency-wide reporting allows law enforcement personnel to associate information in a variety of ways and among a number of different tables or fields, including CFS, warrants, incident reports, traffic data, property data, and weapons data. Managers must be able to query, retrieve, and display information in a variety of ways. They must be able to query on indicators, such as date of the incident, case type, and assigned officer. They will be able to produce reports from a list of standardized reports or on an ad hoc basis. The query and data retrieval system must be integrated with the RMS security system so that the PD has the option to designate search and query types and depths by password or groups of passwords.

D.140 Standardized Reporting: Each module includes its own set of standardized reports, which also are available through the RMS Incident Reporting module.

D.141 Ad Hoc Reporting: PD may need operational reports and analysis that are not provided by standard RMS reports and queries. Ad hoc reporting will allow PD to define and create these additional custom reports. Once created, these custom reports have the option to be saved and run as standard reports. RMS provides a tool that has the option to be used to produce any number of ad hoc reports.

D.142 Permits Management: Provides the ability to apply, review, approve, and manage permits for alarm companies, tow companies, pawn shops, second hand dealers, and other agency-defined registrations.

D.143 Contact Metrics: RMS includes a module that allows in-field capture of contract metrics (on handheld devices and in-vehicle mounted mobile devices) in compliance with the State of California's Racial and Identity Profiling Act (RIPA) of 2015. The functionality is similar to a Field Interview card, but also captures the following demographic and profiling data:

D.143.1 CAD Event/Incident Number
#11..
- 262 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-57
D.143.2 Contact Date
D.143.3 Contact Time
D.143.4 Age
D.143.5 Sex
D.143.6 Stop Category (Dispatch or Self-Initiated)
D.143.7 Reason
D.143.8 Race
D.143.9 Hispanic and Non-Hispanic
D.143.10 Ethnicity
D.143.11 Sex
D.143.12 Address and District
D.143.13 Type of Search
D.143.14 Category
D.143.15 Contact Type
D.143.16 Result of Contact
D.143.17 Officer Assignment (Patrol, Plainclothes, Motor) D.143.18 Officer Vehicle Number
#11..
- 263 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-58
D.143.19 Officers at Scene
D.143.20 Officer Conducting Stop
D.144 Investigative Case Management: The proposed RMS provides the following case-management features and functions:

D.144.1 Provides the capability for effective investigative case management, control, monitoring, reporting, and automatic case assignment based on agency-defined parameters.

D.144.2 RMS System Administrators must be able to define Investigative Case Management module parameters (e.g., case assignment, case management, monitoring, and control) without requiring any assistance from the RMS vendor.

D.144.3 Authorized RMS users must be able to enter case activity and other case related information via a combination of validated fields and free format text fields (e.g., narrative fields) that are contained in predefined Investigative Case Management module supplemental report forms and data entry screens.

D.144.4 The Investigative Case Management module must support an investigative supplemental report approval process.

D.144.5 The Investigative Case Management module must link investigative case activity to initial offense and supplemental reports.

D.144.6 Investigative Case Management cases must be composed of the initial offense and any associated supplemental reports, property and evidence records, arrest reports, witness statements, and other various associated files and data.

D.144.7 The individual records and data that comprise a case must be easily identifiable from the case number and the case number must be easily identifiable from the individual records, reports, and data comprising the case.

D.144.8 The Investigative Case Management module must incorporate the use of weighted solvability factors.

D.144.9 RMS System Administrators must be able to set up and maintain case solvability logic that computes the solvability of a case based on information contained within the case (e.g., availability of witness information, method of operation, location, elapsed time, and other factors) without requiring any assistance from the RMS vendor.

D.144.10 The Investigative Case Management module must support automatic report routing of completed and/or approved reports based upon the information contained in the report (e.g., offense type, gang related, report priority, solvability factors, etc.).

D.144.11 RMS System Administrators must be able to set up and maintain report and case routing parameters that cause the RMS to automatically route completed and approved reports to designated users, groups of users, and/or supervisory role positions of organizational units defined within the RMS #11..
- 264 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-59
without requiring any assistance from the RMS vendor.

D.144.12 The RMS must notify recipients (designated users, user groups, and/or supervisory role positions defined within the RMS) of automatically routed reports that a new or rerouted/reassigned report has been routed to them.

D.144.13 Authorized RMS users must be able to change the offense type of a report thereby causing the report to be re-routed to an appropriate set of users, user groups, and/or supervisory roles.

D.144.14 RMS System Administrators must be able to set up report routing parameters that cause a single, completed/approved report to be routed to multiple destinations (multiple users, user Groups, and/or supervisory roles) based on information contained within the report and its location without requiring any assistance from the RMS vendor.

D.144.15 Authorized RMS users must be able to change the organizational unit responsible for investigating a report and case.

D.144.16 The RMS must notify the organizational unit responsible for investigating a report and case if the responsible organizational unit for the report and case is changed.

D.144.17 The original organizational unit responsible for investigating a report/case must approve any changes in the responsible organizational unit for that report/case.

D.144.18 The Investigative Case Management module must provide an interactive means of assigning reports and cases to investigators, monitoring investigative case progress, and initiating case dispositions.

D.144.19 The Investigative Case Management module must be able to track a case from its assignment to an investigator through final disposition.

D.144.20 The Investigative Case Management module must track the detail/division, individual, and the date and time that a case was reviewed.

D.144.21 The Investigative Case Management module must allow investigative supervisors to view detailed case information and other case related activities of their subordinates.

D.144.22 The Investigative Case Management module must provide the ability for investigators to enter case dispositions and statuses (e.g., clear a case by arrest, etc.) in an interactive format. The module must require that changes of disposition or statuses be approved by a supervisor.

D.144.23 The case dispositions and statuses assigned within the Investigative Case Management module must be stored in different data fields than the dispositions and statuses used for UCR/NIBRS.

D.144.24 Authorized RMS users must be able to select a number of reports and cases and to update all of the selected reports and cases in one action (e.g., assign multiple cases to a single investigator, update the status of multiple cases with a single command, etc.).

D.144.25 The display of reports and cases to be monitored and assigned by the Investigative Case Management module must be controlled by the organizational unit. The default display of reports and cases to be assigned by a specific user or investigative supervisor must only include the cases within that #11..
- 265 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-60
user's organizational unit.

D.144.26 The Investigative Case Management module must provide a caseload weighting algorithm to assist supervisory personnel equalize the caseloads carried by their investigators.

D.144.27 The Investigative Case Management module's caseload weighting algorithm must default to only analyze the caseloads of investigators within that supervisor's organizational unit.

D.144.28 Authorized RMS users must be able to direct the Investigative Case Management module's caseload weighting algorithm to analyze the caseloads of investigators across the entire agency and/or a set of organizational units within the agency.

D.144.29 The Investigative Case Management module must provide for an online investigative case journal.

D.144.30 The Investigative Case Management module must notify appropriate supervisory personnel if a case has exceeded the assigned time interval for a status update or change in status for the particular case type and agency.

D.144.31 RMS System Administrators must be able to assign and maintain report and case status time interval parameters, without requiring any assistance from the RMS vendor, that are unique to one or more agencies, organizational units, and report/case types (e.g., homicide, auto theft, burglary, etc.) that when exceeded must cause a notification to be sent to a designated set of users, user groups, and/or supervisory role positions defined within the RMS.

D.144.32 The Investigative Case Management module must notify investigative personnel of other RMS activities and transactions affecting their assigned reports and cases including, at a minimum, lack of service activity on a warrant, and change in status of property items.

D.144.33 The Investigative Case Management module must be fully integrated with the Offense and Supplemental Reports module and provide access to all initial offense and supplemental reports in a case, as well as involved individuals such as suspects, victims, witnesses, etc.

D.144.34 The Investigative Case Management module must provide access to the charges, narrative, property, vehicles, and all other information available in the initial offense and supplemental reports of a case.

D.144.35 The Investigative Case Management module must include a case summary function or database that provides a quick way to determine the latest status of the elements of a case without having to sort through the various reports of the case. If the initial report described the color of an involved vehicle as red and after further investigation the vehicle color was updated (via a supplemental report) to be blue, the case summary function must identify the vehicle's color as blue. The initial offense report would still identify the vehicle's color as red. However, the supplemental report would indicate when it was changed to blue and why. The status of involved persons would also change as dictated by the various reports constituting the case (e.g., an initial witness may, after further investigation, be found to be a suspect and eventually arrested). The case summary function would always display the most current #11..
- 266 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-61
status of involved persons.

D.144.36 Authorized RMS users must be able to query the Investigative Case Management module by, but not limited to the following criteria: date and time range, assigned investigator, case type (e.g., homicide, assault, robbery, etc.), investigative division/detail (e.g., auto theft), case status, geographic area, and various combinations of all of these selection criteria.

D.144.37 Investigative Case Management module query responses must display a list of reports and cases that meet the selection criteria.

D.144.38 Authorized RMS users must be able to obtain additional report and case details by selecting one or more of the reports and cases listed in response to a Investigative Case Management module query.

D.144.39 The Investigative Case Management module must support queries to, and response displays from NCIC, as well as other RMS databases directly from the various forms, report and queries available within this module.

D.144.40 The Investigative Case Management module must provide reports on unassigned cases by agency, department, division/detail, and/or organizational unit listing relevant information about each case including, at a minimum, the case number; organizational unit responsible for investigating the report/case; initial offense report author; offense type, location, containing boundaries (e.g., grid, precinct, neighborhood, etc.), date and time of incident resulting in the report; solvability factor associated with the report/case; date and time that the report/case was routed for assignment; and elapsed time since the report entered the unassigned report queue for the organizational unit.

D.144.41 The Investigative Case Management module must provide reports on case status summary (case closing analysis) by division/detail, and/or organizational unit.

D.144.42 The Investigative Case Management module must provide reports on case aging by department, division/detail, and/or organizational unit.

D.144.43 The Investigative Case Management module must provide reports on assigned cases (investigator workload) by department, division/detail, and/or organizational unit.

D.144.44 The Investigative Case Management module must provide reports on agency, department, division/detail, and/or organizational unit case counts.

D.144.45 The Investigative Case Management module must provide reports on case activity summary (electronic logbook) by agency, department, division/detail, and/or organizational unit.

D.144.46 The Investigative Case Management module must provide follow-up due reports by agency, department, division/detail, and/or organizational unit.

D.144.47 The Investigative Case Management module must support statistical analysis and management reports regarding individual detective and division/detail productivity, by combining case activity and case journal entries between a user-specified date and time range, as well as by user-specified agency, department, division/detail, and/or organizational unit. #11..
- 267 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-62
D.144.48 Case activity journals within the Investigative Case Management module must include predefined categories of investigative actions that must be maintainable by RMS System Administrators without requiring any assistance from the RMS vendor.

D.144.49 The Investigative Case Management module reports must include appropriate charts to display actual time and percentage calculations of investigators' activities based upon various investigative categories.

D.144.50 The Investigative Case Management module must be able to store a (practically) unlimited number of various printed documents and pictures (including videos) such as offender and witness statements, lab reports, evidentiary documents, etc., and the attachment of those documents, videos and files to case records.

D.144.51 The Investigative Case Management module must allow the use of digital media for the recording of crime scenes or other photographic, video or audio evidence and the attachment (linkage) of a practically unlimited number of evidentiary images to individual reports within cases.

D.144.52 Access to reports and associated data, diagrams, and images within the Investigative Case Management module must be controlled according to the security requirements specified in this RFP.

D.144.53 The Investigative Case Management module must be relationally cross-referenced to the Offense and Supplemental Reports, Report Approval, and other appropriate RMS modules, as well as the master indexes.

D.144.54 Authorized RMS users must be able to use the Investigative Case Management module to create tip sheets and/or crime intelligence bulletins.

D.144.55 Authorized RMS users must be able to package a complete case file with the press of a button.

This function must allow incident and supplement reports, property, videos, and all linked RMS data to be printed to a PDF. This file along with all attachments must then be saved to the users destination of choice.

D.144.56 The Investigative Case Management module must allow users to link all related cases together.

D.144.57 The ability (particularly for case agents) to set reminders regarding items such as follow-up tasks, expiration dates, and required activities.

D.144.58 Case management notes appear in chronological order.

D.144.59 New cases appear as pop-ups to alert supervisor when new cases and case notes are filed.

D.144.60 Application provides a tickler-file for lab requests (to be filed/updated/cleared/held).

D.145 Warrants Module: The proposed RMS must include a Warrants module that includes the following:
#11..
- 268 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-63
D.145.1 At a minimum, the Warrants module must collect, display, and monitor the following data:

D.145.2 Warrant ID
D.145.3 Warrant Type
D.145.4 Status (active, inactive, reactivated, served, recalled, etc.) D.145.5 Date of Issuance, Receipt, Service, Expiration, Extract, Returned, Reactivated, Served, Recalled D.145.6 Crime Class
D.145.7 Physical Location
D.145.8 Subject's Full MNI Data
D.145.9 Last known location (street address, apartment, room, unit, lot number, city, state, and zip code) D.145.10 Fingerprint classification
D.145.11 Associated pictures/images
D.145.12 Scars, Marks, and Tattoos
D.145.13 Issuing Court Name and ID (CA Court Directory) D.145.14 Court Case Number (alphanumeric or all numeric) D.145.15 Issuing Judge
D.145.16 Case Number (DR)
D.145.17 Warrant File Number (8 digits, starts with a 0) #11..
- 269 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-64
D.145.18 Miscellaneous Fields (per NCIC requirement)
D.145.19 NCIC Code
D.145.20 Current Disposition
D.145.21 Agency of Jurisdiction and Associated Case Number D.145.22 Agency Contact Name and ID
D.145.23 Case Agent
D.145.24 Bail Type and Amount
D.145.25 Extradition Information and Status Checks
D.145.26 Offense Code and Designated Charge Codes
D.145.27 Related Cases
D.145.28 Narrative/Remarks
D.145.29 Vehicle Information
D.145.30 Attempted Service, including:

D.145.30.1 Officer Attempting Service
D.145.30.2 Warrant ID
D.145.30.3 Date and Time of Service Attempt
D.145.30.4 The Person Completing the Service Attempt (including full name, ID, and department) #11..
- 270 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-65
D.145.30.5 Location of Service Attempt
D.145.30.6 Results of the Attempt
D.145.30.7 Narrative Description of the Attempt
D.145.31 Attempted service information is depicted in an automated report format.

D.145.32 Ability to produce automated letters and notifications to suspect and postal.

D.145.33 The Warrants module must be able to link warrants to booking charges through a booking number and booking agency or similar fields.

D.145.34 The Warrants module must be able to track extradition refused by a District Attorney.

D.145.35 The Warrants module must be able to keep track of all transactions associated with wants and warrants (i.e., maintain want and warrant histories).

D.145.36 The RMS must support the ability to scan a warrant and attach the scanned image to a case/warrant record.

D.145.37 Authorized RMS Administrators must be able to set date and time intervals that apply to one or more specific warrant types, within which at least one warrant service attempt must be completed.

D.145.38 If no service attempts have been attempted within the date and time interval set for the warrant type and agency, then one or more RMS users must be automatically notified that no service attempts have been attempted for that warrant.

D.145.39 The service attempt date and time interval expiration notice must, at a minimum, identify the warrant and provide the ability for users receiving the notification to drill down to obtain detailed information about that warrant.

D.145.40 Authorized RMS Administrators must be able to identify specific RMS users and/or user groups that must be notified within the department and for one or more specific warrant types if no service attempts occurred within the time interval set for that warrant type.

D.145.41 Authorized RMS users must be able to enter into the RMS a new want and warrant with all associated information.

D.145.42 Without having to re-enter any previously entered information, authorized and properly certified RMS users must be able to automatically upload warrants entered into the RMS to CLETS/NCIC, based on GPD, CLETS and NCIC qualification criteria.

D.145.43 Authorized and properly certified RMS users must be able to automatically update warrants in CLETS and NCIC based on updated warrant information entered into the RMS (if approved by the #11..
- 271 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-66
department).

D.145.44 Authorized RMS users must be able to update the status and information of wants and warrants stored in the RMS (e.g., change them from active to inactive, change the type, add subject's physical descriptors, etc.).

D.145.45 The RMS must notify users any time they enter a wanted person's name or the name of a person for which an active warrant exists in the RMS regardless of the department or RMS module in which the name is entered.

D.145.46 Authorized RMS users must be able generate a list of wants and warrants and associated service attempts by specifying a set of selection criteria that, at a minimum, include date and time range, one or more want/warrant types, departments, one or more individuals (subject and/or contact officer), warrant status, physical descriptions, court name and/or ID, date of last service attempt, geographic areas (e.g., precinct, grid, etc.), and various combinations of these factors.

D.145.47 Authorized RMS users must be able to print a wants or warrants history.

D.145.48 Authorized RMS users must be able to produce a report that displays expired wants and warrants.

D.145.49 The Warrants module must have the capability to provide a report of outstanding wants and warrants based upon user defined geographic information (i.e., street address ranges, reporting district, precinct, grid, neighborhood, near a specific address/location, etc.).

D.145.50 Warrants module reports must be, at the user's discretion, sorted and summarized by warrant type (e.g., felony, misdemeanor), specific offense type, and any other user specified data fields for each want and warrant.

D.145.51 Authorized users must be able to select any data field available in the Warrants module to be included in their ad hoc and standard reports.

D.145.52 The Warrants module must be relationally cross-referenced to the MNI, MLI, MPI, and MVI master indexes such that entering any information into the RMS (e.g., name and DOB) that is potentially associated with an active warrant causes a warning to be displayed to the user entering the information.

D.145.53 When a warrant is active, a flag appears on the user’s screen when viewing information pertaining to the subject.

D.145.54 Authorized RMS users must be able to track and enter warrant service attempts on their MDCs and have the RMS automatically update the Warrants module with the information entered on their MDC.

D.146.0 Mandatory NIBRS/CIBRS Compliance: The proposed RMS/FBR includes the NIBRS/CIBRS functionality as contained in the following two documents:

D.146.1 (embedded NIBRS File)
#11..
- 272 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-67
D.146.2 (embedded CIBRS File)
RMS System Administration
E.1.0 General RMS Maintenance: The RMS system administration functions address RMS configurable aspects. System administration encompasses a wide array of general functions that law enforcement agencies need from their RMS to be able to create and query information effectively; ensure appropriate access to information and systems security; and ensure effective departmental information, image, and document management. Required administrative functions include.

E.1.0.1
RMS table maintenance
E.1.0.2
RMS configurations (parameters, defaults)
E.1.0.3
Security (user role, jurisdiction)
E.1.0.4
Geofile management
E.1.0.5
Data management (data dictionary, archive and purge)
E.1.0.6
Report on users, sortable by names, access level, password age, and machine used E.1.0.7 Report on RMS usage, sortable by user log-in, frequency, total time in system, number of concurrent log-ins, machine used, and duration time-outs E.1.0.8 Report on failed log-ins, sortable by log-in name, number of attempts, date/time of attempt, and machine used
E.1.0.9
Report on subsystem security violations
E.1.0.10
Alerts; user-definable security alerts, which generate an external message to predefined locations E.1.2 Table Maintenance: RMS includes the ability for the PD to define and maintain codes and associated literals (i.e., plain English translation). The literals will be stored in the database.

E.1.3 Authoritative Code Tables: RMS uses the authoritative code tables referenced in GJXML and NCIC.

E.1.3 Record Disposition: RMS must be able to support expungement, sealing, and purging of whole records and partial records. To support this function, the system must be able to flag a record, flag data elements within a record, and delete a record. The flag indicates why the record or data element is #11..
- 273 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-68
restricted.

E.1.4 Data Redaction: In the case of formatted and structured data, report output programs produce redacted versions of specific report data. In the case of narrative or otherwise unstructured information, the redaction process requires a manual step to produce public version of the report. Relying on Adobe PDF tools, or other manual tools, to achieve this functionality would not be acceptable.

E.1.5 Data Dictionary: RMS must provide a capability to display and/or print the database structures to allow PD to access the database tables through third-party, ad hoc inquiry tools/ utilities.

E.1.6 Data Dictionary Field Descriptors: The data dictionary may contain the following information for each field description:

E.1.6.1
Field name (external representation)
E.1.6.2
Database column name (internal representation)
E.1.6.3
Data type (numeric, alpha, or date)
E.1.6.4
Field size
E.1.6.5
Field format (output format)
E.1.6.6
Edit or validation criteria
E.1.6.7
Associated code table
E.1.6.8
Default value
E.1.6.9
Description
E.1.7 General Geofile Maintenance: The system allows PD to enter and update all geofile data, including the physical address and the x/y/z coordinates.

E.1.8 Geofile Database Maintenance: The system supports the creation and maintenance of the geofile using an available mapping/ Geographic Information System (GIS) database.

E.1.9 Geofile Synchronization: Geofile information in CAD and RMS will be synchronized, based on PD-established parameters.

E.1.10 RMS Configuration Warning: Any configuration changes that could affect system integrity must be properly flagged with adequate warning to prevent inadvertent damage to the system. #11..
- 274 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-69
E.1.11 Training Environment: This function relates to the necessity of having a training environment on the RMS system that is isolated from the production and testing environments for the purposes of program testing and file maintenance testing, as well as training of new personnel. To the greatest extent possible, the training environment will be identical to the production region, thus allowing accurate testing and training to occur without impacting the production environment.

RMS Interfaces
F.1.1 NIEM Compliance: Proposed RMS interfaces are 100% compliant with NIEM standards.

F.1.2 DMV Photo Database
F.1.3 Livescan/AFIS: Fingerprint, images, and data exchange.

F.1.4 Citation Import: Citations issued via automated citation issuance devices produce data (processed by TurboData and Brazos) that may be imported into the RMS.

F.1.5 Lexis/Nexis
F.1.6 CrossRoads
F.1.7 Coplink
F.1.8 eProsecutor
F.1.9 Reserved (blank)
F.1.10 DOJ Website for Firearms Release: https://oag.ca.gov/firearms/online-reporting F.1.11 propertyroom.com
F.1.12 JMS- LARCIS (see Requirement J.123.1)
F.1.13 JMS- AJIS (see Requirement J.123.2)
F.1.14 JMS-VINE (Victim Notification): Updated every 15 minutes. #11..
- 275 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-70
F.1.15 State/Federal Interfaces (JDIC-CLETS-SVS-NCIC): RMS must query, add, and modify data elements with CLETS, SVS and NCIC; including updates for wanted people, missing people, stolen vehicles/property, and state sex offender registries. Although listed under RMS Interfaces, end-users may access the system from any CAD, RMS, or JMS workstation. The interface includes the following subsystems and transaction types:

F.1.15.1 SVS – Stolen Vehicle System
F.1.15.2 Lojack
F.1.15.3 ABS – Automated Boat System
F.1.15.4 WPS – Wanted Persons System
F.1.15.5 AFS – Automated Firearms System
F.1.15.6 APPS Armed Prohibited Persons System
F.1.15.7 Mental Health
F.1.15.8 APS – Automated Property System
F.1.15.9 CARPOS – CA Restrained and Protective Order System F.1.15.10 MPS – Missing Persons System
F.1.15.11 UPS – Unidentified Persons system
F.1.15.12 CSAR – California Sex and Arson Registry
F.1.15.13 SRF – Supervised Release File
F.1.15.14 NCIC
F.1.15.15 DMV
#11..
- 276 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-71
F.1.15.16 CHS Criminal History
F.1.15.17 FBI Criminal History
F.1.15.18 NCIC III Rap
F.1.15.19 Los Angeles County
F.1.15.20 AWSS
F.1.15.21 AWSS Active Warrant Report Request
F.1.15.22 Warrant Updates
F.1.15.23 LA County Probation
F.1.15.24 Jail Inquiries
F.1.15.25 Automated Jail Inquiry
F.1.15.26 LARS – Local Arrest Record
F.1.15.27 CJI – Juvenile record
F.1.15.28 Los Angeles County Broadcasts
F.1.15.29 DR Index Inquiries
F.1.15.30 Administrative Messages
F.1.15.31 Unformatted screen to type messages to other agencies free form F.1.15.32 Ability to build templates for Admin messages #11..
- 277 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-72
Outside California
F.1.15.33 NICB – National Insurance Crime Bureau
F.1.15.34 NLETS Criminal History
F.1.15.35 NLETS Miscellaneous
F.1.15.36 Help Files
F.1.15.37 Boat
F.1.15.38 Snowmobile
F.1.15.39 Hazardous Materials
F.1.15.40 Aircraft Tracking
F.1.15.41 LEO Flying Armed
F.1.15.42 Interpol
F.1.15.43 ICE – Immigration – Customs Enforcement Law Enforcement Support Center F.1.15.44 NCIC NSOR – National Sex Offender Registry
F.1.15.45 NCIC ID Theft File
F.1.15.46 NCIC Protection Orders
F.1.15.47 NCIC NICS Denied- National Instant Criminal Background Check System Denied Transaction File
F.1.15.48 NCIC Stolen Securities
#11..
- 278 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-73
F.1.15.49 Hit Confirmations
F.1.15.50 NLETS Admin Messages / All Points Bulletins
F.1.15.51 Oregon LEDS
F.1.15.52 Stolen Vehicles
F.1.15.53 Vehicle Registration and Driver License
F.1.15.54 Oregon Wanted Persons
F.1.15.55 Oregon Gun File
F.1.15.56 Oregon Article File
F.1.15.57 Canadian DMV
F.1.15.58 Canadian People inquiry
F.1.15.59 Wants, Charged, Prohibited, Parolee, Probation, Refused, Observed, Missing F.1.15.60 Canadian Criminal History
F.1.15.61 Canadian Stolen Property
F.1.15.62 NCIC ORI
Resource Center
F.1.15.63 Cal Gang
F.1.15.64 Cal Photo w/DMV Lineup
#11..
- 279 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-74
F.1.15.65 CCHRS (LA County)
F.1.15.66 Coplink
F.1.15.67 CSAR
F.1.15.68 DA Case Management
F.1.15.69 LinX
F.1.15.70 Megan’s Law
F.1.15.71 Parole LEADS 2
F.1.15.72 TAGRS
F.1.15.73 Trackers - Scilas
F.1.15.74 Vision
F.1.15.75 WebDV
Mobile Functionality
G.1.0
Mobile Dispatch: The mobile solution provides dispatch capabilities with a mobile device.

G.1.1 Wireless and Networked Functionality: The mobile solution functions in a wireless, and networked environment.

G.1.2
Digital Dispatch: The mobile solution receives and stores voiceless dispatch messages from CAD.

G.1.3 Database inquires: The mobile solution submits inquires to designated databases and receives responses.

G.1.4 Electronic Messaging: The mobile solution includes electronic text messaging capabilities between the Communication Center and one or more selected MDC's or defined groups of MDC's. #11..
- 280 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-75
G.1.5 Current Location Display: The mobile solution will send the unit's current geographic location (from a GPS receiver) to the CAD system for translation to a physical location and an address.

G.1.6 Function Toggling: The mobile solution will enable mobile data devices to "toggle" between different functions (i.e., electronic messaging, database inquiry, report writing).

G.1.7 Audible Alerts: The mobile solution allows the user to turn off and on any audible alerts associated with incoming dispatches, or data inquiry responses.

G.1.8 Device Disassociation: The mobile solution must provide the ability to disassociate a device from a resource remotely. (i.e., dispatcher disassociates a patrol unit from his/her device, by logging the device off, but leaving the unit logged into the system.)
G.1.9 Magnetic Stripe Reader Compatibility: The mobile solution includes the ability to use driver’s license readers.

G.2.0
Mobile Automation: The mobile solution uses Mobile Automation for managing mobile clients.

G.2.1 Update Distribution: The mobile solution allows for system administrators to distribute updates (without the need to physically touch each mobile device).

G.3.1 Multi-Tasking: The mobile solution must operate in a "multiple window" environment to support concurrent functions with true "multi-tasking" (e.g., processing a license inquiry in its own "window" while working on a field report in another "window").

G.3.2 Default Provisions: All commands performed from an MDC that allow a unit as one of the parameters, will default the user’s unit name unless otherwise entered. (i.e., A unit updates comments to his/her event by entering comment text and sending the entry). The system will automatically use the unit’s name as the default and append the comments to the unit’s current event and/or unit history.) G.3.3 Additional Queries: The mobile solution launches additional queries from a record or list of records (drill down). For example, a search on a person's name in RMS would return multiple possible matches with each name offering a hyperlink to additional information.

G.3.4 Multi-input Capabilities: The mobile solution is designed to accept input from touch screen, mouse and keyboard.

G.3.5 No Pop-Up Blockage: No pop-up windows will be required to be closed before any other work can be done in the mobile application.

G.3.6 Temporary “Lock”: Users are able to temporarily “lock” the mobile application in one step to prevent an unauthorized user from accessing the device.

G.3.7 Resume State: If the username/password is the person currently logged onto the device, the application will be return to the previous state of operation.

G.3.8 Unauthorized User Warning and Lock: If a user, other than the person currently logged onto the device, fails to enter a valid username/password after 3 unsuccessful attempts, the system will return a warning message and will not allow access until the system administrator has reset the locked user. #11..
- 281 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-76
G.3.9 Mobile View Screen (at all times): The mobile solution displays the following information at all times:

G.3.9.1
Transaction Error/Success Information
G.3.9.2
Unit Status Information
G.3.9.3
Coverage/Signal Indicator Information
G.3.9.4
Date/Time (format configurable by GPD)
G.4.0 Emergency Button: The system provides the ability to use a single keystroke (i.e., function key) to transmit the following information in an officer emergency situation:

G.4.0.1
Unit ID
G.4.0.2
Vehicle Location
G.4.0.3
Type of CFS
G.4.1 Emergency Button Actions: In an emergency situation, the information listed above is automatically sent as a notification along with an audible alert tone. This alert appears:

G.4.1.1
On all active MDC's within a user-defined zone
G.4.1.2
On individual Communications Center workstations
G.4.1.3
On Supervisor workstations
G.4.1.4
Any other system administrator defined devices
G.4.2 AVL Update increase: In an emergency situation, the frequency of AVL polling increases for the unit.

G.4.3 Download Only Changes: When making updates to system files, provide the ability to download only the changes, not the entire file, to the MDC.

G.4.4 Auto-Download Changes: The system is able to download system updates without requiring user intervention or degrading application performance.
#11..
- 282 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-77
G.4.5
Scratch Pad: The mobile solution includes a "scratch pad" feature to capture ad hoc notes.

G.5.0 Save inquiry Results: The mobile solution saves the previous 50 inquiry results on the device, or until the end of the shift.

G.5.1 Data Mining Returns: The mobile solution provides automatic drill-down of selective query returns (e.g., a license plate inquiry returns the name of the registered owner, followed by an automatic inquiry for the registered owner).

G.5.2 Visual Notifications: The mobile solution provides user-configurable audible and visual notifications when a dispatch message is received.

G.5.3 Short Message Service (SMS): The solution includes a Short Message Service (SMS) interface to allow bidirectional communication between dispatch and field units.

G.6.0 Visual Premise indicators: The application will give the user two separate visual indicators if a displayed call has: a) premise history and/or b) premise information. The user has the ability to view either one or both as separate returns.

G.6.1 View and Query Premise history: The application will give the user the option to query and view premise history and information separately from a call.

G.6.2 Summary/Detail Display: Each MDC user will have the option to choose a summary or detail display of the premise records.

G.6.3 Last 10 Incident Recall: The summary display for premise history will display a single line for each of the ten previous incidents showing the date, time, location, type and disposition of the incident.

G.6.4 Record Concatenation: The detail display for premise history will concatenate the entire content of each premise history record into a continuous text file (i.e., with no new line-delimiters) which the user may quickly review.

G.6.5 Premise Summary Display: The summary display for the premise information will display an indication of the type and number of records found.

G.6.6 Premise Detail Display: The detail display for premise information will concatenate the entire content of each premise information record into a continuous text file that the user has the option to quickly review.

G.6.7 Premise Display By Proximity: When displaying premise history records the application shall display the records first by their proximity to the incident location, and second by the date and time of occurrence (i.e., most recent occurrence displayed first).

G.6.8 Display By Predefined Order: The mobile solution allows users to sort data by system administrator-defined order. (e.g., by event status; by precedence; by time in precedence).

G.6.9 Self-Dispatching: With the exception of closed calls, officers will be allowed to dispatch themselves to any call within their MDC summary without dispatcher intervention. #11..
- 283 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-78
G.6.10 Top of Call Feature: The mobile solution allows users to jump to “top of” call details screen/display with one key stroke/click.

G.6.11 Bottom of Call Feature: The mobile solution allows users to jump to “bottom of” call details screen/display with one key stroke/click.

G.6.12 Expand/Zoom in Feature: The mobile solution allows users to expand/zoom in and out of the call detail portion of an event in order to view more text information on one screen.

G.7.0 Dynamic Updates to Events: The application will display the event changes/updates dynamically for the event currently displayed including, but not limited to, suspect information, vehicle information and additional names, location changes or main fields of an event.

G.7.1 Hotkeys Update Status: The mobile solution allows an officer to update their status with defined hotkeys (or programmable function keys) with standard functions and status information, including, but not limited to:

G.7.1.1
Unit in service, but out of car
G.7.1.2
Unit in-service but busy (downtime, eating, garage)
G.7.1.3
Unit on a call, but available
G.7.1.4
Unit en-route
G.7.1.5
Unit Arrived
G.7.1.6 Unit Clear -Available. Clear from downtime (downtime, eating, garage), or acting as backup on a call
G.7.1.7
Clear unit timer
G.7.1.8
Other status as defined by the System Administrator
G.7.2 Delayed Message Storage/Retrieval: The mobile solution stores all text messages in the mobile device for later viewing, subject to manual deletion, for the duration of a shift.

Global Functionality
H.1.0 Vendor Message Description: The vendor will define, structure, and document error and system messages. Messages shall be stored for transmission integrity in the event of a system outage.

H.1.1 System Accessibility: Authorized users must be able to perform any system task from any authorized workstation.
#11..
- 284 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-79
H.1.2 Daylight Savings: The system must allow for adjustment, if required, of the system time to change for daylight savings time on all system components.

H.2.0 Workstation User Configuration: The system must permit user-specific customization/configuration of the workstation environment, including font, font size, font color and number/placement of windows.

H.2.1 Workstation Configuration Retention: The system must retain and associate each user's workstation customizations/configuration by their User ID.

H.2.2 Workstation System Administrator Configuration: The system must restrict access to functions, views, and features based on a user's job function and security level. The system must provide features for the system administrator to establish the user job functions, security levels, and define the functions, views, and features that are appropriate for each job function and security level.

H.2.3 Message Location and Attribute Configuration: The system must provide features for the system administrator to configure the location or position, and size or color, of automatically displayed message and dialog boxes, including error messages, for any module.

H.2.4 Multiple Application Capability: The system must allow users to have multiple applications open simultaneously on the same workstation.

H.2.5 Multiple Window Capability: The system must allow users to open multiple windows for each application.

H.2.6 Window Positioning Controls: The system must provide common menu options to toggle between windows and to control the positioning of windows (e.g., cascading, side-by-side, up and down).

H.2.7
Window Sizing: The system provides the ability to minimize or maximize any window or screen.

H.2.8 Consistent Use of Commands, Syntax, Key Patterns: The system provides the ability for all functions common to more than one module and/or subsystem to use the same command syntax, function key pattern, and edit criteria.

H.2.9 Consistent Formatting: The system must provide consistent formatting of common data elements (e.g., name, date, time) across all modules and/or subsystems.

H.2.10
Common Window Features: The system must provide the following user interface features:

H.2.10.1
Error messages in plain language (e.g., not using error codes or acronyms) H.2.10.2
Feedback as to the success or failure of an action
H.2.10.3
Suggested remedies for errors
H.2.10.4
Highlighted fields or field prompts for data entry
#11..
- 285 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-80
H.2.10.5
Tool bars
H.2.10.6
Pull down menus
H.2.10.7
Automatic defaults for field values
H.2.10.8
Automatic field completion based on previous field values H.2.10.9
Drop-down lists (i.e., pick lists or code tables)
H.2.10.10 Type-ahead feature for drop-down lists (e.g., user enters "te" and cursor jumps to drop-down list values starting with "te")
H.2.11 Consistency of Look and Feel: The system must provide a common look and feel across all modules/components, including:

H.2.11.1
Layout and formatting of data input screens
H.2.11.2
Layout and formatting of data output screens
H.2.11.3
Data entry functions
H.2.11.4
Query screens
H.2.11.5
Command syntax
H.2.11.6
Help menus
H.2.11.7
Tool bars
H.2.11.8
Drop-down menus
H.2.11.9
Navigation
H.2.12 Drop-down Lists: The system must display coded values as well as the text description in all dropdown lists. #11..
- 286 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-81
H.2.13 Function Key Definition: The system must permit users to assign function keys to specific commands in order to provide "shortcuts" for common functions/commands.

H.2.14 Single Function Key Programming: The system must provide a shortcut or function key that allows the user to return to the main menu from any screen within the system via a single key press or single selection item.

H.2.14.1
Vendor's solution uses single-sign-on for all applications and interfaces.

H.2.15 Hyperlink Support: The system must permit active Hyperlinks (i.e., the user can click on the link to go to the specified location).

H.2.16
Unlimited Narrative Fields: Narrative fields have an unlimited number of characters.

H.2.17 Word Processing Features: Basic word processing capabilities (e.g., text wrapping, font size, bullets, cut, copy, and paste) are included for all fields and across applications.

H.2.18
Spellcheck Enabled: Spell-checking utility is included for all narrative/comment fields.

H.2.19 Additional information Display: The system must provide an indicator signifying that additional information remains to be displayed whenever the proposed application presents multiple "pages" of information or the information cannot be displayed within the available space.

H.2.20 Search Results Display: An authorized user, system wide, shall be able to determine how search results are displayed for searches that return multiple records (e.g., number of responses provided, number of responses shown on a page, sort criteria).

H.2.21 Search Results Sorting: When search results are displayed in columnar format, the system provides the ability for users to sort search results by column (e.g., by name, by date, by incident number).

H.3.0 System Navigation Features: The system provides the ability to navigate among all data entry screens using:

H.3.0.1
Keyboard (tab, function keys, hot keys, command line, paging and scrolling) H.3.0.2
Mouse (point and click)
H.3.1
Toggling: The system provides the ability to toggle or hot key to any screen or application.

H.3.2 Mouse or Touch Screen: The system provides the ability to use mouse and/or touch screen to invoke a function (e.g., dispatch units).
#11..
- 287 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-82
H.3.3 Page Skipping: The system provides the ability to skip pages when scrolling through search results (e.g., long list of names).

H.3.4 Keyboard Scrolling: The system provides the ability to page or scroll forward and backward through search results by using the keyboard.

H.3.5 Mouse Scrolling: The system provides the ability to page or scroll forward and backward through search results by using a mouse.

H.3.6 Screen Format Display: The system uses a common screen format for all screens that display the following:

H.3.6.1
Current system date and time
H.3.6.2
Screen name/description
H.3.6.3
System name/description
H.3.6.4
Current screen number and total number of screens (e.g., page 1 of 3) H.3.6.5
User ID
H.3.6.6
Workstation/Terminal ID
H.3.7 "Save" and "Log-off" Features: The system provides a single-click or single-select feature for save and for logoff, including each of the following options:

H.3.7.1
Hot button
H.3.7.2
Function key
H.3.7.3
Icon (tool bar)
H.3.8 Exiting: The system permits a user to exit a screen without saving changes. The system will prompt the user that they are leaving without saving changes.

H.4.0
Touch Screen: The system supports touch screen MDCs and tablets.

H.4.1 Smartphone/Tablets: The system supports smartphone technologies and the use of applications on tablets.
#11..
- 288 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-83
H.4.2 Uninterrupted Data Entry: The system must allow the user to continue data entry while the system is processing a previous transaction.

H.4.3 Data Population: The system must pre-populate entry screens with previously entered data (e.g., name) to minimize redundant data entry.

H.4.4 Drop Down Entries Based on Previously Entered Data: The system must provide context sensitive "drop-down lists" that are based on prior entries (e.g., drop-down lists associated with a field vary depending upon type of incident).

H.4.5 Data Validation: The system must verify all required data fields have been completed prior to exiting a screen. If a required field is not completed, the system must present a warning message to the user indicating which required fields have not been completed. The system must prevent the user from exiting the screen until all required data has been entered.

H.4.6 Transactional Data Validation: The system must verify all required data fields have been completed prior to executing a transaction. If a required field is not completed, the system must present a warning message to the user indicating which required fields have not been completed. The system must prevent the user from exiting the screen until all required data has been entered.

H.4.7 Instructions for Completing Incomplete Data: The system prompts or advises the user of required data necessary to complete a transaction or report.

H.4.8 Use "If/Then" Logic: The system permits the use of conditional validations ("if/then") logic to validate data entries.

H.4.9
Field Types Validation: The system validates data entry based on field types (e.g., date, numeric).

H.4.10 Current Age Default: The system must calculate and display a person's current age based on the date of birth entry.

H.4.11 Logic-Driven Rules: The system must apply logic-driven rules to support field-level data validation (e.g., on-scene time occurs after call is closed, or age entered conflicts with Date of Birth).

H.4.12 Name Validation Against MNI: The system must validate names against the MNI when the name is entered and provide a list of possible matches, and;
H.4.12.1
If the user selects one of the possible matches, the application will pre-populate the data fields.

H.4.13 Address Validation Against MLI: The system must validate locations against the MLI when the location is entered and provide a list of possible matches, and; H.4.13.1
If the user selects one of the possible matches, the application will pre-populate the data fields.

H.4.14 Vehicle Validation Against MVI: The system must validate vehicles against the MVI when the vehicle is entered and provide a list of possible matches, and; #11..
- 289 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-84
H.4.14.1
If the user selects one of the possible matches, the application will pre-populate the data fields.

H.4.15 Duplicate Records: The system provides a feature to copy an existing record in order to create a new record.

H.4.16 Calendar Options: The system provides the ability to provide day of the week and Julian date capabilities.

H.4.17 Table Matching: The system must calculate and display the correct day of the week based on the calendar date for all date fields.

H.4.18 Agency Defined Table Data Conversion: The system provides the ability to convert agency-defined data lists to drop down lists (aka pick lists or code tables).

H.4.19 Non Case Sensitive Format Support: Data entered and stored in the system shall be treated as noncase sensitive.

H.4.20 Undo or Cancel Feature: The system must provide a feature to undo or cancel an entry or transaction prior to saving it.

H.5.0
Print Capabilities: The system provides the ability to print from any screen.

H.5.1 Print to Any Printer: The system provides the ability to print to any printer within the authorized network from any application, subject to GPD security protocol.

H.5.2 Select Print: The system permits the user to selectively print information (e.g., incident history, premise information, search results):

H.5.2.1
Print single record
H.5.2.2
Print group/all records
H.5.3 Print Auditing: The system provides the ability for the System Administrator to audit system print screens to identify user, date, time, and workstation used to print.

H.6.0 Update all Application Clients: System has management functionality to automate deployment of updates to all application clients (e.g., workstations and MDC's) and manage configuration settings.

This includes application upgrades, releases and configuration settings.

H.6.1 User-initiated Upload: The system provides the ability to support the upload of software updates as a background operation at log-on or log-off.

H.7.1 Applying Current Patches: The proposed system is compatible with utilities used for applying operating system and third-party software updates (e.g., Microsoft Windows updates).

H.7.2 Antivirus: The solution is compatible with antivirus software (identify preferred antivirus software in the comments).
#11..
- 290 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-85
H.7.3 Input Mechanism Support: The mobile system allows user input via the following input mechanisms:

H.7.3.1
Keyboard
H.7.3.2
Touchscreen
H.7.3.3
OPTIONAL: Pen-based
H.7.3.4
OPTIONAL: Voice-recognition
H.7.3.5
OPTIONAL: Magnetic Card Readers
H.7.4 Edit and Purge: The system provides a feature for authorized users to selectively edit and purge information (based on security level):

H.7.4.1
Purge single record
H.7.4.2
Purge by type of record
H.7.4.3
Purge by date
H.7.4.4
Purge group/all records
H.7.4.5
Purge all except specific records
H.7.4.6
Agency defined purge parameters
H.7.5 Standard Report Does Not Impact Enterprise: Running standard reports shall not degrade call taking and performance in any way.

H.7.6 Log of Failure: When an application failure occurs, the proposed system logs the failure in a format that is comprehensible and accessible to GPD System Administrators. Error log should contain adequate information so technical support engineers can establish the cause of the failure. Error log should include detailed information, such as nature of error, database affected, date/time error occurred, workstation and user ID on which error occurred, command/function being executed, and module/component at fault.

H.7.7 Automated Backup: The solution has been designed to backup data automatically to permit operational and application continuity should the system experience a single point of failure. #11..
- 291 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-86
H.7.8
Mobile RMS Access: The mobile data devices must be able to access the RMS from field locations.

H.7.9
Failover: The proposed system must provide CAD failover capabilities.

H.7.10 Remote Administration: The proposed system must be capable of remote administration, including the ability to apply patches and restart the system via a remote system console.

H.7.11 Multiple Separate Windows/Work: The system must be compatible with multiple monitors to allow users to switch focus between monitors via a single keyboard and mouse.

H.7.12 QWERTY Keyboard: The CAD and RMS keyboards shall be the standard QWERTY 104 keyboards with 12 function keys, 10-key pad, arrow keys, Microsoft hot keys.

H.7.13
Keyboard Adjustment: The CAD and RMS users must be able to adjust the “tilt” of the keyboard.

H.7.14
The system relies on a standard PC mouse, except:

H.7.14.1
The CAD standard pointing device must be a ball-mouse.

H.7.15 Switch between the Standard Keyboard: Users must be allowed to switch between the standard keyboard/mouse and the users preferred device(s) (e.g., ergonomically-designed keyboards, trackballs).

H.7.16 Switching of Peripheral Device(s): The switching of peripheral device(s) must be done without having to either shutdown the system software or workstation and/or unplug and plug in devices.

H.7.17 One Time Peripheral Installation: The installation and configuration of peripheral device(s) shall be a one-time event. The system should not require it to be re-installed each time it is disconnected and reconnected.

H.7.18 Wireless Device Configuration: Any wireless devices must be able to be installed and configured so that devices from one workstation do not interfere with devices at other workstations.

H.7.19 PS/2 and USB Device Compatibility: The use of wireless devices shall not preclude the use of PS/2 and USB devices.

H.7.20 Included Hardware: The proposed vendor can provide all racks, tables, stands, or other required mounting facilities for the proposed CAD solution, consoles, communications, and/or network equipment consistent with their proposed configuration(s).

H.7.21 Application Restores Completely to Environment at Failure: in the event of a failure, the proposed CAD and RMS system operations must resume to the state that existed when it was shut-down.

H.7.22 System Changes Do Not Impact incidents, Units, Messages: System changes (e.g., updates, upgrades, enhancements, bug fixes) must be made local users or via remote system administration without loss of incidents, units, or messages.
#11..
- 292 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-87
H.7.23 System Shutdown Controlled: The system shut down routine must perform the shut down process in a controlled manner and must save the operational environment.

H.7.24 Time Synchronization: The proposed system must interface with a time synchronization device utilizing Network Time Protocol (NTP) in order to ensure consistent and accurate time throughout all system components (without the need to restart a session or device).

H.7.25 GPD Environmental Support: The proposed system workstations must perform all functions and access all information within the products while providing access to CLETS; access to the internet; access to email or other office automation applications; and access to other GPD applications and utilities.

H.7.26 Correct Workstation Sizing: The vendor has proposed an appropriate workstation configuration based on the needs of the CAD system.

H.7.27 Sub Second CAD Response Support: The proposed CAD system (hardware, software, networking, and all ancillary components) shall support all CAD standards functions/selections requested activities with a sub-second response time for 99 percent of all transactions on a daily basis.

H.7.28 Incident Routing: The proposed CAD system must be able to route an incident to any authorized user with only minimal data (i.e., incident type and location) having been entered, while allowing additional call details to be added, as they become known.

H.7.29 Online Updates Do Not Impact Performance: System files and tables, including the Geofile, shall be capable of being updated on-line without affecting system performance.

H.7.30 Backup Without Degradation: Backup of system data files must be able to be done on-line without degrading system functionality to levels that are below expected standard service and response levels.

H.7.31 System Performance Not Impacted by GPD Stated/Required Utilization: The proposed system must be configured and able to support the workstations defined in the RFP.

H.7.32 System Documentation: The proposed solution includes a complete set of system documentation including general design documents, data dictionary, system architecture, network architecture, file/table layouts, and operational manuals.

H.7.33 Restricted Value Definition: The proposed system must allow authorized system users to define the restricted values for any field; define and dynamically change deployment plans, disposition codes and incident dispositions; manage the CAD configuration files and security tables; perform system administration activities from any workstation with the appropriate sign-on; perform database optimization tasks including arriving and purging of selected data using a vendor-supplied utility; establish and reset passwords; and maintain area, beat, unit status code, priority, incident type, officer information, and other supporting data files and tables.

H.7.34 System Alarms and Messages: The proposed CAD system must be set to send messages and/or alarms to appropriate authorized system users alerting and informing them of system problems. For example, should a CAD failover occur, the operational CAD system would send a message to GPD #11..
- 293 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-88
system administrator, alerting them of the failover.

H.7.35 Backup Medium Not Proprietary: The backup medium is not proprietary to the proposed vendor, and is available from multiple sources.

H.7.36 Database/File Integrity: The proposed CAD system maintains database/file integrity in the event of a disk drive failure; and, in the case of mirrored disk drives, if both disks in the pair fail simultaneously.

H.8.1 Fields May be Added to Screens: The GPD System Administrator shall have the option to add/remove user-defined fields to the screens at the organizational level (not at the agency level).

H.8.2 Report Fields Configurable: The system shall provide a feature to allow the System Administrator to add/remove user-defined fields to reports.

H.8.3 Report Saving Features: Mobile and RMS users shall have the ability to save an incomplete report, transaction, or request.

H.8.4
GPD Specific Configurations: The vendor is responsible for configuring the software with:

H.8.4.1
Agency defined validations and edits
H.8.4.2
Agency defined forms
H.8.4.3
Agency specific processes/workflow
H.8.4.4 Tools provided to allow agency to develop additional custom forms and/or modify existing forms without assistance from vendor, with proper training.

H.8.5 Mandatory Configurations: The system shall provide a feature/tool which allows the system administrator to define which fields and parameters are mandatory for a given command or function.

H.8.6 User Definable Macros: the system shall provide a feature/tool to create macros that combine two or more individual commands or other actions.

H.9.0 System Security: Any access to databases must first pass through system security, regardless of the route or purpose of access (including ad-hoc inquiries).

H.9.1
Role Based Security: The proposed application shall incorporate role-based security.

H.9.2 Security Levels: Security levels and user profiles shall be defined by either on-site or remote workstation administrators.

H.9.3 Levels of Security: Role-based security groups shall restrict access to system functions at the following levels:

H.9.3.1
Application/subsystem
#11..
- 294 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-89
H.9.3.2
Screen/transaction
H.9.3.3
Record
H.9.3.4
Field
H.9.4 User Account Auditing: The proposed solution provides system administrator-controllable useraccount auditing.

H.9.4.1
Change
H.9.4.2
Add
H.9.4.3
Delete
H.9.4.4
View/Print all screens from all modules
H.9.5 User Security information: Maintain the following user security information and audit trail, accessible to GPD technical personnel:

H.9.5.1
User ID
H.9.5.2
User Name
H.9.5.3
Security level
H.9.5.4
Last inquiry, update or delete--date, time, user initials, transactions H.9.6 Logging Restrictions: If a user unsuccessfully attempts to logon to a position a System Administrator defined number of times, the user’s account will be locked and must be unlocked by the System Administrator.

H.9.7 Security Profiles: The proposed application shall include a security profile for devices which has the option to limit access to forms, commands, features, interfaces and other aspects of the application based on the device type and user role.

H.9.8 Device Security Permissions: Device security permissions shall always supersede the permissions of the logged on user. For example users might be prohibited to run NCIC III inquiries from mobile devices.
#11..
- 295 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-90
H.9.9 User De-Activation: The system must maintain an electronic history of de-activated user IDs and prevent using de-activated user IDs when adding new users.

H.9.10 Password Protection: The system prevents display, view and print of passwords and stores all passwords in an encrypted format.

H.9.11 Data Element Flagging: The system flags a data element as sealed/expunged for security purposes by authorized RMS personnel.

H.9.12 User Alerts: The system highlights, flags, or otherwise alerts users with the appropriate security access that a record or data element has been flagged as requiring sealing or expungement.

H.9.13
File Security: The system provides the following security features:

H.9.13.1
Track any files that have been altered and printed.

H.9.13.2
Provide appropriate role-based security access based on the user ID and password H.9.14 Security Based Display: The system must display and print data in accordance with the user's role and security level and the security level of the data.

H.9.15 Auto-Log Off: The system automatically logs off users after a system administrator defined period of inactivity, with no loss of data.

H.9.16 Auto-Log Off Upon New Log-in: The system automatically logs user off from devices when they sign onto another device.

H.9.17
User Profiles: The system maintains user profiles for:

H.9.17.1
User role
H.9.17.2
User ID
H.9.17.3
User name
H.9.17.4
Location
H.9.17.5
Default printer location/address
H.9.17.6
Date/Time of last update
#11..
- 296 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-91
H.9.18 CLETS Recording: The system retains all user CLETS records for the entire life of that user ID plus two years.

H.9.19 Tiered Access: System allows tiered access to information, based on passwords and other authentication and non-repudiation practices.

H.9.20 CLETS Recording: The proposed system complies with all Department of Justice CLETS security and reporting requirements.

H.9.21 Ability to enter "WHO" command to view list of all active users (logged into the CAD, RMS, and mobile applications).

H.9.21.1 Ability to define groups of users to query their status (i.e., "WHO CAD" would show all users logged into CAD, while "WHO RMS" would show all users logged into RMS).

H.9.22
CJIS Security Compliance: The proposed system complies with all FBI CJIS security policies.

H.10.0 Geovalidation: The system will perform address geocoding using the city's GIS data and store the x/y/z values in the database.

H.10.1 Address Modification: The system allows an authorized user to modify street address files, including the ability to temporarily edit block face, dummy intersections, aliases, and commonplace files.

H.10.2 Coordinates in Degrees: The system displays and prints latitude/longitude coordinates expressed in degrees.

H.10.3 Geocoding Relies on Granularity: The system automatically selects the most appropriate Geofile record of decreasing or increasing granularity to obtain geocoding of the greatest accuracy given the address provided in the applicable field. Information returned will include call sign (or dispatch position), name, and the person’s designated number as contained in their personnel file.

H.10.4 Geofile Loading: The system permits the loading of Geofile map modifications. Modifications are available to the user without restarting the system.

H.10.5 GIS Modification Immediately Available: The system allows modifications made to the GIS database to be available immediately and shall not require the system to be halted.

H.10.6 ArcGIS-Compliant: The proposed system is Environmental Systems Research institute, Inc. (ESRI) ArcGIS-compliant.

H.11.0 Mapping integration: The solution shall include an integrated mapping subsystem that will be used to provide geographic context to CAD/RMS/MDS records and perform spatial analysis of CAD/RMS/MDS data.

H.11.1 Location Verification: The mapping display and location verification process shall utilize the same geographical data sets or be created from the same data file. Maintaining two separate geographical databases is not acceptable.
#11..
- 297 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-92
H.11.2 Mapping Attributes: The system shall allow the authorized user to set the following attributes for the map:

H.11.2.1
The default display position on the monitor.

H.11.2.2
The default size of the map when it is displayed.

H.11.2.3
The default view and zoom level.

H.11.2.4
The default layers which will be displayed on the map.

H.11.2.5 The colors utilized on the map shall be consistent with those chosen for use within CAD. (e.g.: If a unit's status changes, the color used in CAD to signify that status (enroute, on scene, available, etc.) will also be used as the color of the unit on the map.)
H.11.3
Map Manipulation Features: The system includes the following map manipulation functions:

H.11.3.1
Zoom in and zoom out.

H.11.3.2
Pan in any direction.

H.11.3.3
Add and remove (i.e., view and hide) layers of the map.

H.11.4 Map Manipulation from Sources: The system allows the user to manipulate the map (pan, zoom) from the command line, a menu command or with a mouse.

H.11.5 GIS Layer Display: The system allows users to display any GIS layer that is part of the proposed system, on the map.

H.11.6 Map Symbol Connection to Records: All map symbols representing an underlying text record will be associated with the text record such that a user shall have the ability to double-click, right-click or position the mouse on the icon and the textual record will be retrieved.

H.11.7 Map Zoom: The system allows users to enter a street address, intersection, commonplace name, or other verifiable location and have the map zoom to the location and place an icon in the correct position.

H.11.8 External Query Based on Geofile: The system provides the ability to query outside systems for additional GIS information. For example, it shall be possible for a user to retrieve and display aerial photos of a given area of the map from an external orthophotography system.

H.11.9 GPD-Definable Icons: The system allows users to define and utilize a different icon for each category of premise information.
#11..
- 298 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-93
H.11.10 Location Based on Clicking: The system allows users to select a location by clicking on the map screen with a mouse (or other pointing device) and the application will display the nearest known street address, intersection name or commonplace name for non-addressed locations (i.e., McDonalds).

H.11.11 Cut and Paste into the Location Field: The system allows the location information to be inserted into a screen by executing a “cut-and-paste” procedure or by a similar function.

H.11.12 Water Locations: if the identified location is on water and within the map area the application shall display/print the latitude/longitude coordinates.

H.11.13 Latitude/Longitude Cutting/Pasting: The system allows the latitude/longitude coordinates information to be inserted into a screen by executing a “cut-and-paste” procedure or by a similar function.

H.11.14 Icon Display of Premise Information: The system displays icons which represent the presence of premise information at a location.

H.11.15 Location of Route Blocks: The system displays the location of route blocks and impediments on the map by using different icons to represent common categories of impediments.

H.11.16 Table Creation and Viewing: The system allows authorized users to create and view tables for underlying data depicted on map.

H.11.17 Graphical GIS Tools: The system includes graphical tools to allow authorized users to maintain, view, or print from the GIS database. These tools shall have the following minimum capabilities:

H.11.17.1
Add, modify, or delete any graphic element (e.g., a street or intersection).

H.11.17.2
Move any graphic element.

H.11.17.3
Add, modify, or delete the database record associated with any graphic element.

H.11.17.4
Add, modify, or delete the text labels associated with graphic elements on the map.

H.11.18 Modifications to GIS Do Not interrupt Applications: Modifications made to the GIS database with the CAD/RMS/MDC tools shall be available immediately and shall not require the system to be halted.

H.11.19 Physical Identification of Non-Geocoded Locations: The system allows users to physically identify a location on a map to generate x/y/z coordinates for location-specific-data that doesn’t geocode.

H.11.20 Disaster Recovery: The system supports fail-over or concurrent operation from a geographically distant location.

H.11.21 Environments: The solution should include the following environments: PROD, TRAIN, BUILD/TEST (with commands to make porting over to a different environment simple - single execution)
#11..
- 299 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-94
AVL
I.1.0
CAD Automatic Vehicle Location (AVL) is integrated with the mobile solution.

I.1.1
The solution supports numerous GPS devices including both TAIP and NMEA standards.

I.1.2
The software provides configurable icons for tracking police units on the map.

I.1.3
The CAD AVL Map allows a "quick access" option, using standard windows ribbon functionality.

I.1.4
The software provides a playback feature.

I.1.5
The Playback feature allows the selection of specific unit(s).

I.1.6
The Playback feature allows the selection of date/time ranges.

I.1.7 The Playback feature shows the unit location, coordinates, and speed for each stored AVL transmission.

I.1.8 More than one type of GPS standard may be used concurrently (for example, one agency's devices use TAIP, and another uses NMEA).

I.1.9 The system administrator may define criteria that affects how often AVL data is refreshed on the call screen (for example, call type, distance traveled, speed, etc).

I.1.10
The AVL data is logged in the database and easily retrieved for reporting later.

I.1.11
The logged data includes the LAT/LON, or X/Y/Z coordinates for each point that is captured.

I.1.12 The solution includes a mechanism that allows authorized operators to "play back" AVL data within a given timeframe, for specific units or an entire range of units.

I.1.13
The Playback feature may be provided to authorized personnel inside each agency.

I.1.14 The solution includes a mechanism to save the AVL playback in a standard video format, such as WMV, MP4, etc.

I.1.15 The software has the ability to provide mobile units with routing information to a dispatched incident from their current GPS/AVL location.
#11..
- 300 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-95
I.1.16
AVL provides CAD with routing to an event using street impedances to factor fastest route.

I.1.17
The map provides both turn by turn and route indicators.

I.1.18 The CAD software provides a driving directions toolbar which launches a directions window for easy navigation, allowing the directions to "float" over the map.

I.1.19
Auto-routing supports both units to calls and from call to call.

I.1.20 Auto-routing uses a "find route" function that allows both text based driving directions and a visual route line on the map.

I.1.21 Operators (with the correct permission) can overlay historical AVL data collected from field units and display that data on the map.

I.1.22 The AVL data may be played back in chronological sequence, showing the movement of the field unit over a specified period of time.

I.1.23 Historical data from both the CAD and RMS systems may be overlaid on the same map (for example, a map showing all CAD calls related to fireworks complaints, and all RMS contacts related to fireworks violations).

I.1.24 The solution has the ability to provide mobile units with routing information to a dispatched incident from their current GPS/AVL location.

I.1.25
Ability to use AVL for closest dispatch
I.1.26
Ability to add closest dispatch feature by Unit ID
I.1.27
Ability to use AVL even when the mobile device is not turned-on by the user.

JMS
J.1 Information entered into JMS shall be validated on entry, and identified errors shall be resolved before additional information can be entered. The system edits necessary to perform this validation shall be controlled by a combination of user-defined and user-maintained parameters. A list of possible values for each field of entry will be provided to the operator by pressing the appropriate key sequence. These values will be user-maintained
J.2 JMS shall accept and correctly process hyphenated names in any name component, first, middle, and/or last
J.3 JMS shall use Soundex coding in name searches to minimize the impact names with similar and variant spellings and of misspelled names (either on entry or in requesting a name search) #11..
- 301 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-96
J.4 JMS shall allow for interruptions in data entry to accommodate other necessary tasks (i.e., a user may interrupt entering suspect data in order to conduct an inquiry) J.5 The user shall be able to request that JMS remind detention facility personnel (with audible and visual notifications) when they are to perform required actions. These may be inmate-specific (e.g., check an inmate on suicide watch), or they may be more general (e.g., check the contents of emergencyresponse kits). Users may schedule actions based on the following criteria:

J.5.1 Inmate information (Name)
J.5.2 Housing Location (Unit)
J.5.3 Booking Number
J.5.4 Type of Action Scheduled
J.5.5 Date and Time of Scheduled Action
J.5.6 Type of Alert
J.5.7 Position(s) to Receive Alert
J.6 Alert messages (such as computer-generated notifications, schedule reminders, and operator-error messages) shall be accompanied by suitable attention-getting audible signals J.7 Solution will share data amongst all points of entry within RMS and JMS (For example, once booking information has been entered on an inmate, it is available to all other JMS functions:
classification, housing, transportation, food services, commissary, and medical services)

DETENTION PROCESSING AND ACCOUNTING
J.8 If a user attempts to input information out of sequence, or the information entered is inconsistent with requirements for information entry, the entry shall be rejected, and an error message shall indicate the reason for the rejection, and the minimum requirements that must be met for the entry to be accepted J.9 The user shall be able to return to a screen already processed to add optional information, or to modify information previously entered
J.10 JMS shall not allow the modification of previously stored information that creates inconsistent conditions
J.11 JMS shall allow a user to cancel an action at any time prior to his or her completion of that action #11..
- 302 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-97
J.12 Upon determining that the user has canceled an action, JMS shall restore any interim information entries the user has made to their status prior to the initiation of the action J.13 JMS shall allow the user the ability to access any screen with the minimal use of sub-menuing J.14 JMS shall display an inmate's current account balance on the general information screen for each inmate
J.15 A display shall indicate the current status of a booking, and shall permit the user to determine what has to be done to complete that booking
J.16 The information typically entered into JMS on a booking is listed below. The information below shall be obtained initially from the RMS reporting module (used by officers for entering their crime and arrest reports). Any information that is not entered through RMS shall be entered directly into JMS.

Notwithstanding the list below, the selected vendor’s solution must include all of the NIBRS and CIBRS data elements associated with an arrest, as defined in the Appendix (see CA DOJ CIBRS DATA ELEMENTS).

J.16.1 Name (Last, First, Middle, Suffix)
J.16.2 AKAs (no limit)
J.16.3 Permanent Address
J.16.4 Temporary Address
J.16.5 Telephone Numbers(s)
J.16.6 Date of Birth (multiple)
J.16.7 Place of Birth (City, State, Country)
J.16.8 Foreign National
J.16.9 Social Security Number (multiple)
J.16.10 Sex
J.16.11 Race of Arrestee
#11..
- 303 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-98
J.16.12 Hair Color
J.16.13 Eye Color
J.16.14 Height (Feet and inches)
J.16.15 Weight (Pounds)
J.16.16 Scars, Marks, Tattoos: Common SMT (or SMTs) and location (or locations) selected from user-maintained lists; unusual SMT (or SMTs) described in a free-form text field J.16.17 SMT image processing required - flag(s), identification(s), and location(s) to alert for unusual SMT(s) which should be recorded, usually when mug shots are recorded (manually set) J.16.18 Date and Time of Arrest
J.16.19 Arresting Agency
J.16.20 Arrest Location (Address and Common Place Name) J.16.21 Arrest Charge(s)
J.16.22 Arresting Officer’s Department and ID
J.16.23 Transporting Officer’s Department and ID
J.16.24 Driver’s License Number (multiple)
J.16.25 Vehicle License Plate and State
J.16.26 Vehicle Disposition
J.16.27 Special Identifiers (i.e., Career Criminal, Sex Offender, etc.) J.16.28 Gang Affiliation
#11..
- 304 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-99
J.16.29 Agency DR Number
J.16.30 Date and Time Booked
J.16.31 Booking Officer’s ID
J.16.32 Searching Officer’s ID
J.16.33 Arrest Bail (Automatically calculated from user-definable table) J.16.34 Property Description (Cash and Non-Cash)
J.16.35 Booking ID Number (Jail Number)
J.16.36 Emergency Contact information
J.16.36.1 Name
J.16.36.2 Relationship
J.16.36.3 Address
J.16.36.4 Telephone Number
J.16.37 Occupation
J.16.38 Employer(s)
J.16.38.1 Occupation
J.16.38.2 Name
J.16.38.3 Address
#11..
- 305 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-100
J.16.38.4 Telephone Number (Multiple)
J.16.39 FBI Number (multiple)
J.16.40 AFIS Number
J.16.41 State of California Identifier Number (CII) (multiple) J.16.42 Department of Corrections Number (multiple)
J.16.43 Calculated Release Date
J.16.44 Citation Number
J.16.45 Internal Identification Number (Booking Number) J.16.46 Alien Registration Number
J.16.47 Sentencing Date
J.16.48 Warrant arrest information
J.16.48.1 Judge name and information
J.16.49 Local and/or foreign warrant number
J.16.50 Foreign or out of County
J.16.50.1 Field to identify County
J.16.51 Warrant number
J.16.52 Remanded booking/Commitment Court-Ordered Booking #11..
- 306 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-101
J.16.53 Court case number
J.17 JMS shall provide a field for the entry of an inmate's primary language and dialect, selected from a user-maintained list. The automatic default for this field shall be English.

J.18 Bail Calculation: JMS shall compute bail based on a stored list of charges and associated bail amounts. Charges and associated bail amounts shall be user-maintained values. JMS shall place no limit on the number of charges and bail amounts it can store. JMS shall also prompt the user for data that cannot be determined from charge codes, but on which the bail depends (for those charge codes for which this information is required). Since some charges do not have a known bail (e.g., warrants), and not all charges will be in the system, JMS shall accept the manual computation and entry of bail. The system shall also accept the values of:

J.18.1 "No bail" (i.e., no bail is required, if other conditions are met for release) J.18.1.1 Name of authorizing personnel
J.18.2 Felony vs. Misdemeanor identification
J.18.3 Bail conditions
J.19 JMS shall display identifying information about an inmate, and the amount of bail required for his or her release from custody. This display shall include each charge and/or warrant that comprises the total amount of bail. JMS shall accept a bail transaction at the time of booking, or at any time while an inmate is in custody, but has not been convicted (excludes bench warrants) J.20 The system should enable a checkbox for any cash bails received J.21 The following is typical of the information that JMS shall require to process bail:

J.21.1 Name of person or bonding company posting the bail J.21.2 Amount of bail posted (partial or complete)
J.21.3 Charge or charges against which the amount of bail is to be applied - in order of application to bail amounts (if requested by person or bonding company posting bail) J.21.4 Bond number - for a bond only
#11..
- 307 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-102
J.21.4.1 Name of bonding company
J.21.4.2 Name of insurance company insuring the bond
J.21.5 Dept. ID of Officer accepting the bail - entered by the system J.21.6 Date and time bail was posted - entered by the system J.22 Bail receipts for all participants shall be printed in sequential order J.22.1 includes foreign currency calculation
J.23 When JMS has received an amount of bail equal to the total for all charges, the system shall print a notice to release at the holding area printer (if the inmate has not been transferred to a housing unit) J.24 The proposed solution will enable collection of intake medical information.

J.25 The proposed solution conforms with HIPPA regulations regarding security and privacy of medical data collection
J.26 If JMS contains medical history based on a prior record (or records), the system shall alert the user when a previous dangerous condition has not been recorded during the current booking J.27 A user shall be able to enter information on an inmate that indicates that he or she should not associate with other specific prisoners
J.28 The system shall prohibit any inmates that should be kept separate from being placed in the same housing unit
J.29 The system shall provide an alert when inmates that should be separated will be assigned to the same activities and programs (e.g., will be transported on the same bus) J.30 Alerts shall be included in any printed lists of inmates (e.g., daily worksheets) J.31 Alerts should include phone restrictions
J.32 JMS shall accept miscellaneous comments entered as free-form text. Comments shall be kept in the order in which they are entered; and each comment shall include the Dept. ID of its author and the date and time of entry
J.33 Ability to prepare the following standard reports, in addition to ad hoc reports:
#11..
- 308 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-103
J.33.1 Monthly Arrest and Citation Register (MACR), submitted electronically monthly J.33.2 Adult Disposition of Arrest and Court Action Report (JUS-8715) J.33.3 Monthly Juvenile Detention Report
J.33.4 Monthly Booking and Confinement Report
J.33.5 Monthly Release Report
J.34 Processing of inmate Cash: JMS shall establish a cash account for every inmate booked into the system, even if the inmate has no cash to deposit in it J.35 JMS relies on the RMS Property/Evidence module for processing inmate property with single-signon access to RMS from JMS booking workstations (including all necessary bar-code technology/peripherals).

J.36 Setting Court Appearances/Dates: JMS shall determine, from a user-maintained list, the specific court that has jurisdiction over an inmate’s case
J.37 Inmate identification information may be printed as a label on the booking sheet. The number, size, and content of any other labels printed on the booking sheet shall be user-definable J.38 The inmate identification information shall include the following information J.38.1 Name
J.38.2 Booking Number (numeric and bar code)
J.38.3 Bar Code Number
J.38.4 Mugshot Image
J.39 Home Custody/Work Release inmates: JMS will treat the booking of a home custody/work release inmate in an identical manner to that of a booking for a standard, continuous incarceration, except that the booking employee shall be able to:

J.39.1 Indicate to JMS that the sentence is to be served on a discontinuous basis by selecting custody/work release status on the appropriate booking screen J.39.2 Designate the periods of time during which the sentence will be served by selecting them from a calendar-like display
#11..
- 309 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-104
J.40 JMS shall allow a booking employee to enter a transfer of housing location to the inmate's residence address and retain an inmate's booking record in inactive status, pending the next period of incarceration (When the defendant returns to serve a subsequent period of incarceration, JMS shall allow a booking employee to retrieve and activate the defendant’s booking record, indicating a transfer from the defendant’s residence to a suitable housing location in the detention facility) J.41 Disposition Information: JMS shall allow for disposition information to be entered into the RMS Master Name Index (MNI) record for an inmate
J.42 If the inmate is sentenced to serve time in local custody, then JMS shall have the ability to calculate the release date, considering credit for time served, “good time” and “work time” credits and debits, percentage reductions and any other sentence modifications allowed by law, any court or other lawful process. The algorithm for this calculation shall be user-maintainable and definable J.43 JMS shall release inmates for any of the following reasons:

J.43.1 Time limit without arraignment has run - an inmate has been detained for the maximum allowable period of time without having been arraigned. This type of release shall cause JMS to distribute information on the release to a user-maintained list (e.g., responsible investigator, investigator's supervisor)
J.43.2 Time served (automatically calculated)
J.43.3 Court authorized - the standard type of release
J.43.4 Transferred - custody of an inmate has been transferred to another agency or person [e.g., home bracelet detention]
J.43.5 Escape
J.43.6 Parole
J.43.7 Temporarily released to external agency
J.43.8 Death
J.43.9 Remanded to prison - an inmate has been convicted, and is transferred to state or federal prison J.44 At the time of an inmate's release, JMS shall display for the Officer performing the release functions the inmate's classification code and any special handling-alerts applicable to him or her (i.e., domestic violence notifications)
#11..
- 310 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-105
J.44.1 Prior to release, JMS shall conduct the following processes:

J.44.2 Check the Want/Warrant System to determine that the inmate is not subject to any outstanding warrants
J.44.3 Require a positive identification before any inmate can be released J.44.4 Update all inmate records (e.g., criminal history) J.45 JMS shall prepare a daily booking log, which shall list all inmates booked during the preceding 24- hour period. The daily booking log shall typically contain the following information on each inmate:

J.45.1 Name - last, first, middle, suffix
J.45.2 Identification number
J.45.3 Booking date
J.45.4 Booking time
J.45.5 Arresting/booking agency
J.45.6 Date of birth
J.45.7 Sex
J.45.8 Race
J.45.9 Document number (or numbers)
J.45.10 Charge(s)
J.45.11 Office ID
J.45.12 Officer Name
#11..
- 311 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-106
J.45.13 Custody Status
J.45.14 Warrant Number (if any)
J.45.15 Type of Warrant (local, other)
J.46 JMS shall maintain a set of accounts that will report the balance of:

J.46.1 Accounts receivable for inmate worker pay
J.46.2 Accounts payable for bail and fines
J.47 JMS should have the ability to post bail and fine receipts to the General Ledger and generate the appropriate accounting reports
J.48 JMS should have the ability to place holds on inmate’s account transactions J.49 For previously released inmates that are re-booked with a new Identification number, the system should be able to track any remaining moneys or negative balances associated with the previous Identification number of this inmate
J.50 JMS shall generate the following reports on a routine, user definable basis:

J.50.1 Detention cash summary
J.50.2 Balance sheet
J.50.3 Proof-of-Cash report
J.50.4 General Ledger Activity report
J.51 Generate receipts on any money transactions

IDENTIFICIATION REQUIREMENTS
J.52
Utilizing the Live-Scan device, a fingerprint technician shall be capable of downloading identification information on any subject match to JMS. The system should capture and populate the JMS entry fields for the following criteria:
#11..
- 312 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-107
J.52.1 Name - last, first, middle, suffix
J.52.2 AKAs
J.52.3 Sex
J.52.4 Race
J.52.5 Height
J.52.6 Weight
J.52.7 Hair color
J.52.8 Eye color
J.52.9 Date of birth (multiple)
J.52.10 Place of birth
J.52.11 Social Security number (multiple)
J.52.12 Booking date
J.52.13 Charge (or charges)
J.52.14 Document number
J.52.15 Arresting agency NCIC code
J.52.16 Registrant information
J.52.17 CDC Number
#11..
- 313 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-108
J.52.18 FBI Number
J.52.19 CII Number
J.52.20 GPD's NCIC code
J.53
If problems exist in determining the correct match for the inmate being processed, JMS shall force alert messages to the terminals used by the Identification Unit and the Detention booking Officers where the inmate is currently being housed.

J.54
JMS will inform detention processing once a booking has been cleared by identification via messaging and printing the inmate’s name, Identification number and booking ID number at the detention supervisor’s position
J.55 JMS shall display summary of completed and pending identification requests J.56 JMS will rely upon RMS Master Name index (MNI) files for initial identification match criteria J.57
MNI match criteria shall result in possible matches being presented in summary form to the user, with the most probable matches presented first, and other possible matches presented in descending order of probability
J.58 Local matches will automatically and non-destructively update inmate data J.59 if a search identifies a prior detention history, JMS shall display the following information:

J.59.1 Identification Number
J.59.2 Charge (or charges) for which the most recent prior detention was imposed J.59.3 Housing classification (or classifications)
J.59.4 Medical history - if specific user-defined medical conditions appear in the prior history J.59.5 Discipline record - for the most recent prior detention J.59.6 Special situations
#11..
- 314 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-109
J.60 JMS shall permanently store at least three color images for each arrestee per booking, each with a description attached
J.61 JMS shall automatically associate all images with a specified inmate's file, and store the date and time at which it was recorded with the image
J.62 Users shall be able to retrieve and/or print any mug shots associated with a present or past inmate's record (or with any other person whose photograph is in the system for identification purposes) J.63 JMS shall also provide the user with the capability to generate a photo-lineup of up to six mug shots with the following capabilities:

J.63.1 Ability to prepare montage images of subjects with similar physical characteristics J.63.2 Ability to utilize images from local and stock (vendor provided) database files J.63.3 Ability to prepare montage in less than 2 seconds J.63.4 Random placement of images in photo line-up
J.64 JMS shall store color images of scars, marks, and tattoos for each arrestee J.65 JMS shall automatically associate all images of an inmate's scars, marks, and tattoos with his or her MNI, and store the date and time at which the images were recorded J.66 JMS shall differentiate images of scars, marks, and tattoos from mug shots, and shall require the user to attach a two-part description to each image of a scar, mark, or tattoo:

J.66.1
Class and location. Classes shall be scars, marks, or tattoos. Locations of scars, marks, and tattoos shall be selectable from a user-maintained list (e.g., right upper arm, back of right hand, left shoulder). The user shall be required to make brief free-form text entries to describe the locations of scars, marks, and tattoos not included in the user-maintained location list.

J.66.2
Type, subtype, and words. Common types and subtypes of scars, marks, and tattoos shall be selectable from a user-maintained list. The user shall be able to describe unusual types and subtypes in free-form text entries. A tattoo of words shall also be entered as free-form text. Standard entries to use validation tables.

J.67 JMS shall perform a check for outstanding wants and warrant for every booking and release J.68
For each remote (external) database (i.e., CLETS, NCIC) to be checked for wants and warrants, JMS shall generate a query in the format required by the database being checked, and shall route it to the target database. The response from the database shall be accepted in the format provided by the database, and converted to the format used by JMS
#11..
- 315 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-110
J.69 JMS shall include additional information about holds that may be placed on the inmate J.70 The system shall provide for including additional charges for an arrested person (i.e., rebook), relying on the RMS Warrants module (JMS imports all data entered within the RMS warrants module).

J.71
If a person being booked refuses to identify himself or herself, or an identity cannot be determined, the JMS shall accept "REFUSED (M)," "REFUSED (F)," "UNKNOWN (M)," or "UNKNOWN (F)" in the name field. "(M)" and "(F)" shall indicate the sex of the unidentified inmate. This entry shall cause JMS to generate a refused or unknown name with the next sequential number (e.g., REFUSED (M)-106)

CLASIFICATION REQUIREMENTS
J.72 To support classification of inmates, JMS shall make available the inmate's criminal history record.

J.73
JMS shall support classification interviews by displaying interview questions along with potential responses (where they can be determined) and text-entry fields for narrative information (to supplement predetermined answers, or for questions with open-ended answers). The system allows for the following information entry:

J.73.1 Current charge (or charges) for assault felony (or felonies), including attempts - code section selected from a user-maintained list
J.73.2 Convictions for prior assault felonies - code section (or sections) selected from a usermaintained list J.73.3 Current charge (or charges) for sex offense (or offenses), including attempts - code section selected from a user- maintained list
J.73.4 Convictions for prior sex offenses - code section (or sections) selected from a user-maintained list
J.73.5 Escapes from medium- and maximum-security facilities, including attempts - facility (or facilities), date (or dates)
J.73.6 Institutional behavior problems - type (or types) selected from a user-maintained list, detention facility, date (or dates) or, for numerous problems, number of episodes and range of dates J.73.7 Felony convictions in the past five years, including those for nonviolent crimes J.73.8 Sentencing status - all cases resolved, additional cases pending J.73.9 Most recent incarceration - location, release date J.73.10 Previous state or federal prison commitments and level, including California Youth Authority - locations, time spans
#11..
- 316 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-111
J.73.11 Current probation status - type, probation officer's name J.73.12 Parole status - parole office, parole officer's name J.73.13 Gang affiliation - name of gang, street/prison, membership status (active, associate, former), length of time in the gang, gang moniker
J.73.14 Enemies - name (or names) of known enemies in custody, current housing location of enemies J.73.15 Status as informant, witness, or recipient of protective custody - reason, location, agency, agency contact, confirmed/unconfirmed
J.73.16 Gender identity (M, F, M-F, F-M)
J.73.17 Other special housing requirements - youthful appearing, has been assaulted, elderly, other J.73.18 Current medical problems - cardiac, respiratory, other; if under treatment, physician, physician's telephone number (with area code)
J.73.19 Currently taking medication - type (or types), required while in detention, inmate supplied J.73.20 Psychiatric/emotional problems - type; if under treatment, therapist/ counselor, therapist/ counselor's telephone number (with area code)
J.73.21 Suicide attempts - when, method, current suicidal feelings J.73.22 Allergies
J.73.23 Physical handicaps - type, restricted access, medication required, subject to victimization J.73.24 Drug/alcohol abuse - type (or types) selected from user-maintained list, injected, length of use, most recent use
J.73.25 Special identifiers - selected from a user-defined list (e.g., career criminal, child abuse offender, child abuse victim)
J.73.26 Comments - any additional information entered as free-form text J.74 Based on the information input by the classification interviewer, JMS shall use an algorithm to generate a recommended classification code
#11..
- 317 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-112
J.75 The system shall set special handling alerts
J.76 The classification recommendation is subject to supervisor-approved change J.77 JMS shall identify unoccupied housing locations which have been pre-designated to be acceptable for the particular inmate’s classification code and display a list of available beds J.78
Before accepting a housing location, JMS shall check inmate records for the housing location against the inmate(s) to be housed for any restrictions for “keep separate”, co-defendant(s), gang restrictions, etc. and display an alert message indicating the restriction reason J.79
If the classification officer chooses to place an inmate in a location deemed unsuitable by JMS, the system must allow for an explanation for over-ride field (free form text narrative), subject to supervisory approval
J.80 JMS shall accept an unlimited number of inmate reclassifications J.81 JMS shall also accept an unlimited number of actions to rehouse inmates as required by reclassifications
J.82 JMS shall maintain a housing history on each inmate and shall update RMS MNI with associate information based upon proximate inmate population
J.83 JMS shall maintain an audit trail of all classification and reclassification actions J.84 The system should have the ability to track all inmate movement (virtually every movement of a prisoner, regardless of how slight)
J.85 JMS shall generate reports designed to evaluate the effectiveness of the Department's classification activities. These shall include the following:

J.85.1 Monthly list of inmates requiring reclassifications J.85.2 Monthly summary of vacancies
J.85.3 Daily report of all major disciplinary actions
J.85.4 Discipline summary
J.85.5 initial classification delay summary report
J.85.6 Reclassification delay summary report
#11..
- 318 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-113
J.85.7 initial and reclassification delay summary report J.85.8 Classification override summary
J.85.9 Classification Levels by housing
J.86 JMS shall provide full CLETS integration accessible from any RMS/JMS workstation J.87 JMS shall be interfaced with LiveScan for all fingerprint exchanges to/from CAL ID

HOUSING REQUIREMENTS
J.88 JMS shall provide the capability to record information on all special situations involving any inmate. Typical information to be collected shall include:

J.88.1 All information available in the RMS AFR incident/arrest reporting modules.

J.88.2 Inmate (or inmates) involved - name and Identification number (if several inmates are involved, the incident will be recorded in all their booking records).

J.88.3 Incident types that are unique to the jail (i.e., medical, psychiatric, violent behavior, criminal act, other disciplinary matter, refusal to accept a meal, refusal to accept medicine, telephone call, other) J.89
The system shall determine which inmates are scheduled for court appearances; medical, dental, and psychiatric appointments; work furlough; and work release programs each day, and shall prepare lists, which are organized by unit (or house) and/or cell or bed assignment. These lists shall be printed out in each detention facility on a daily basis at 6:00 AM (or at another user-selectable time). The list for each unit, module and/or cell or bed assignment shall show:

J.89.1 Inmate's name
J.89.2 Identification number
J.89.3 Destination (court, clinic, work furlough location, work release crew) J.89.4 Start time of inmate's activity - appearance, appointment, departure (date, time) J.89.5 End time of inmate's activity - returns of work furlough participant only (date, time) #11..
- 319 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-114
J.89.6 Holds and charges - court appearances only
J.89.7 Document number (or numbers) - court appearances only J.90 JMS shall prepare lists of all inmates scheduled for court appearances, organized by court and showing the following
J.90.1 Inmate's name - last, first, middle, suffix
J.90.2 Special handling alert (or alerts), if any - escape risk, combative, suicide risk, other at risk from enemies, high-profile
J.90.3 Classification code
J.90.4 Date of birth
J.90.5 Sex
J.90.6 Identification number
J.90.7 Booking date
J.90.8 Arresting agency
J.90.9 Bail amount
J.90.10 Housing location - unit (or house), module and/or cell or bed assignment J.90.11 Time of inmate's appearance
J.90.12 Charges
J.90.13 Holds
J.90.14 Document number (or numbers)
#11..
- 320 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-115
J.91 JMS shall be capable of displaying various entry fields based upon the type of visitor (e.g., attorney vs. spouse)
J.92 JMS shall have the capability to manage both personal and professional (e.g., attorney) visits.

Management shall include:

J.92.1 Maintaining lists of visitors authorized to see (or prohibited from seeing) each inmate J.92.2 Running want and warrant checks on visitors
J.93 JMS shall accept entry of the names of and identifying information for persons authorized to visit each inmate
J.94 Identifying information for each visitor and each inmate he or she will visit shall be user-defined, and shall typically include:

J.94.1 Name - last, first, middle, suffix
J.94.2 Name of firm (professional visits only)
J.94.2.1 CAL BAR Card Number (professional visits only) J.94.3 Address - street number, direction, street name, street type, apartment number, city, state, zip code
J.94.4 Telephone number (with area code)
J.94.5 Name of inmate to be visited - last, first, middle, suffix J.94.6 Identification number
J.94.7 Housing location - unit (or house), module and/or cell or bed assignment J.94.8 Relationship - personal: specific relationship, professional (selected from a user-maintained list)
J.94.9 Date of birth
J.94.10 Social Security number
#11..
- 321 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-116
J.94.11 Passport or VISA
J.94.12 Driver's license number and state
J.94.13 Date authorized
J.94.14 Dept. ID of the person authorizing visits
J.94.15 Access level - personal visits: specific facility at which person to be visited is housed; professional visits: one or more specified facilities; contact or non-contact visits J.95 The system shall also alert the user to requests for visits by restricted persons J.96 The system shall produce a visitor tracking report for those visitors identified by the user or to track all visitors to a particular inmate
J.97 JMS shall allow for free-form narrative text entries in either the inmate’s record or the Visitor Tracking Records
J.98 JMS shall assist the staffs of the detention facilities in selecting inmates to serve as inmate workers, and in managing them
J.99 JMS shall identify inmates whose classifications indicate that they are potentially suitable for employment as inmate workers
J.100 JMS shall prohibit overriding the exclusion of inmates with unsuitable classification codes from the inmate workers list
J.101 JMS shall also find suitable housing for inmate workers J.102 The system's inmate worker management capabilities shall include:

J.102.1 Keeping track of inmate workers' assignments and schedules J.102.2 Calculating each inmate’s accrual of total community service hours served J.102.3 Tracking each inmate worker's job performance and discipline problems J.102.4 Providing input to calculation of potential sentence reductions #11..
- 322 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-117
J.103
JMS shall provide inmate worker officers (and other inmate worker supervisors) the capability to input lists of job assignments for inmate workers, and to schedule the inmate labor necessary to fulfill those assignments. Scheduling shall allow for staffing inmate worker positions 24 hours a day, seven days a week
J.104 JMS shall print an inmate workers status list
J.105 Report summary for single or group of inmates
J.106 JMS shall have the capability to determine and accumulate the cost associated with housing and/or controlling inmates who are incarcerated for agencies other than GPD.

J.107 The system shall determine which inmates are being housed on a reimbursable basis and will store the rate per day for each inmate for each external agency J.108 JMS shall generate a monthly report identifying for each external agency:

J.108.1 Names of inmates housed and/or controlled during reporting period J.108.2 Identification numbers
J.108.3 Start and end dates of each inmate's incarceration and/or control period J.108.4 Daily charge for housing and/or controlling each inmate J.108.5 Special charges, if any, itemized by date and type for each inmate (for example, transportation charges)
J.108.6 Total charges and offsets for housing and/or controlling each inmate during the reporting period
J.108.7 Total charges and offsets for housing and/or controlling all inmates during the reporting period

TRANSPORTATION REQUIREMENTS
J.109
The system shall determine which inmates are scheduled for court appearances; medical, dental, and psychiatric appointments; transportation to special destinations, and transfers from one detention facility to another, and shall prepare daily transportation lists. The list shall show all inmates that are to be transported to each specific destination. The inmates going to each destination shall be listed alphabetically by last name
#11..
- 323 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-118
J.110 The system shall accommodate special transportation requests and will capture the following information:

J.110.1 Identity of vehicle(s)
J.110.2 Departure location - standard locations: selected from a user-maintained list; special locations:
entered as free-form text (can include out-of-state locations) J.110.3 Departure odometer reading - edited against the immediately previous entry for this vehicle J.110.4 Departure date
J.110.5 Planned departure time - hours, minutes
J.110.6 Arrival location - standard locations: selected from a user-maintained list; special locations:
entered as free-form text (can include out-of-state locations) J.110.7 Arrival odometer reading - edited against the immediately previous entry J.110.8 Arrival date
J.110.9 Estimated travel time - hours, minutes
J.110.10 Number of inmates to be transported
J.110.11 Number of other persons to be transported (if any, excluding the driver) J.110.12 Special instructions and other comments - selected from a user-maintained list; or entered as free-form text
J.110.13 Dept. ID of driver
J.111 JMS will immediately route priority messages to transportation detail employees upon any schedule change
J.112 JMS shall maintain a log of each transportation run. Each record shall typically contain the following information:

J.112.1 Identity of vehicle
#11..
- 324 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-119
J.112.2 Departure location
J.112.3 Odometer reading - edited against the immediately previous entry for this vehicle J.112.4 Departure date
J.112.5 Departure time - hours, minutes
J.112.6 Arrival location
J.112.7 Arrival odometer reading - edited against the immediately previous entry J.112.8 Arrival date
J.112.9 Arrival time - hours, minutes
J.112.10 Number of inmates transported
J.112.11 Number of other persons transported
J.112.12 Special instructions and other comments
J.112.13 Driver's comments
J.112.14 Dept. ID of driver
J.112.15 Dept. ID(s) of other Department personnel, if any, assigned to the run for official reasons (e.g., to provide security)
J.113 Transportation entries should be input through the following:

J.113.1 Preparation of daily transportation lists
J.113.2 Input of a special transportation request
#11..
- 325 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-120
J.114
JMS shall maintain a list of all scheduled runs (from daily transportation lists and change messages), and shall print out a list of runs on the previous day for which run information has not been entered
J.115 Description of reimbursable runs
J.116 Vehicle log
J.117 Transportation summary to include the following:

J.117.1 Total number of trips
J.117.2 Number of inmates transported
J.117.3 Number of other persons transported
J.117.4 Number of miles traveled

MEDICAL SERVICES REQUIREMENTS
J.118 JMS shall enable the creation of a medical record for all established inmates (regardless of whether there are any identifiable medical problems)
J.119 JMS will integrate with the State of California’s Health and Human Services application J.120 JMS shall provide for the scheduling, rescheduling, and cancellation of appointments with both staff and outside practitioners.

J.121
After an inmate has been seen by a practitioner, JMS shall create and maintain a chart as part of the inmate's medical record. For the initial and each subsequent visit, the inmate's chart contains the following types of information:

J.121.1 Name
J.121.2 Identification number
J.121.3 Housing location - unit (or house) and cell
J.121.4 Practitioner seen - name of physician, dentist, nurse seen #11..
- 326 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-121
J.121.5 Location, if outside the detention facility - street number, direction, street name, street type, suite number, city, zip code
J.121.6 Telephone number (with area code), if outside the detention facility J.121.7 Inmate's complaint (or complaints)
J.121.8 Vital signs and other physical examination findings J.121.9 Diagnosis
J.121.9.1 Treatment plan
J.121.9.2 Medication (or medications)
J.121.9.3 Special diet - type, start date, stop date
J.121.10 Laboratory tests and X-rays
J.121.11 Follow-up chart review
J.121.12 Hospitalization, if required
J.121.13 Institution to which inmate is to be transferred, method of transportation (ambulance company, other)
J.121.14 Follow-up appointment (or appointments) - for each: date; practitioner, if known; location J.121.15 Billing costs for internal expenses
J.121.16 Other information, as appropriate
GPD JMS Reporting
J.122 JMS shall also prepare and automatically print the following reports at a user-defined interval:
#11..
- 327 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-122
J.122.1 Recap of jail statistics
J.122.2 Unit list - name sequence
J.122.3 Unit list - name within cell sequence
J.122.4 Unit list - identification number sequence
J.122.5 Inmate housing location, by hour
J.122.6 Inmate - by location with charges
J.122.7 Inmate master list
J.122.8 Reproduction of inmate roster from specification J.122.9
Daily Activity Log (Including prior period arrests, detentions, releases, incidents, dispositions, and user defined fields. For each activity, the report identifies the officer/user-ID, date/time of activity, and notes.)
J.122.10 Inmate master list
J.122.11 Reproduction of inmate roster from specification GPD JMS Interfaces
J.123 JMS must be integrated with the following two systems:

J.123.1
Los Angeles Regional Crime Information System (LARCIS): The Data Systems Bureau houses the Los Angeles Regional Crime Information System ((LARCIS) that contains records of all incidents or events resulting in a report. Since the late 1990's LARCIS has served as the LASD RMS.

LARCIS is an in-house designed RMS that is Oracle-based and housed on an HP-UX Superdome.

J.123.2
Automated Justice Information System (AJIS): The LA Sheriff's Department uses an internally-developed solution called AJIS to managae the information system requirements of the jail.

Other ancillary systems are used to facilitate the agency's ability to report on jail activity. The AJIS solution is in the process of being replaced by JIMS from Syscon Justice Systems. #11..
- 328 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-123
APCO Unified CAD

CALL HANDLING / CAD EVENT CREATION
K.1.0 The CAD will support an E-911 interface to import ANI/ALI and other specific call information into the system.

K.1.1 The CAD will import a call for service generated on a remote workstation and mobile devices.

K.1.2 The CAD will allow for multiple data entry and function access (i.e.. Command Line, Drag-NDrop, Right Mouse Click, map dispatching and Function Keys).

CAD Incident/Event Types
K.1.3 The CAD will allow for system administrator-defined CAD incident types or nature codes.

K.1.4 The CAD will allow system users to modify the incident type and provide new/updated response plan information/recommendations based on the new incident type.

K.1.5 The CAD will provide the capability to create an event, assign a unit, and close the event with a disposition without going through the dispatch process steps.

K.1.6 The CAD will allow entry of scheduled recurring events.

Update Call for Service Event Data
K.1.7 The CAD will enable a user to enter supplemental (new) information into the call for service event record.

K.1.8 The CAD will display a notification of the event update at each appropriate CAD position whenever an event record is updated, as determined by the system's configuration.

K.1.9 The CAD will create an automatic time/date stamp for every transaction related to an event and store the responsible user ID, workstation ID and the nature of the change.

K.1.10 The CAD will add audit records to the event history or store audit records in the CAD system's audit log file.

K.1.11 The CAD will create a permanent audit trail for all information recorded related to an event.

K.1.12 The CAD will support ease of entry for supplemental event information and changes to existing event information.
#11..
- 329 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-124
K.1.13 The CAD will allow the user to display a supplemental data entry screen by specifying either the event number or a unit assigned to the event.

K.1.14 The CAD will allow the user to display a data entry screen to change information previously entered into a CAD event by specifying either the event number or a unit assigned to the event.

K.1.15 The CAD will allow the user to display a data entry screen to change information previously entered into a CAD event by specifying either the event number or a unit assigned to the event (noting that this functionality would not apply to closed CAD events/units).

K.1.16 The CAD will provide agency-definable visual and audible alerts to notify CAD system users (including users of systems interfaced to CAD such as Mobile Data Computers), of event changes and supplemental information.

K.1.17 The CAD will document all changes and supplemental information in the event history.

K.1.18 The CAD will allow the user to update or change a unit’s most recent event by entering the unit’s identification or any unit that is currently assigned.

K.1.19 The CAD system will allow the department to use agency-definable case numbers and allow numbers to be rolled monthly or yearly.

K.1.20 The CAD system will allow various file types to be attached to CAD incidents and viewed.

K.1.21 The CAD system will provide function key access for frequently used screens and functions (Traffic Stops, Unit Indicated Incidents, New Call Screens, etc.), which can be set by the agency.

K.1.22 The CAD system will include a remarks field for user-defined text and characters (including the ID of those who request report numbers, transportation data including purpose, arrival, and date/time, etc.).

Utilize Incident Disposition
K.1.23 The CAD will allow the user to enter one or more dispositions, as dictated by agency policy, when a CAD event is closed.

K.1.24 The CAD will allow a CAD event to be closed OR placed back in pending if no remaining resources are assigned to the event.

K.1.25 The CAD will allow the system administrator to define disposition codes.

K.1.26 The CAD will allow a mobile unit to enter one or more dispositions when clearing from a CAD event.

Assign Incident Classification and Priority
K.1.27 The CAD will enable CAD users to select the appropriate incident/event type from a pre-defined list of codes based upon information received from reporting party. #11..
- 330 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-125
K.1.28 The CAD will provide the ability to generate a CFS event with only the location and incident type code entered.

K.1.29 The CAD will allow the user to utilize incident screening menus, such as a drop-down menu, to assist in determining the appropriate incident/event type code.

K.1.30 The CAD will allow the user to interrupt the CFS event creation process and save entered information, sometimes known as call stacking, to process a higher priority incoming incident.

K.1.31 The CAD will provide a warning notification of the held CFS event generated at an administratorconfigured time. Any position can review current CFS events, retrieve a partial CFS record, and complete the CFS event entry.

K.1.31.1 Upon the entry of user-defined high-priority type codes (i.e., homicide, shooting), all on-duty dispatchers will receive an audible and visual alert.

Check for Duplicate Incidents
K.1.32 The CAD will identify during the creation of a CFS event whether the event is a potential duplicate of an active CAD event or an event recently closed; and notify the call taker of the results (noting that closed CFS will not be presented as duplicates).

K.1.33 The CAD will present the user with the following information for each potential duplicate event if potential duplicates are located: Incident ID, Incident Type, Incident Location, and Status.

K.1.34 The CAD will allow the user the ability to create a new CFS event and link the event to the primary event record; or, to merge any new information contained in a duplicate event into the main event record associated with the identified duplicate CAD event.

Location Verification
K.1.35 The CAD will validate all streets, intersections and address ranges and resolve ambiguities, while accounting for spelling variations and duplications.

K.1.36 The CAD will validate entered incident addresses against the CAD geofile, using ESRI source data.

K.1.37 The CAD will relate latitude, longitude, altitude (X/Y/Z) coordinates to an actual address and display on map.

K.1.38 The CAD will provide the ability to enter a unique building and unit number to clearly identify the location.

K.1.38.1 The location may be manually entered without validation, subject to validation prior to call closure.

K.1.39 The CAD will provide various suggestions to assist users in selecting accurate incident locations. #11..
- 331 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-126
K.1.40 The CAD will allow each address or commonplace name to have an unlimited number of alias names that will appear on the calltaker's screen.

K.1.41 The CAD will organize the display of possible address matches in an ergonomic, easily understood manner that aids users in identifying valid incident locations.

K.1.42 The CAD will allow authorized users to configure their tactical map display to show jurisdictional boundaries (e.g. town boundaries) and to display potential valid incident locations by jurisdiction.

K.1.43 The CAD will provide the ability to enter a partial street name, with a minimum number of characters, and be presented with a list of possible matches to pick from for an exact match.

K.1.44 The CAD will provide the ability to enter a misspelled street name and be presented with a list of possible matches based on SOUNDEX and/or other methodology.

K.1.45 The CAD will provide the ability to enter an incorrect street address for a correct street name and be presented with a list of valid ranges.

K.1.46 The CAD will provide the ability to enter common street alias and abbreviations instead of the actual street name.

K.1.47 The CAD will provide the ability to display the incident location in relation to other active incidents on the system’s tactical map display during the CAD event entry process.

K.1.48 The CAD will display premise warnings, hazards or alerts on the location of the incident.

Involved Person or Vehicle Information
K.1.49 The CAD will display prior incidents that occurred at an incident's location within a configurable period of time.

K.1.50 The CAD will initiate an automatic query, upon entry of information about an individual associated with an event, using the following guidelines at a minimum: 1) If the name only is known, then a name query should be initiated to local files capable of performing a lookup based only on a name. 2) If the minimum required fields contain enough data for state and federal queries, then the system should initiate queries to local, state and federal databases.

K.1.51 The CAD will return all responses from local, state, and federal databases to the data entry originator.

K.1.52 The CAD will bring positive responses (e.g. possible “hits”) that require a review by the originator to the attention of the originator through the use of audible and visual indicators.

K.1.53 Positive “hits” will appear on all CAD workstations in different color than non-hit returns.

K.1.54 The CAD will initiate an automatic query to local, state and federal databases, upon entry of information about a vehicle associated with an event, using the following guidelines at a minimum: 1) License plate number and license plate state or 2) VIN. #11..
- 332 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-127
K.1.55 The CAD will default the state to CA for all inquiries.

Premise Hazards and Previous History
K.1.56 The CAD Premise Hazard and Previous History file will be capable of storing information of interest to responders including, but not limited to:

K.1.56.1 Hazardous materials stored at the location
K.1.56.2 Firearms kept at the location
K.1.57 AND Information specific to individuals at the location, including, but not limited to:

K.1.57.1 Warrants on file
K.1.57.2 Serious medical information
K.1.57.3 Impairments
K.1.57.4 Potential dangers to first responders
K.1.58 AND Information specific to the address, including, but not limited to:

K.1.58.1 Entry codes
K.1.58.2 Knox Box information
K.1.59 The CAD will enable all required data for direct input, to be uploaded, or to be loaded via a live interface from RMS(s).

CAD Event Creation
K.1.60 The CAD will support the creation of new CFS events by either call takers or dispatchers depending on the source of the event information.

Determine Response Agency and Service Area
#11..
- 333 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-128
K.1.61 The CAD will assess an event’s location and nature code, then use the system’s geofile to identify the appropriate service agency or agencies that need to handle the event.

K.1.62 The CAD will use the service agency and response to notify the appropriate dispatcher(s) that they must process a CAD event.

CAD Event Routing
K.1.63 The CAD will allow configuration of any CAD workstation for Call Taking and/or Dispatching Functions.

K.1.64 The CAD will examine the location, event type and response plans (when dedicated dispatch positions are in operation) to route the CFS event to one or more dispatch positions as the CFS event entry is being performed by a call taker.

K.2 DISPATCH SUPPORT
Response Plans
K.2.1 The CAD will allow for dynamic and fixed/static response plans.

K.2.2 The CAD will allow for assignment to be by officer, role, capability and equipment.

K.2.3 The CAD will allow for the use of resource groups made up of individual units.

K.2.4 The CAD will allow for the use of AVL systems for selecting units.

K.2.5 The CAD will support multiple agency response plans.

K.2.6 The CAD will allow for unit assignment based on time or distance to the incident.

K.2.7 The CAD will allow for adjustable plans that are based on time of day or day of week.

Unit Rotation
K.2.8 The CAD will allow for customization based on the needs of the agency (e.g. incident address, response type, assignment, resources required, unit-on-task-time, unit utilization, time of day and proximity if you have multiple available units with the capability required).

K.2.9 The CAD will make unit response recommendations based on the configuration of rules defined by an agency, and unit class.
#11..
- 334 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-129
Be On the Look-Out / Attempt to Locate
K.2.10 The CAD will support creation and distribution of any BOLO entered into the system.

K.2.11 The CAD will provide a BOLO structure to include all necessary information such as the nature of the BOLO, priority, date, range of effectiveness, subject and/or vehicle information, hazard information, and contact information.

K.2.12 The CAD will allow narrative fields for additional information.

K.2.13 The CAD will provide the means for BOLO information to be easily searchable, printable, and have the ability to automatically populate on an incident sheet referencing any particular name, address, or vehicle information.

K.2.14 The CAD will flag the field (automatically) with configurable visual and audible alerts.

K.2.15 The CAD will support a workflow record for initial BOLO creation and any additional edits.

Dispatch Units
K.2.16 The CAD will have the ability to assign one incident number to each unit responding to the incident.

K.2.17 The CAD will capture every time stamp associated with each unit’s response and status change related to the incident.

K.2.18 The CAD will capture all status changes and their times for statistical and research purposes (e.g. out of service versus in service to calculate “lost unit hours”).

Resource Alerting for Units
K.2.19 The CAD will alert units via MDC and handheld devices and tablets.

K.2.20 The CAD will support alphanumeric paging via TAP, WCTP, SMTP, and SNPP.

K.2.21 The CAD will support sending SMS messages either directly via cellular modem or using a common carrier’s SMTP interface.

K.2.22 The CAD includes the ability to send a copy of an event to all units without assigning them to the event with a single command.

K.3 RESOURCE / UNIT MANAGEMENT
#11..
- 335 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-130
Rostering
K.3.1 The CAD will provide the capability to create rosters (i.e. assign personnel to a vehicle or position to facilitate on/off duty transactions).

K.3.2 The CAD will allow the dispatcher to adjust the rosters and/or assignments (i.e. on-the-fly, during shifts, and above normal complements).

K.3.3 The CAD will contain a 2-way, real-time interface to auto populate roster information in CAD.

Scheduling
K.3.4 The CAD will provide scheduling capabilities to include pre-assignment of personnel to shifts, districts, and beats.

K.3.5 The CAD will allow the dispatcher, with proper permissions, to make adjustments to scheduling onthe-fly and/or during shifts.

K.3.6 The CAD allows dispatchers to retrieve historic rosters within a user-defined date/time range.

Mileage Tracking
K.3.7 The CAD will capture beginning and ending mileage for individual transports.

K.3.8 The CAD will provide a method of integration with an AVL system for increased accuracy and efficiency.

K.3.9 The CAD will use GIS/mapping to supplement driving directions based on shortest route beginning and ending address locations, with regard to environmental factors such as time of day, weather conditions, train schedules, and road/bridge blockages.

K.3.10 The CAD will provide the ability for an authorized user to manually override an entry by a dispatcher or supervisor.

K.3.11 The CAD will record the overridden information in an audit log.

K.4 CALL / INCIDENT / EVENT MANAGEMENT
Display of Incident/Event Data
K.4.1 The CAD will display CFS event data on the CAD monitor after being selected by the dispatcher.

All CFS event data will be accessible to the dispatcher. #11..
- 336 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-131
K.4.2 The CAD will enable Windows tabs to be used to allow the dispatcher to select supplemental history about the incident (e.g. premises history, past event history, hazards, persons of interest).

K.4.3 The CAD will display (automatically) updates to the CFS event for the dispatcher.

K.4.4 The CAD will provide updated information that is easily discernible from the previously read data (e.g. newest information on the top, different font/color text).

K.4.5 The CAD will present an audible and/or visual indication to the dispatcher when a CFS event is updated by another source such as a call taker, another dispatcher, or a field unit.

K.4.6 The CAD will provide, upon receipt of an update, a method of ease, such as an ‘Update’ button, for the dispatcher to retrieve the CFS event that has been updated.

K.4.7 The CAD will remove CFS events as they are closed by the dispatcher from the CFS event display, without additional interaction from the dispatcher.

Assign Units
K.4.8 The CAD will allow the assignment of units by using drag-and-drop and point-and-click pull-down menus or command line.

K.4.9 The CAD will re-queue the CFS that has had all units removed, but has not been handled.

K.4.10 The CAD will recommend a unit that is unavailable only if SOP permits units to be pre-empted for a higher priority event.

K.4.11 The CAD will provide the ability to assign one or more units to an incident with a single command.

K.4.12 The CAD will provide the ability to dynamically, and without user intervention, change the unit recommendation if relevant incident information changes (i.e. type, location).

K.4.13 The CAD will provide the ability to notify users that the unit recommendation has changed.

K.4.14 The CAD will provide the ability to cancel a unit from an assignment: If the cancelled unit is the only unit assigned, then the CFS will be returned to the pending event queue.

K.4.15 The CAD will provide the ability to hold a CFS event for a specific unit.

K.4.16 The CAD will allow the dispatcher to override the system recommended units and assign other units.

K.4.17 The CAD will allow the dispatcher to assign any valid field unit to an incident even if that unit is not currently logged on to the system.
#11..
- 337 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-132
K.4.18 The CAD will notify the dispatcher and confirm that the correct unit has been assigned if a unit assigned to an incident is not logged on the system.

Update Incident Data
K.4.19 The CAD will log the following information for all entries into the CFS event: date, time, user ID (or note if action was system generated), position (terminal) ID, action performed, and any notes associated with action.

K.4.20 The CAD will allow, at any time, additional incident information to be added to the CFS event prior to incident closure.

K.4.21 The CAD will allow the user to display the added comments in reverse chronological order.

K.4.22 The CAD will provide the user the option of specifying the CFS event to update by entering the call sign of any assigned unit or by entering the incident number.

K.4.23 The CAD will permit multiple users, including MDC-equipped field resources, the ability to simultaneously update information to the CFS event.

K.4.24 The CAD will provide the ability for one or more CAD users to simultaneously add incident information to an active CFS event.

Assign RMS Incident / Case Number
K.4.25 The CAD includes an interface to an RMS to allow the transfer and tracking of incident data.

K.4.26 The CAD will provide the ability to transfer the incident data to the RMS at a set time (incident closure) or at dispatcher discretion based upon the field unit’s needs.

K.4.27 The CAD will coordinate the assignment of RMS incident/case numbers through a list maintained in the CAD system.

K.4.28 The CAD will provide the ability for the dispatcher to retrieve the RMS incident number at any point during the event or after the incident has been closed.

Transfer Incident Data To/From the RMS
K.4.29 The CAD will auto-populate necessary CAD data into RMS via appropriate interface.

K.4.30 The CAD will automatically query a different RMS system via appropriate interface (in a best-ofbreed environment).

Scheduled Events
#11..
- 338 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-133
K.4.31 The CAD will provide the ability to automatically schedule the CFS event for future dispatch.

K.4.32 The CAD will be capable of displaying a list of all scheduled events.

K.4.33 The CAD will provide the ability for authorized users to activate a scheduled event at any time.

K.4.34 The CAD will send a message to the appropriate users when the scheduled activity occurs.

K.4.35 The CAD will support location override for scheduled incidents.

Secondary Incident Location
K.4.36 The CAD will provide the ability to note responding units have arrived “in staging,” which may be a remote secondary address associated with the primary incident location.

K.4.37 The CAD will provide the ability to change a unit’s location from the primary address to a secondary address without clearing the unit from the incident or CAD record.

K.4.38 The CAD will log a date/time stamped record of the change in the CFS event.

Single Discipline Incident to a Combined Discipline Incident K.4.39 The CAD will provide the ability to add another agency’s resources to a CFS event.

K.4.40 The CAD will provide the ability to assign an agency specific incident/event number to the CFS event.

K.4.41 The CAD will provide the ability to link added agency records with the initial CFS event.

K.4.42 The CAD will provide the ability to share incident information across multiple linked records.

K.4.43 The CAD will provide the ability to track the added resources for the duration of the incident.

Timers
K.4.44 The CAD will have, and allow configuration of, multiple timers based on unit status and CAD incident type, such as time on a particular call, time since last check-in, and time at the hospital or jail. #11..
- 339 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-134
K.4.45 Ability to run status command (to view/monitor different dispatch groups).

K.4.46 The CAD will have, and allow configuration of, timers for CAD system events, such as a priority 1 call overdue to be dispatched.

K.4.47 The CAD will allow for operators to manually place a timer alert on a CFS or a unit.

K.4.48 The CAD will minimally include “down to the second” timestamps (e.g. hhhh/mm/ss).

K.4.49 The CAD will allow configurable timers (i.e. ‘hh:mm:ss’, ‘mm:ss’, or ‘ss’).

K.4.50 The CAD will be equipped with predefined timers that can be configured by the system administrator.

K.4.51 The CAD will provide the ability for the system administrator to create customized definable timers.

K.4.51.1 The CAD will record timer activity to the CFS event log.

K.4.51.2 The CAD will produce both visual and audible alerts to the dispatcher when a timer is triggered.

K.5 SUPPLEMENTAL RESOURCE REQUEST AND TRACKING
Supplemental Resources
K.5.1 The CAD will be able to store, and easily retrieve, a file for standardized and ad hoc supplemental resources that may be recalled and requested as needed for services not available from the public safety agencies.

K.5.2 The CAD will make request and “dispatch” of said resources on the basis of the unique type of service needed, the geographic proximity to the site of the needed service, or a rotation of the unique service providers of a given type—or, a combination of methods.

K.5.3 The CAD will be able to create a unique or supplemental unit designation in real time.

K.5.4 The CAD will be able to record the activities of unique or supplemental units in the same manner in which agency response units are tracked and their activities recorded.

K.5.5 The CAD will allow for agency-configurable non-agency units to be recommended, such as the closest towing company recommendation when a unit is dispatched to an accident event type. The recommendation will take into account the rotation of towing companies. #11..
- 340 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-135
K.5.6 The CAD will store, and provide for easy retrieval, a list of authorized providers of unique or supplemental supplies or services
K.5.7 The CAD will provide multiple sources of contact for each authorized vendor.

K.5.8 The CAD will be able to display the list of authorized service providers based upon geographical proximity to the site of need, by rotation, or by agency preference based upon contractual agreement.

K.5.9 The CAD will record the transactions that occur with supplemental or unique resources.

K.5.10 The CAD will provide the ability to create a record of the supplemental service request.

K.5.11 The CAD will accommodate selection from the provided list either at random, by geographic proximity to the site of need, or by rotation.

K.5.12 The CAD will trigger the next provider in the rotation, when selected by rotation and upon creation of the record
K.5.13 The CAD will process the rotation regardless of the requested resource’s ability to respond.

K.6 GEOFILE MAINTENANCE
K.6.1 The CAD will validate all locations entered into or processed by the CAD system against the CAD system’s geofile.

K.6.2 The CAD will provide an interactive, GUI-based address matching tool for assisting users to determine the location of incidents that do not have an exact geofile match for their initially-entered location.

K.6.3 The CAD will be capable of determining X/Y/Z coordinate values that represent the location of incidents whose locations have been validated.

K.6.4 The CAD will be capable of displaying coordinates anywhere on the map with mouse over.

K.6.5 The CAD will support coordinate-based operations including X/Y/Z, Lat/Lon, and USNG.

K.6.6 The CAD will make possible integration of the CAD system’s geofile with Global Positioning Satellite (GPS), AVL, and Automatic Person Location (APL) systems.

K.6.7 The CAD will support X/Y/Z coordinate-based geographic searches for such things as nearby hazardous materials, duplicate incidents, and premises information at or near an incident’s location.

K.6.8 The CAD will be capable of importing geographic boundary information (e.g. station boundaries, jurisdictional boundaries, reporting districts, response zones, neighborhoods, precincts) from GIS and other geographic data sources.
#11..
- 341 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-136
K.6.9 The CAD will be capable of importing topologically-structured street networks and other linear features (e.g. rivers, streams, utility right of ways, bus routes) from GIS and other geographic data sources.

K.6.10 The CAD will be capable of importing point data (e.g. landmarks, parcel address points, business locations, retail store address points, etc.) from GIS and other geographic data sources.

K.6.11 The CAD will be capable of importing other types of geographic data (e.g. park boundaries, rectified aerial photography, trailer parks, apartment complexes) from GIS and other geographic data sources.

K.6.12 The CAD will support parcel-level GIS information and use this information for address/location validation.

K.6.13 The CAD will support multiple layers of information; for example, the storage of building footprints, aerial photographs and other images (i.e. pictures of specific buildings) that are associated with specific areas and addresses.

K.6.14 The CAD will maintain the CAD system’s geofile while the system is live and operational.

K.6.15 The CAD meets i3 standards and functions in order to comply with NG9-1-1 requirements.

K.7 SECURITY
K.7.1 The CAD will employ data security measures that are compliant with applicable state and federal security standards.

K.7.2 The CAD will employ data encryption that meets CJIS security policy standards for any exchange or transmittal of data.

K.7.3 The CAD will provide appropriate safeguards to ensure that only authorized devices and users are allowed access to the CAD system and stored information.

K.7.4 The CAD will provide a security profile to control individual user access to the various modules, applications, functions, features, and data available within the CAD system.

K.7.5 The vendor's company and solution meets all FBI CJIS Security Policy requirements.

K.7.6 The CAD will validate each user’s credentials through a mandatory logon process before being granted access to any functions or data available within the CAD system.

K.7.7 The CAD will enable a user replacing an existing user to quickly log off the existing user and logon without the need to exit from CAD or re-start the CAD application (i.e. when two-factor authentication does not apply.)
K.7.8 The CAD will enable system administrators to create and maintain a centralized and indexed database containing information about each system user, including their unique user ID, password, #11..
- 342 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-137
contact information, and security profile.

K.7.9 The CAD will enable system administrators to define individual user access privileges and assign them to security groups.

K.7.10 The CAD will provide a method for authorized users to reset a user’s password.

K.7.11 The CAD will associate the user ID and workstation ID with all CAD system transactions, including data entry and report generation.

K.7.12 The CAD will limit access to the centralized user security database to only specifically authorized users.

K.7.13 The CAD will establish security profiles that are assigned to individual users or user groups based on personnel classifications (e.g. call taker, dispatcher, system administrator, supervisor).

K.7.14 The CAD will prohibit deletion of any data entered into a CFS event.

K.7.15 The CAD will provide application and module level security that enables certain users to access specific CAD system functions and application modules, while keeping other users from accessing these same functions and modules.

K.7.16 The CAD will provide data entry form security that enables certain users to access specific data entry forms, while keeping other users from accessing these same data entry forms.

K.7.17 The CAD will provide record type security that enables certain users to access specific CAD system record types, while keeping other users from accessing these same record types.

K.7.18 The CAD will provide transaction level security that enables certain users to access specific transaction types.

K.7.19 The CAD will provide data field level security that enables certain users to access specific CAD data fields, while keeping other users from accessing these same data fields.

K.7.20 The CAD will facilitate the use of unique user IDs and passwords to control CAD system access and privileges.

K.7.21 The CAD will provide a “single entry” to enable logons to multiple authorized systems that are available through the system (e.g. CAD, RMS, External and Internal Interfaces).

K.7.22 The ability to use Active Directory for using multiple domains.

K.7.23 The CAD will limit access to system functions and data by physical device (e.g. PCs, terminals), as well as by user ID.

K.7.24 The CAD will provide the ability to “lock out” a user after a system administrator defined number of failed attempted logons.
#11..
- 343 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-138
K.7.25 The CAD will provide the capability for individual user name change (e.g. getting married) and keep a link to historical data.

Logging
K.7.26 The CAD will include a transaction audit database that contains all system transactions and that includes the logon identification (i.e. user ID and workstation ID), date and time stamp, transaction type, contents before ID, and contents after the transaction completes.

K.7.27 The CAD will enable authorized system users to search the transaction audit database by date and time ranges, by application module, transaction type, specific tables and data fields within tables, specific data entry forms, individual users, user groups, workstation ID, and by various combinations of these factors.

K.7.28 The CAD will enable authorized system users to create formatted reports and/or export the results of transaction audit database queries and searches.

K.7.29 The CAD will prohibit any changes to the contents of the CAD transaction audit database.

K.7.30 The CAD transaction audit database will capture and store ALL system transactions.

Configuration
K.7.31 The CAD will enable authorized system administrators to configure the CAD system to meet the requirements of the department by creating and modifying CAD configuration parameters.

K.7.32 The CAD will enable authorized system administrators to modify CAD configuration parameters without the requirement for programmer or other support from the manufacturer of the CAD system.

K.7.33 The CAD Configuration will include functionality for table driven and directly modifiable functionality by authorized system administrators.

K.7.34 The CAD Configuration will include functionality for interactive, menu-driven, GUI-based tool that allows authorized administrators to easily update and modify parameters.

K.7.35 The CAD Configuration will allow system administrators to specify or modify the following:

K.7.35.1 Incident Types
K.7.35.2 Incident Priorities
K.7.35.3 Reporting District(s)
#11..
- 344 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-139
K.7.35.4 Beat(s)
K.7.35.5 Agencies
K.7.35.6 Type of Resources (color-coded text)
K.7.35.7 Dispatch Policies
K.7.35.8 Alerts/ Timers
K.7.35.9 Type of Dispositions
K.7.35.10 Case Number Formatting
K.7.35.11 Windows / Menus layout, color, font, attributes K.7.35.12 Map Display Zoom Levels
K.7.35.13 Display and functional characteristics of CAD system queues (i.e. pending, active, etc.) K.7.35.14 Display and functional characteristics of CAD system interfaces systems and gateways.

Table Maintenance
K.7.36 The CAD Table Maintenance will include CAD tables that are maintained using entry windows.

K.7.37 The CAD Table Maintenance will include CAD table maintenance entry windows that have context-sensitive, field-level help.

K.7.38 The CAD Table Maintenance will enable changes made to CAD tables to become immediately effective and shall not affect overall CAD system availability nor require any CAD system down time.

K.7.39 The CAD Table Maintenance will allow agencies to define additional data elements based on their operational requirements.

K.7.40 The CAD Table Maintenance will provide the ability for tables to be defined to support the maintenance of the following CAD objects:
#11..
- 345 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-140
K.7.40.1 Incident Types
K.7.40.2 Agencies
K.7.40.3 Disposition Codes
K.7.40.4 Commands
K.7.40.5 Hazards
K.7.40.6 Units
K.7.40.7 Unit statuses
K.7.40.8 Unit types
K.7.40.9 Vehicles
K.7.40.10 Service Types (i.e. police, animal control, etc) K.7.40.11 Response Plans
K.7.40.12 Personnel
K.7.40.13 Rosters
K.7.40.14 Messages (e.g. canned, scheduled)
K.7.40.15 Alerts/ Timers
K.7.40.16 Notifications
K.7.40.17 Equipment
#11..
- 346 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-141
CAD Catch-Up
K.7.41 The CAD will allow a CAD Catch-Up function due to interruption of CAD services.

K.7.42 The CAD will have the ability to manually open and create a CFS event sheet.

K.7.43 The CAD will have the ability to log the entering individual's information and time of entry.

K.7.44 The CAD will provide the ability for all information to be entered without any restrictions, and times/dates changed to reflect the actual time that notice of the CFS event was received.

K.7.45 The CAD will denote the manually-entered CFS event so there is a record that the CFS event was not entered when it was actually received.

K.7.46 The CAD will provide ability to manually designate the “starting” incident number (i.e. the last incident +1 for the starting number once the system is restarted).

K.7.47 The CAD will allow for simultaneous automatic and manual entry without degradation.

K.7.48 The CAD will include all the information in back entered records that a live incident/event sheet should require.

K.8 SYSTEM FUNCTIONS
Notifications
K.8.1 The CAD will enable the system administrator to define the rules for automatic CFS event notifications.

K.8.2 The CAD will provide the ability to create messages that are retained in the system and sent at prespecified times.

K.8.3 The CAD will allow the user to send and store messages to other users, groups, positions, or mobile devices.

K.8.4 The CAD will allow a message to be sent to multiple recipients and/or groups.

K.8.5 The CAD will log all sent messages.

K.8.6 The CAD will provide the ability to create and maintain automatic reminders of scheduled activities (e.g. radio tests).
#11..
- 347 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-142
Premises Information / Hazards
K.8.7 The CAD will provide the ability to enter a premises location by full address detail, cross street or latitude/longitude, and commonplace name.

K.8.8 The CAD will notify the dispatchers if non-safety-related information exists (wherein users may click to read the information), whereas safety/hazard information is automatically displayed and added to the call.

K.8.9 The CAD will provide the ability to capture, maintain or interface to specific premises information types for operators. (i.e. Hazard Materials, Handicap, Warrants, Unit Safety, Dangerous Animals, Sex Offenders, etc.)
K.8.10 The CAD will provide the ability to automatically create (i.e. upon closing of an incident) premises history based on pre-determined criteria.

K.8.11 The CAD will provide the ability for supervisors to delete premise information for a given address or location based on expiration date and/or time of record, with prompted review prior to deletion.

K.8.12 The CAD allows dispatch premise information to expire automatically at a pre-defined interval of time, but remain available for supervisory review (without being deleted).

K.8.13 The CAD will provide the ability to automatically embed premises information into the event history at the time the event is created.

K.8.14 The CAD will provide (or interface to) a “cautions” file to contain information pertaining to dangerous individuals possibly residing at that location or near proximity, and exceptional persons at the location, such as an emotionally disturbed person.

Dispatch Standard Operating Procedures
K.8.15 The CAD will provide the ability to store and easily retrieve SOPs for the PSAP.

K.8.16 The CAD will provide a SOP tool to prompt the user to ask for additional information, perform certain tasks, or relay critical information to responding units or other responders.

K.8.17 The CAD will provide a method where the retrieval of relevant SOPs are accessible from the CFS event information window and associated with the location, incident type, unit, or special skilled personnel responding.

CAD Workstation to CAD Workstation Messaging
K.8.18 The CAD will provide short messaging from one CAD workstation to another.

K.8.19 The CAD will include the ability to create message groups, whether they are dispatch workstations, mobile computers, groups within the PSAP, or other communications devices. #11..
- 348 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-143
K.8.20 The CAD will enable the system administrator to disable this function if desired on an agency basis.

K.8.21 The CAD will log all messages.

K.8.22 The CAD will provide the ability to create user definable “canned” messages for selection and distribution to other system users.

Narrative Field “Shorthand” / Auto Text
K.8.23 The CAD will provide the ability to recognize character patterns and automatically fill in expanded text.

K.8.24 The CAD will expand (automatically) the shorthand into a full description and save it into the narrative.

K.8.25 The CAD will allow the agency to add agency-specific shorthand terms and their expansions.

Multi-Agency / Multi-Jurisdictional Capability
K.8.26 The CAD will have the ability to create a CFS event for user-defined multi-agency events and route the CFS event to the appropriate agency dispatch position(s).

K.8.27 The CAD will have the ability to create a linked CFS event for each required agency and route the CFS event(s) to the appropriate dispatch positions when an event involves more than one agency.

K.8.28 The CAD will have the capacity to create a multi-jurisdictional response.

K.8.29 The CAD will provide the ability to create and route a CFS event for dispatch even though the event is in another jurisdiction.

Communications Supervisor Support
K.8.30 The CAD will provide the ability for a CAD supervisor, or another dispatcher with appropriate system permissions, to observe the activity of a given dispatcher including the pending events queue, active events, available units list, and map.

K.8.31 The CAD will enable a supervisor, or another dispatcher with appropriate system permissions, to co-dispatch the units under the control of another dispatcher.

CAD Testing / Training Environment
K.8.32 The CAD will support a CAD testing/training environment that mirrors the functionality of the CAD live environment.
#11..
- 349 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-144
K.8.33 The CAD testing/training will be able to be used, operated, started up, shut down, and updated to match the live application without affecting the live environment.

K.8.34 The CAD testing/training will include all tables and administrative configurations, and allows for call takers and dispatchers to train on specific services and on pre-configured geographic areas identical to that of the live environment.

K.8.35 The CAD testing/training will have a separate E9-1-1 test connection or canned script E9-1-1 information and provide realistic training regarding incoming E9-1-1 data.

K.8.36 The CAD testing/training will be able to be used to test modifications and updates to the live CAD application prior to implementing the modifications and updates in the live environment.

K.9 REPORTING AND MONITORING
Dispatch Supervisor Support
K.9.1 The ability to add additional dispatchers “on-the-fly” for one or more services either globally or for predetermined geographical areas.

K.9.2 The ability to create police districts/beats on the fly, which allows dispatchers to move units to defined city zones. Can be moved by command to other workstations/people/dispatchers.

CAD Management Reporting
K.9.3 The system will include standard reports that simultaneously use date, time, location, and/or incident type search parameters for report definitions.

K.9.4 Ability to concatenate file size (i.e., lengthy DUI checkpoint events).

K.9.5 The system will include the capability of customizing standard reports and for creating user-defined reports.

K.9.6 The system will provide access to all reports to the user, subject to permissions, from within the CAD system.

K.9.7 The system will include reports in the CAD security/permissions function (i.e. individual reports can be made available/unavailable based on a user’s security profile).

K.9.8 The system will provide all reports to users, subject to permissions, regardless of the application used to create user-defined or custom reports (i.e. internal to the CAD system or via a third-party reporting or analysis tool).

K.9.9 The system will provide an ad hoc reporting capability.

K.9.10 End users may retrieve report detail from either the incident number or the DR. #11..
- 350 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-145
K.9.11 The system will provide a data exporting capability.

Training and Testing
K.9.12 The CAD system’s training environment is clearly identifiable as the training environment (e.g. “TRAINING” prominently displayed on the screen).

Snapshot/Incident Relay
K.9.13 The proposed CAD includes functionality to provide a detailed, system-wide snapshot report and/or graphic display of the system status to include all units and events, based on a user-specified date, and time and an incident replay, based on a user-specified date and time, specific incidents, or other CAD events.

K.10

ADDITIONAL APCO REQUIREMENTS
National Suspicious Activity Reporting (SAR) Features
K.10.1 The CAD allows users to flag a CFS as “suspicious” with regard to the National SAR Initiative.

K.10.2 Flagged CFS are exported to the appropriate fusion center for SAR reporting.

K.10.3 The CAD provides the capability to notify an intelligence unit/counterterrorism unit when a SAR is submitted.
#11..
- 351 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-146
Glossary of Terms
Acceptance test – A test which must be passed before a system or system component is considered to meet specified requirements.

AFR – Automated Field Reporting.

ALI – Automatic Location Identification.

ANI – Automatic Number Identification.

AOL – Automatic Officer Location.

API – Application Protocol information.

Audit trail – An electronic history log of system activity.

AWS – Automated Warrant System.

Boolean query – Searching technique by which document Images are identified based on relationship's between attributes. it uses the logical (Boolean) operators AND, OR, NOT, to construct complex queries of the index database.

BOLO – Be On the Lookout
CAD – Computer Aided Dispatch.

CAL ID – California Identification Fingerprint System.

CAL Gangs – State of California database on gang information, including photographs and relationships.

CCTV – Close Circuit Television.

CLETS/JDIC – California Law Enforcement Telecommunications System.

CJIS – Criminal Justice information Systems (refers to FBI security policy).

DIS – Department of Homeland Security.

DMV – Department of Motor Vehicles.

DOJ – Department of Justice.

E CARS – State of California Electronic Crime Analysis Reporting System.

FBI – Federal Bureau of investigation.

Final acceptance – The decision that the system is complete and fully functional; that it meets all requirements specified in the contract, including performance, functional and reliability standards; that the vendor has met all contractual obligations; that the customer is prepared to meet all financial commitments to the vendor.

Functional systems test – A test which demonstrates the functionality of all modules, components and interfaces of the system as a fully integrated whole. This test must be completed to the satisfaction of the end user before the decision to ‘go live’ is made. it is not to be construed as the acceptance of the system, although it is frequently referred to as an acceptance test.

Geo-file – Geographical information data file (term used by older CAD systems).

GIS – Geographical information System.

Go-Live – The decision by the end user and the vendor to put the system, or any single phase of the system, into production mode GPD – Glendale Police Department.

GPS – Global Positioning System.

GJXML – Global Justice Extensive Markup Language.

GUI – Graphical User interface.
#11..
- 352 -
GPD Integrated Public Safety Solution RFP
Chapter 3: Technical and Functional Specifications
3-147
Legacy application – An existing software application, typically a mainframe or minicomputer based database application.

LEITSC – Law Enforcement information Technology Standards Council.

MDS – Mobile Data System.

MNI – Master Name index.

NCIC – National Crime information Center.

NIJ - National institute of Justice.

NLETS – National Law Enforcement Telecommunications System.

ODBC– Open Database Connectivity.

Performance test – A test that demonstrates that the vendor’s system meets the speed, volume and stress requirements of the system during a specified period of time, often called a stress test.

Record – A generic term used to describe official documentation, either of an entire case or event or components thereof.

Reliability test – A test conducted after the system has been put into production mode which demonstrates that the system meets all functional requirements and performs according to standards specified in the contract without downtime or other internally caused disruption for a period of time specified in the contract.

Successful completion of the reliability test is usually a requirement for final acceptance of the system.

RMS – Records Management System.

SOP – Standard Operating Procedure.
#11..
- 353 -

APPENDIX A
Appendices
#11..
- 354 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 2
Appendix A: Standard Agreement Form
CONTRACT No. _________

PROFESSIONAL SERVICES AGREEMENT

BETWEEN THE CITY OF GLENDALE
AND
____________________
THIS AGREEMENT (“Agreement”), effective ________________, 20___ (“Effective Date”), is between the City of Glendale ("CITY"), a municipal corporation, and ____________________ ("CONSULTANT”), a [(Name of State) corporation/ partnership/ limited partnership/ limited liability company] (collectively, “PARTIES” or individually, “PARTY”).

RECITALS
A. CITY is a public entity organized and existing under its Charter and the State of California’s Constitution.

B. CONSULTANT represents that CONSULTANT is, and will continue to be for this Agreement’s duration, a [(Name of State) corporation in good standing/ partnership/ limited partnership/ limited liability company.]
C. CONSULTANT possesses the competence, experience, expertise, skill, facilities, equipment, personnel, financial wherewithal, and other resources necessary to perform this Agreement’s tasks in a professional and competent manner.

D. CONSULTANT desires to furnish and perform professional services for CITY, on the terms and conditions described in this Agreement. CONSULTANT has the legal authority to provide, engage in, and carry out the professional services set forth in this Agreement.

AGREEMENT
THEREFORE, CITY engages CONSULTANT’s services, and in consideration of the PARTIES’ mutual promises, the PARTIES agree as follows:

1.0 INCORPORATION OF RECITALS
#11..
- 355 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 3

1.1. The Recitals constitute the factual basis upon which CITY and CONSULTANT have entered into this Agreement. CITY and CONSULTANT acknowledge the Recitals’ accuracy and, therefore, incorporate them into this Agreement.

2.0 TERM

2.1. This Agreement begins on the Effective Date, and continues in effect until completion of the work described in Article 3, unless this Agreement ends sooner according to the terms elsewhere in this document.

3.0 SERVICES

3.1. Scope of Work. CONSULTANT shall [specify services to be provided] (“the Services”) in accordance with the Scope of Work, which is attached as “Exhibit A” to this Agreement and is incorporated into it by this reference.

3.2. Written Authorization.
(A) CONSULTANT shall not make changes in the Scope of Work, perform any additional work, or provide any additional material, without first obtaining written authorization from CITY. If CONSULTANT provides additional services or materials without written authorization, or if CONSULTANT exceeds the Maximum Cost in Paragraph 7.4 of this Agreement, CONSULTANT proceeds at CONSULTANT's own risk and without payment. (B) CITY will authorize CONSULTANT to proceed with discrete tasks by issuing written Task Orders. Receipt of a written Task Order, signed by CITY’s Project Manager, is a prerequisite for CONSULTANT to proceed with each task. CONSULTANT shall not exceed the not-to-exceed price in each Task Order.] In performing each phase or task, CONSULTANT shall not exceed the Maximum Cost in Paragraph 7.4 of this Agreement.

Issuance of a Task Order neither authorizes CONSULTANT to incur expenditures in excess of the Maximum Cost, nor relieves CONSULTANT from its responsibility for completing all of the Services within the Maximum Cost.

3.3. Professional Standard of Care. During this Agreement’s Term:
(A) CONSULTANT and its Subconsultants, subcontractors, employees, and agents (collectively, “CONSULTANT PARTIES”) shall perform all of the Services in this Agreement in an expeditious and professional manner, using professionals properly licensed and duly qualified to perform the Services.
(B) CONSULTANT PARTIES shall perform the work described in this Agreement in accordance with generally accepted professional practices and principles, and in a manner consistent with the level of care and skill ordinarily exercised under similar conditions by members of CONSULTANT PARTIES’ profession currently practicing in California. By delivering the completed work, CONSULTANT PARTIES represent and certify that their work #11..
- 356 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 4
conforms to: the requirements of this Agreement; all applicable (federal, state, county, local, CITY) laws, rules, regulations, orders, and procedures; and the professional standard of care in California.
(C) CONSULTANT PARTIES are responsible for making an independent evaluation and judgment of all conditions affecting performance of the work, including without limitation: site conditions; existing facilities; seismic, geologic, soils, hydrologic, geographic, climatic conditions; applicable (federal, state, county, local, CITY) laws, rules, regulations, orders, and procedures; and all other contingencies or design considerations. Data, calculations, opinions, reports, investigations, or any other information or documents that CITY provides relating to site, local, or other conditions are not warranted or guaranteed, either expressly or implied, by CITY.
(D) When the Scope of Work requires or permits CITY’s review, approval, conditional approval, or disapproval, CONSULTANT acknowledges that CITY’s review, approval, conditional approval, or disapproval:
(1) Is solely for the purposes of administering this Agreement and determining whether CONSULTANT is entitled to payment for its Services;
(2) Is not to be construed as a waiver of any breach, or acceptance by CITY, of any responsibility— professional or otherwise— for the Services or CONSULTANT’s work product;
(3) Does not relieve CONSULTANT of the responsibility for complying with the standard of performance or professional care; or laws, regulations, or industry standards; and
(4) Does not relieve CONSULTANT from liability for damages arising out of CONSULTANT’s: negligent acts, errors, or omissions; recklessness; willful misconduct; or noncompliance with industry standards.
(E) Without additional compensation to CONSULTANT and at no cost to CITY, CONSULTANT shall correct or revise all errors, mistakes, or deficiencies in its work product, studies, reports, designs, drawings, specifications, or other services.

4.0 TIME FOR PERFORMANCE
#11..
- 357 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 5

4.1. CONSULTANT shall perform the Services according to the Project Time Schedule, which is attached as “Exhibit B” to this Agreement and is incorporated into it by this reference. CONSULTANT shall complete all of the Services by [DATE ] .

4.2. If the Project Time Schedule calls for performance of the Services in phases or discrete increments, CONSULTANT shall not proceed from one phase or increment to the next without written authorization from CITY’s Project Manager.

4.3. Force Majeure. If an event or condition constituting a “force majeure”— including, but not limited to, an act of God, labor dispute, civil unrest, epidemic, or natural disaster— prevents or delays a PARTY from performing or fulfilling an obligation under this Agreement, the PARTY is not in Default, under Paragraph 13.1 of this Agreement, of the obligation. A delay beyond a PARTY’s control automatically extends the time, in an amount equal to the period of the delay, for the PARTY to perform the obligation under this Agreement.

The PARTIES shall prepare and sign an appropriate document acknowledging any extension of time under this Paragraph.

5.0 PERSONNEL

5.1. Project Management. Each PARTY shall appoint a Project Manager.

The Project Managers shall meet onsite monthly to coordinate, review, and ensure CONSULTANT’s performance under this Agreement. CITY’s Project Manager will oversee the administration of CONSULTANT’s tasks under this Agreement.

5.2. Key Personnel. CONSULTANT’s project team shall work under the direction of the following key personnel: LIST
CONSULTANT shall employ the key personnel identified in “Exhibit A.” CONSULTANT shall minimize changes to its key personnel. CITY may request key personnel changes, and CITY may review and approve key personnel changes proposed by CONSULTANT. CITY will not unreasonably withhold approval of key personnel assignments and changes.

5.3. Use of Agents or Assistants. With CITY’s prior written approval, CONSULTANT may employ, engage, or retain the services of persons or entities (“Subconsultants”) that CONSULTANT may deem proper to aid or assist in the proper performance of CONSULTANT’s duties. CITY is an intended beneficiary of all work that the Subconsultants perform for purposes of establishing a duty of care between the Subconsultants and CITY. CONSULTANT is as responsible for the performance of its Subconsultants as it would be if it had rendered the Services itself. All costs of the tasks performed or the expenses incurred by the Subconsultants are chargeable directly to CONSULTANT. Nothing in this Agreement constitutes or creates a contractual relationship between CITY and anyone other than CONSULTANT.

5.4. Independent Contractor.
#11..
- 358 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 6
(A) CONSULTANT understands and acknowledges that CONSULTANT is an independent contractor, not an employee, partner, agent, or principal of CITY. This Agreement does not create a partnership, joint venture, association, or employer-employee relationship between the PARTIES. At its own expense, CONSULTANT is responsible for providing compensation; employment benefits; disability, unemployment, and other insurance; workers’ compensation; training; permits and licenses; and office space for CONSULTANT and for CONSULTANT’s employees and Subconsultants. CONSULTANT has, and shall retain, the right to exercise full control over the employment, direction, compensation, and discharge of all persons whom CONSULTANT uses in performing the Services under this Agreement.

CONSULTANT shall provide the Services in CONSULTANT’s own manner and method, except as this Agreement specifies. CONSULTANT shall treat a provision in this Agreement that may appear either to give CITY the right to direct CONSULTANT as to the details of doing the work, or to exercise a measure of control over the work, as giving CONSULTANT direction only as to the work’s end result.
(B) CONSULTANT shall indemnify, defend (including CONSULTANT’s providing and paying for legal counsel for CITY), and hold harmless CITY for any obligation; claim; suit; demand for tax or retirement contribution, including any contribution or payment to the Public Employees Retirement System (PERS); social security; salary or wages; overtime, penalty, or interest payment; or workers' compensation payment that CITY may be required to make on behalf of CONSULTANT, an employee of CONSULTANT, or any employee of CONSULTANT construed to be an employee of CITY, for the work done under this Agreement.

5.5. Non-Discrimination in Employment. CONSULTANT shall not discriminate against any employee or person who is subject to this Agreement because of race, color, religion, religious belief, national origin, ancestry, citizenship, age, sex, sexual orientation, marital status, pregnancy, parenthood, medical condition, or physical or mental disability.

5.6. Disability Access Laws. CONSULTANT represents and certifies that the work product, studies, reports, designs, drawings, and specifications that CONSULTANT prepares under this Agreement fully conform to all applicable disability access and design laws, regulations, and standards— including, but not limited to, the Americans with Disabilities Act (42 U.S.C. Sections 12101 et seq.) and Title 24 of the California Code of Regulations— when the Scope of Work requires or calls for compliance with those laws, regulations, or standards.

5.7. Prevailing Wage Laws. Services by persons deemed to be employees of CONSULTANT possibly may be subject to prevailing wages under California Labor Code Sections 1770-1781. CONSULTANT’s sole responsibility is to comply with those requirements, should they apply. If a dispute based upon the prevailing wage laws occurs, CONSULTANT, at its expense, shall indemnify, defend (including CONSULTANT’s providing and paying for legal counsel for CITY), and hold harmless CITY, its officers, agents, employees, and representatives from and against all liability, claims, suits, demands, damages, fines, penalties, wages, costs, or expenses pertaining to the prevailing wage laws.
#11..
- 359 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 7

5.8. Workers’ Compensation. CONSULTANT understands and acknowledges that all persons furnishing services to CITY under this Agreement are, for the purpose of workers’ compensation liability, employees solely of CONSULTANT and not of CITY. In performing the Services or the work under this Agreement, CONSULTANT is liable for providing workers’ compensation benefits to CONSULTANT’s employees, or anyone whom CONSULTANT directly or indirectly hires, employs, or uses. CITY is not responsible for any claims at law or in equity caused by CONSULTANT’s failure to comply with this Paragraph.

6.0 FACILITIES

6.1. CONSULTANT shall provide all facilities necessary to fully perform and complete the Services. If CONSULTANT needs to use a CITY facility, CONSULTANT shall meet and confer with CITY before CONSULTANT begins the work that this Agreement requires, the PARTIES shall agree to any costs chargeable to CONSULTANT, and in an amendment to this Agreement, the PARTIES shall describe the facility’s terms of use and its charges.

6.2. CONSULTANT shall pay for any damage to CITY property, facilities, structures, or streets arising out of CONSULTANT’s use, occupation, operation, or activities in, upon, under, or over any portion of them.

7.0 PAYMENT

7.1. CITY’s payment to CONSULTANT will be based upon CONSULTANT’s Fee Schedule, which is attached as “Exhibit C” to this Agreement and is incorporated into it by this reference. Except as itemized in the Fee Schedule, CONSULTANT shall pay for all expenses, including reimbursable or out-of-pocket expenses that CONSULTANT incurs in performing the Services. The Fee Schedule will remain in effect for the Agreement’s Term.

7.3. If CITY requires additional work not included in this Agreement, CONSULTANT and CITY shall negotiate the additional work, mutually agree on the amount of additional compensation, and memorialize the terms in either a separate written contract or an amendment to this Agreement.

7.4. Maximum Cost. CONSULTANT expressly acknowledges that the total cost to complete all tasks set forth in “Exhibit A” must not exceed ___________________________________ dollars ($__________) (“Maximum Cost”). When CONSULTANT has billed 75% of the Maximum Cost, CONSULTANT shall provide written notice to CITY’s Project Manager that CONSULTANT has expended 75% of the Maximum Cost.

7.5. Taxes. CONSULTANT shall pay all applicable (federal, state, county, local, CITY) excise, sales, consumer use, possessory interest, or other similar taxes required by #11..
- 360 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 8
law that are levied upon this Agreement or upon CONSULTANT’s services under this Agreement.

7.6. Invoices. CONSULTANT shall submit an original, itemized invoice to CITY for approval, before receiving compensation. CONSULTANT shall submit the invoice at no more than monthly intervals. All invoices must include a summary of total costs, description of the Services performed, a brief itemization of costs associated with each task or phase, and the total phase or project costs to date.

8.0 AUDIT BY CITY

8.1. During this Agreement’s Term and for a period of four (4) years after the expiration, cancellation, or termination of this Agreement, or any extension of it, CONSULTANT shall:
(A) Keep and maintain, in their original form, all records, books, papers, or documents related to CONSULTANT’s performance of this Agreement; and

(B) Permit CITY or its authorized representatives, at all reasonable times, to have access to, examine, audit, excerpt, copy, photocopy, photograph, or transcribe all records, books, papers, or documents related to CONSULTANT’s performance of this Agreement including, but not limited to: direct and indirect charges, and detailed documentation, for work CONSULTANT has performed or will perform under this Agreement.

9.0 DATA, RECORDS, PROPRIETARY RIGHTS

9.1. Copies of Data. CONSULTANT shall provide CITY with copies or originals of all data that CONSULTANT generates, uses, collects, or stores in relation to all work associated with this Agreement. Data that CONSULTANT generates, uses, collects, stores, or provides must be in a form acceptable to, and agreed upon by, CITY.

9.2. Ownership and Use.
(A) Unless CITY states otherwise in writing, each document— including, but not limited to, each report, draft, record, drawing, or specification (collectively, “work product”)— that CONSULTANT prepares, reproduces, or causes its preparation or reproduction for this Agreement is CITY’s exclusive property. (B) CONSULTANT acknowledges that its use of the work product is limited to the purposes contemplated by the Scope of Work. CONSULTANT makes no representation of the work product’s application to, or suitability for use in, circumstances not contemplated by the Scope of Work.

9.3. Intellectual Property.
#11..
- 361 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 9
(A) If CONSULTANT uses or incorporates patented, trademarked, or copyrighted work, ideas, or products— in whole or in part— into CONSULTANT’s work product, CONSULTANT represents that:
(1) CONSULTANT holds the patent, trademark, or copyright to the work, idea, or product; or
(2) CONSULTANT is licensed to use the patented, trademarked, or copyrighted work, idea, or product.
(B) Unless CITY states otherwise in writing, all proprietary rights or intellectual property rights, including copyrights that arise from creation of the work under this Agreement vest in CITY. CONSULTANT waives and relinquishes all claims to proprietary rights and intellectual property rights, including copyrights, in favor of CITY. (C) CONSULTANT shall indemnify, defend (including CONSULTANT’s providing and paying for legal counsel for CITY), and hold harmless CITY, its officers, agents, employees, and representatives from and against all liability, claims, suits, demands, damages, royalties, fines, penalties, costs, or expenses arising out of or alleging any infringement or misappropriation of a patent, copyright, trade secret, trade name, trademark, or other intellectual property right or proprietary right.

9.4. Confidentiality. CONSULTANT shall not use any information that it obtains from performing the Services for any purpose other than for fulfillment of CONSULTANT’s Scope of Work. Without CITY’s prior written authorization, CONSULTANT shall not disclose or publish— or authorize, permit, or allow others to disclose or publish— data, drawings, designs, specifications, reports, or other information relating to the Services or the work that CITY assigns to CONSULTANT or to which CONSULTANT has access.

9.5. Public Records Act.
(A) CONSULTANT acknowledges that this Agreement is a public record.

This Agreement, its Exhibits, and all documents produced under this Agreement are subject to the California Public Records Act (Government Code Sections 6250 et seq.), including its exemptions. CONSULTANT acknowledges that CITY has no obligation to notify CONSULTANT when a request for records is received.
(B) CONSULTANT shall identify in advance all records, or portions of them, that CONSULTANT believes are exempt from production under the Public Records Act. (C) If CONSULTANT claims a privilege against public disclosure or otherwise objects to the records’ disclosure, then:
#11..
- 362 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 10
(1) CONSULTANT may, when notified by CITY of the request, seek protection from disclosure by timely applying for relief in a court of competent jurisdiction; or
(2) CITY may either decline to produce the requested information, or redact portions of the documents and produce the redacted records. (D) If CONSULTANT fails to identify one or more protectable documents, in CITY’s sole discretion, and without its being in breach of this Agreement or its incurring liability to CONSULTANT, CITY may produce the records— in whole, in part, or redacted— or may decline to produce them.
(E) CONSULTANT shall indemnify, defend (including CONSULTANT’s providing and paying for legal counsel for CITY), and hold harmless CITY, its officers, agents, employees, and representatives from and against all liability, claims, suits, demands, damages, fines, penalties, costs, or expenses arising out of or alleging CITY’s refusal to publicly disclose one or more records that CONSULTANT identifies as protectable, or asserts is protectable.

10.0 CONFLICT OF INTEREST; CAMPAIGN CONTRIBUTIONS

10.1. Conflict of Interest. CONSULTANT represents and certifies that:
(A) CONSULTANT’s personnel are not currently officers, agents, employees, representatives, or elected officials of CITY;
(B) CONSULTANT will not employ or hire a CITY officer, agent, employee, representative, or elected official during this Agreement’s Term; (C) CITY’s officers, agents, employees, representatives, and elected officials do not, and will not, have any direct or indirect financial interest in this Agreement; and (D) During this Agreement’s Term, CONSULTANT will inform CITY about any possible conflict of interest that may arise as a result of any change in circumstances.

10.2. Campaign Contributions.
(A) CONSULTANT and its Subconsultants shall fully comply with Glendale Municipal Code Section 1.10.060, which places limitations on CONSULTANT’s and its Subconsultants’ ability to make campaign contributions to certain elected City officials or candidates for elected City office. Specifically, Section 1.10.060 prohibits:
(1) A consultant (including a subconsultant)― who has a contract with the City of Glendale, Glendale Successor Agency, or the Housing Authority of the City of Glendale and that contract is subject to #11..
- 363 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 11
approval by the City Council, Successor Agency, or Housing Authority― from making a contribution to a City Council member, City Clerk, or City Treasurer, when the contract has a total anticipated or actual value of $50,000 or more, or a combination or series of contracts having a value of $50,000 or more; and
(2) A City Council member, Successor Agency member, or Housing Authority member from voting on a contract in which a consultant (or a subconsultant) has provided a campaign contribution.
(B) CONSULTANT acknowledges that even if the Maximum Cost in Paragraph 7.4 of this Agreement is less than $50,000, CONSULTANT still may be subject to the campaign contribution limitations in Municipal Code Section 1.10.060, when:
(1) CONSULTANT and CITY amend the Scope of Services in
this Agreement which increases the Maximum Cost to equal or exceed $50,000; or
(2) CITY, Glendale Successor Agency, or the Housing Authority awards CONSULTANT another contract which has a total anticipated or actual value of $50,000 or more, or awards CONSULTANT a combination or series of contracts which have a value of $50,000 or more.
(C) CONSULTANT represents and certifies that:
(1) CONSULTANT has read and fully understands the provisions of Municipal Code Section 1.10.060;

(2) CONSULTANT will not: (a) make a prohibited campaign contribution to an individual holding CITY elective office; or (b) otherwise violate Municipal Code Section 1.10.060; and
(3) CONSULTANT shall timely complete, return, and update one or more disclosure or reporting forms that CITY provides.

11.0 INSURANCE

11.1. When CONSULTANT signs and delivers this Agreement to CITY, and during this Agreement’s Term, CONSULTANT shall furnish CITY with insurance forms that fully meet the requirements of— and contain provisions entirely consistent with— all of the “Insurance #11..
- 364 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 12
Requirements,” which are attached as “Exhibit D” (D-1 to D-___) to this Agreement and are incorporated into it by this reference.

11.2. This Agreement’s insurance provisions:
(A) Are separate and independent from the indemnification and defense provisions in Article 12 of the Agreement; and
(B) Do not limit, in any way, the applicability, scope, or obligations of the indemnification and defense provisions in Article 12 of the Agreement.

12.0 INDEMNITY

12.1. To the maximum extent permitted by law— including, but not limited to, California Civil Code Section 2778— CONSULTANT, its employees, agents, Subconsultants, and persons whom CONSULTANT employs or hires (individually and collectively, “CONSULTANT INDEMNITOR”) shall indemnify, defend, and hold harmless CITY, its officers, agents, employees, and representatives (individually and collectively, “CITY INDEMNITEE”) from and against a “liability” [as defined in Subparagraph (A) below], or an “expense” [as defined in Subparagraph (B) below], or both, that arise out of, pertain to, or relate to an act, error, or omission of a CONSULTANT INDEMNITOR:
(A) “Liability” means claims, suits, actions, causes of action, proceedings, judgments, decrees, awards, settlements, liens, losses, damages, injuries, or liability of any kind, whether the liability is:
(1) Actual or alleged;
(2) In contract or in tort; or
(3) For bodily injury (including accidental death), personal injury, advertising injury, or property damage.
(B) “Expense” means fees, costs, sums, penalties, fines, charges, or expenses of any kind, including, but not limited to:
(1) Attorney’s fees;
(2) Costs of an investigation, litigation, arbitration, mediation, administrative or regulatory proceeding, or appeal;
(3) Fees of an accountant, expert witness, consultant, or other professional; or
(4) Pre or post: judgment interest or settlement interest. #11..
- 365 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 13

12.2. Under this Article, CONSULTANT INDEMNITOR’s defense and indemnification obligations:
(A) Apply to a liability, or an expense, or both, that arise out of, pertain to, or relate to the actual or alleged passive negligence of a CITY INDEMNITEE; but (B) Do not apply to a liability, or an expense, or both, that arise out of, pertain to, or relate to the sole active negligence or willful misconduct of a CITY INDEMNITEE.

12.3. To the extent that CONSULTANT INDEMNITOR’s insurance policy provides an upfront defense to CITY, CONSULTANT INDEMNITOR’s obligation to defend a CITY INDEMNITEE under this Article:
(A) Means that CONSULTANT INDEMNITOR shall provide and pay for legal counsel, acceptable to CITY, for the CITY INDEMNITEE; (B) Occurs when a claim, suit, complaint, pleading, or action against a CITY INDEMNITEE arises out of, pertains to, relates to, or asserts an act, error, or omission of CONSULTANT INDEMNITOR; and
(C) Arises regardless of whether a claim, suit, complaint, pleading, or action specifically names or identifies CONSULTANT INDEMNITOR.

12.4. Paragraph 12.3 does not limit or extinguish CONSULTANT INDEMNITOR’s obligation to reimburse a CITY INDEMNITEE for the costs of defending the CITY INDEMNITEE against a liability, or an expense, or both. A CITY INDEMNITEE’s right to recover defense costs and attorney’s fees under this Article does not require, and is not contingent upon, the CITY INDEMNITEE’s first:
(A) Requesting that CONSULTANT INDEMNITOR provide a defense to the CITY INDEMNITEE; or
(B) Obtaining CONSULTANT INDEMNITOR’s consent to the CITY INDEMNITEE’s tender of defense.

12.5. If CONSULTANT subcontracts all or any portion of the Services under this Agreement, CONSULTANT shall provide CITY with a written agreement from each Subconsultant, who must indemnify, defend, and hold harmless CITY INDEMNITEE under the terms in this Article.

12.6. CONSULTANT INDEMNITOR’s obligation to indemnify, defend, and hold harmless CITY will remain in effect and will be binding upon CONSULTANT INDEMNITOR #11..
- 366 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 14
whether the liability, or the expense, or both, accrues— or is discovered— before or after this Agreement’s expiration, cancellation, or termination.

12.7. Except for Paragraph 12.3, this Article’s indemnification and defense provisions are separate and independent from the insurance provisions in Article 11. In addition, the indemnification and defense provisions in this Article:
(A) Are neither limited to nor capped at the coverage amounts specified under the insurance provisions in Article 11; and
(B) Do not limit, in any way, the applicability, scope, or obligations of the insurance provisions in Article 11.

13.0 DEFAULT, REMEDIES, AND TERMINATION

13.1. Default. Default under this Agreement occurs upon any one or more of the following events:
(A) CONSULTANT refuses or fails— whether partially, fully, temporarily, or otherwise— to:
(1) Provide or maintain enough properly trained personnel, or licensed personnel, or both, to perform the Services that this Agreement requires;
(2) Pay for, obtain, maintain, or renew the insurance policies or coverages that this Agreement requires;
(3) Comply with indemnification, defense, or hold harmless provisions that this Agreement requires; or
(B) CONSULTANT, or its personnel, or both— whether partially, fully, temporarily, or otherwise:
(1) Disregards or violates a law, ordinance, rule, procedure, regulation, directive, or order;
(2) Refuses or fails to pay for, obtain, maintain, or renew requisite licenses;
(3) Refuses or fails to observe, perform, or fulfill a covenant, condition, obligation, term, or provision of this Agreement; #11..
- 367 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 15
(4) Commits an unlawful, false, fraudulent, dishonest, deceptive, or dangerous act while performing the Services under this
Agreement; or
(C) CONSULTANT:
(1) Or another party for or on behalf of CONSULTANT: institutes proceedings under any bankruptcy, reorganization, receivership or other insolvency; or assigns or transfers assets to its creditors; (2) Delegates— whether in whole, in part, temporarily, or otherwise— its duties or obligations under this Agreement, without notifying CITY, or without CITY’s written authorization;
(3) Assigns, transfers, pledges, hypothecates, grants, or encumbers— whether in whole, in part, temporarily, or otherwise— this Agreement or any interest in it, without notifying CITY, or without CITY’s written authorization;
(4) Or one of its partners, directors, officers, or general managers, or a person who exercises managerial authority on CONSULTANT’s behalf, is convicted under state or federal law, during this Agreement’s Term, of embezzlement, theft, fraud, forgery, bribery, deceptive or unlawful business practices, perjury, falsifying or destroying records or evidence, receiving stolen property, or other offense indicating a lack of business integrity or business honesty; or
(D) Any other justifiable cause or reason, as reasonably determined by the City Manager, or a designee.

13.2. Notice of Default. If CITY deems that CONSULTANT is in Default, or that CONSULTANT has failed in any other respect to satisfactorily perform the Services specified in this Agreement, CITY may give written notice to CONSULTANT specifying the Default(s) that CONSULTANT shall remedy within 30 days after receiving the notice. The Notice of Default will set forth one or more bases for any dissatisfaction and may suggest corrective measures.

13.3. Remedies upon Default. Within 30 days after receiving CITY’s Notice of Default, if CONSULTANT refuses or fails to remedy the Default(s), or if CONSULTANT does not commence steps to remedy the Default(s) to CITY’s reasonable satisfaction, CITY may exercise any one or more of the following remedies:
(A) CITY may, in whole or in part and for any length of time, immediately #11..
- 368 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 16
suspend this Agreement until such time as CONSULTANT has corrected the Default; (B) CITY may provide for the Services either through its own forces or from another consultant, and may withhold any money due (or may become owing to) CONSULTANT for a task related to the claimed Default;
(C) CITY may withhold all moneys, or a sum of money, due CONSULTANT under this Agreement, which in CITY’s sole determination, are sufficient to secure CONSULTANT’s performance of its duties and obligations under this Agreement; (D) CITY may immediately terminate the Agreement;
(E) CITY may exercise any legal remedy, or equitable remedy, or both, including, but not limited to, filing and action in court:
(1) Seeking CONSULTANT’s specific performance of all or any part of this Agreement; or
(2) Recovering damages for CONSULTANT’s Default, breach, or violation of this Agreement; or
(F) CITY may pursue any other available, lawful right, remedy, or action.

13.4. Termination for Convenience. Independent of the remedies provided in Paragraph 13.3, CITY may elect to terminate this Agreement at any time upon 30 days’ prior written notice. Upon termination, CONSULTANT shall receive compensation only for that work which CONSULTANT had satisfactorily completed to the termination date. CITY shall not pay CONSULTANT for de-mobilization, takedown, disengagement, wind-down, or other costs incurred arising out of this Agreement’s termination.

14.0 GENERAL PROVISIONS

14.1. Entire Agreement. This Agreement represents the entire and integrated agreement between the PARTIES. This Agreement supersedes all prior and contemporaneous communications, negotiations, understandings, promises and agreements, either oral or written.

Neither CONSULTANT nor CITY has made any promises or representations, other than those contained in this Agreement or those implied by law. The PARTIES may modify this Agreement, or any part of it, by a written amendment with CITY’s and CONSULTANT’s signature.

14.2. Interpretation. This Agreement is the product of negotiation and compromise by both PARTIES. Every provision in this Agreement must be interpreted as though the PARTIES equally participated in its drafting. Therefore, despite the provisions in California Civil Code Section 1654, if this Agreement’s language is uncertain, the Agreement must not be #11..
- 369 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 17
construed against the PARTY causing the uncertainty to exist. In interpreting this Agreement and resolving any ambiguities, this Agreement will take precedence over any cover page or attachments. If a conflict occurs between a provision in this Agreement and a provision in an attachment, the following order of precedence applies, with the terms and conditions in the document higher on the list governing over those lower on the list:
(1) The Agreement.
(2) Exhibit D.
(3) Exhibit B.
(4) Exhibit A.
(5) Exhibit C.

14.3. Headings. All headings or captions in this Agreement are for convenience and reference only. They are not intended to define or limit the scope of any term, condition, or provision.

14.4. Governing Law. California’s laws govern this Agreement’s construction and interpretation. Unless this Agreement provides otherwise, any reference to laws, ordinances, rules, or regulations include their later amendments, modifications, and successor legislation.

14.5. Waiver of Breach. If a PARTY waives the other PARTY’s breach of a term in this Agreement, that waiver is not treated as waiving a later breach of the term and does not prevent the PARTY from later enforcing that term, or any other term. A waiver of a term is valid only if it is in writing and signed by the PARTY waiving it. This Agreement’s duties and obligations:
(A) Are cumulative (rather than alternative) and are in addition to (rather than a limitation on) any option, right, power, remedy, or privilege; and (B) Are not exhausted by a PARTY’s exercise of any one of them.

14.6. Attorney’s Fees. If CITY or CONSULTANT brings an action at law or in equity to enforce or interpret one or more provisions of this Agreement, the “prevailing party” is entitled to “reasonable attorney's fees” in addition to any other relief to which the prevailing party may be entitled. A “prevailing party” has the same meaning as that term is defined in California Code of Civil Procedure Section 1032(a)(4). “Reasonable attorney’s fees” of the City Attorney’s office means the fees regularly charged by private attorneys who:
(A) Practice in a law firm located in Los Angeles County; and (B) Have an equivalent number of years of professional experience in the subject matter area of the law for which the City Attorney’s services were rendered. #11..
- 370 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 18

14.7. Further Assurances. Upon CITY’s request at any time, CONSULTANT shall promptly:
(A) Take further necessary action; and
(B) Sign, acknowledge, and deliver all additional documents as may be reasonable, necessary, or appropriate to carry out this Agreement’s intent, purpose, and terms.

14.8. Assignment.
(A) This Agreement does not give any rights or benefits to anyone, other than to CITY and CONSULTANT. All duties, obligations, and responsibilities under this Agreement are for the sole and exclusive benefit of CITY and CONSULTANT, and are not for the benefit of another person, entity, or organization. Without CITY’s prior written authorization, CONSULTANT shall not do any one or more of the following:
(1) Assign or transfer a right or interest— whether in whole, in part, temporarily, or otherwise— in this Agreement; or
(2) Delegate a duty or obligation owed— whether in whole, in part, temporarily, or otherwise— under this Agreement.
(B) Any actual or attempted assignment of rights or delegation of duties by CONSULTANT, without CITY’s prior written authorization, is wholly void and totally ineffective for all purposes; and does not postpone, delay, alter, extinguish, or terminate CONSULTANT’s duties, obligations, or responsibilities under this Agreement. (C) If CITY consents to an assignment of rights, or a delegation of duties, or both, CONSULTANT’s assignee or legal representative shall agree in writing to personally assume, perform, and to be bound unconditionally by the covenants, obligations, terms, and conditions in this Agreement.

14.9. Successors and Assigns. Subject to the provisions in Paragraph 14.8, this Agreement is binding on the heirs, executors, administrators, successors, and assigns of the respective PARTIES.

14.10. Time is of the Essence.
(A) Except when this Agreement states otherwise, time is of the essence in this Agreement. CONSULTANT acknowledges that this Agreement’s time limits and deadlines are reasonable for CONSULTANT’s performing the Services under this Agreement. (B) Unless this Agreement specifies otherwise, any reference to “day” or “days” means calendar and not business days. If the last day for giving notice or performing an act under this Agreement falls on a weekend, a legal holiday listed in either Glendale Municipal Code #11..
- 371 -
GPD Integrated Law Enforcement Solution RFP
Appendix A
APPENDIX A PAGE 19
Section 3.08.010 or California’s Government Code, or a day when City Hall is closed, the period is extended to and including the next day that CITY is open for business. A reference to the time of day refers to local time for Glendale, California.

14.11. Recycled Paper. CONSULTANT shall endeavor to submit all reports, correspondence, and documents related to this Agreement on recycled paper.

14.12. Notices.
(A) The PARTIES shall submit in writing all notices and correspondence that this Agreement requires or permits, and shall deliver the notices and correspondence to the places set forth below. The PARTIES may give notice by:
(1) Personal delivery;
(2) U.S. mail, first class postage prepaid;
(3) “Certified” U.S. mail, postage prepaid, return receipt requested; or (4) Facsimile.
(B) All written notices or correspondence sent in the described manner will be presumed “given” to a PARTY on whichever date occurs earliest:
(1) The date of personal delivery;
(2) The third (3rd) business day following deposit in the U.S. mail, when sent by “first class” mail;
(3) The date on which the PARTY or its agent either signed the return receipt or refused to accept delivery, as noted on the return receipt or other U.S. Postal Service form, when sent by “certified” mail; or (4) The date of transmission, when sent by facsimile.
(C) At any time, by providing written notice to the other PARTY, CITY or CONSULTANT may change the place, or facsimile number, for giving notice.

Modesto City CouncilJuly 9, 2024

Modesto City Council
July 9, 2024