RFP 2026_08 Co_Managed IT Services (FINAL).pdf

City of Hinesville – RFP 2026-08 Co-Managed IT Services

REQUEST FOR PROPOSALS TO PROVIDE

CO-MANAGED IT SERVICES

RFP 2026-08

ISSUED ON: September 28, 2026

SUBMITTAL DEADLINE: Friday, October 23, 2026 at 12:00 pm

City of Hinesville – RFP 2026-08 Co-Managed IT Services 2

TABLE OF CONTENTS

1. General Information and Overview

2. Background and Co-Managed IT Model

3. Scope of Services

4. Service Levels and Performance Requirements

5. Transition and Onboarding

6. Reporting and Governance

7. Out-of-Scope and Professional Services

8. Proposal Requirements and Format

9. Cost Proposal Requirements

10. Evaluation and Selection

11. General RFP Conditions

12. Contract Requirements

13. Required Forms and Attachments

Attachment A – Proposer Information Form

Attachment B – References

Attachment C – Cost Proposal Form

Attachment D – Exceptions / Deviations

Attachment E – Conflict of Interest Certification

Attachment F – Georgia E-Verify / Immigration Compliance Affidavit

Attachment G – Non-Collusion Affidavit

Attachment H – Insurance Requirements

City of Hinesville – RFP 2026-08 Co-Managed IT Services 3

1. GENERAL INFORMATION AND OVERVIEW

1.1 Purpose

The City of Hinesville (the “City”) is seeking proposals from qualified Information Technology firms to provide comprehensive co-managed IT services. The City intends to retain an experienced co-managed technology partner to supplement the City’s internal IT team by providing remote Tier 1 end-user support through a ticketing system, monitoring and alerting support, cybersecurity support, and collaborative assistance on escalated and complex issues. City IT retains ownership of network and systems administration, production configurations, firewall policy, hardware standards, and architecture decisions.

1.2 Solicitation Information

Item Information Solicitation Request for Proposals – Co-Managed IT Services RFP Number 2026-08 Issuing Entity City of Hinesville, Georgia Proposal Contact Temperance West, Assistant City Manager Email twest@cityofhinesville.org Proposal Delivery Address 115 East M.L. King, Jr. Dr.

Hinesville, GA 31313

Optional Pre-bid Meeting:

All firms that intend to respond to this solicitation are invited to a virtual pre-bid meeting/tour that will be held on Tuesday, October 06, 2026 beginning at 10:00 am. For a link to the pre-bid meeting, please contact Temperance West, twest@cityofhinesville.org. All questions and answers during this meeting will be documented and posted to the city’s website, www.cityofhinesville.org as an addendum prior to the submittal deadline.

1.3 Questions and Communications

All inquiries and questions regarding this RFP shall be in writing and directed to:

Temperance West, Assistant City Manager 115 East M.L. King, Jr. Drive

Hinesville, Georgia 31313 twest@cityofhinesville.org

The deadline for submission of any written questions relating to this RFP shall be Friday, October 09, 2026 at 5:00 pm. All questions and answers will be documented and posted to the city’s website, www.cityofhinesville.org as an addendum prior to the submittal deadline. Please check the City’s web site often to review the addendums, if any.

Proposing companies shall not contact the Mayor or the City Council or any city employee regarding this RFP, proposal evaluation, or selection process from the time the RFP is issued on Monday, September 28, 2026, until a company is selected.

Tentative RFP Timeline Date / Time

RFP Issued Monday, September 28, 2026 Newspaper and Media Advertisements Thursdays, September 24 and October 02, 2026 Optional Pre-Bid Tuesday, October 06, 2026, 10:00 am Comments/Questions Due Friday, October 09, 2026, 5:00 pm City response to questions/comments Friday, October 16, 2026, 5:00 pm Submittal deadline Friday, October 23, 2026, 12:00 pm RFP Opening Friday, October 23, 2026, 12:00 pm Review of qualifications and proposals October 23-30, 2026 Recommendations to Mayor and Council Thursday, November 05, 2026 Contract term begins Monday, November 09, 2026 mailto:twest@cityofhinesville.org mailto:twest@cityofhinesville.org mailto:bedwards@cityofhinesville.org http://www.cityofhinesville.org/

City of Hinesville – RFP 2026-08 Co-Managed IT Services 4

1.4 Submittal Deadline

Responses are due no later than 12:00 pm on Friday, October 23, 2026. The responses (one electronic flash drive and 3 printed copies) must be enclosed in a sealed envelope plainly marked, “City of Hinesville Proposal for Co-Managed IT Services,” and delivered to the Assistant City Manager’s Office, 115 East M.L. King, Jr. Drive, Hinesville, Georgia 31313, by the above deadline date and time. One Cost Proposal should be submitted in a separate sealed envelope clearly labeled with your company name and “Cost Proposal”. The cost proposal should NOT be included on the electronic file.

A representative of Hinesville City government will publicly read the names of the companies submitting responses at 12:00 pm on Friday, October 23, 2026. Incomplete responses may not be considered if the omissions are determined to be significant. The City will not be responsible for late mail deliveries and any responses received after the deadline date and time will not be accepted and returned unopened.

1.5 Public Records

Proposals submitted to the City may be subject to disclosure under applicable Georgia public-records laws.

Proposers shall identify any information they believe is legally protected from disclosure and shall identify the applicable legal basis for any requested protection. The City makes no representation that any designation will prevent disclosure where disclosure is required by law.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 5

2. BACKGROUND AND CO-MANAGED IT MODEL

2.1 Background

The City is seeking a co-managed IT service model rather than a fully outsourced IT arrangement. The successful Contractor shall supplement and extend the City’s internal IT capabilities, not unnecessarily duplicate or displace City personnel.

Under the Co-Managed services model, the City’s internal IT personnel will retain ownership of network and systems administration, production configurations, firewall policy, hardware standards, and architecture decisions. The Contractor will supplement the City’s team by providing remote Tier 1 end-user support through the ticketing system, centralized monitoring and alerting support, cybersecurity support, and collaborative escalation assistance. The Contractor shall not implement high-impact network, firewall, server, or identity changes unless directed by the City.

The City’s current environment, staffing levels, systems, user counts, network architecture, applications, and technology inventory may change during the contract term. Proposers should include any cost assumptions related to any changes in users in their proposal.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 6

3. SCOPE OF SERVICES

The following services represent the minimum scope anticipated by the City. Proposers may offer additional capabilities where they are relevant to the City’s objectives. Unless expressly identified as optional or separately priced, required services shall be included in the proposed recurring managed-services fee.

Current City Staff Roles and Responsibilities are as follows and will remain so under the Co-Managed Contract

• City Network and Systems Administration o firewall rules and policy, routing and switching configuration, o VLANs, VPN and remote access design, wireless infrastructure, and network hardware standards.

o server platforms, o core identity administration o system-level backup/recovery design.

The Contractor may recommend configurations, review changes, monitor supported systems, and assist with implementation when requested by City IT.

3.1 Co-Managed Services Provided

• Remote Tier 1 end-user support through the ticketing system during normal support hours

• Collaborative support and escalation assistance for server, network, Microsoft 365, backup, and cybersecurity issues

• Monitoring of supported workstations, servers, network infrastructure, backups and security events

• Review and validation of priority infrastructure and cybersecurity alerts, ensuring City visibility and decision on infrastructure changes

• Patch, vulnerability, and remediation coordination/assistance as needed from City IT Staff

• Microsoft 365 Administrative Assistance

• User-account, access-control, and administrative support

• Security incident triage and response assistance, as needed.

• Technical guidance and escalation support for City’s internal IT personnel

• Coordination with approved vendors, internet service providers, and technology partners

• Documentation of significant incidents, changes, risks, and remediation activities

• Bi-Weekly operational coordination meetings

• Monthly management, service, and cybersecurity reporting

• Advisory recommendations concerning staffing, support, and technology operating matters, as requested by the City; major redesign or platform replacement is not included in the recurring co-managed fee unless separately authorized

3.2 Co-Managed Responsibilities

• City IT will retain ownership of network and systems administration, production configurations, firewall policy, hardware standards, and architecture decisions.

o Perform onsite equipment installation and replacement o Coordinate directly with City departments and personnel o Maintain accurate user, device, and asset information o Receive and own tickets involving network infrastructure, firewall or device configuration, servers, identity and access architecture, backup platform work, and design or architecture questions

• Vendor will:

o Provide remote Tier 1 support through the ticketing system and remain engaged as a collaborator on escalated tickets

City of Hinesville – RFP 2026-08 Co-Managed IT Services 7 o Provide collaborative support, monitoring, troubleshooting, technical recommendations, and implementation assistance for server, network, Microsoft 365, backup, and security issues when directed by City IT o Review priority monitoring and SIEM alerts and promptly notify the appropriate City administrator of issues requiring City-owned infrastructure or systems action o Provide technical recommendations and remediation guidance without assuming ownership of City network or systems administration o Document significant work and maintain service records o Provide operational and management reporting

• Shared Responsibilities o The Contractor and City IT personnel will work together on ticket prioritization, patch and vulnerability remediation, user onboarding/offboarding, Microsoft 365 support, backup recovery activities, security incident handling, vendor coordination, infrastructure planning, and technology documentation. Shared work does not transfer ownership of City network or systems administration.

The final responsibility matrix shall be refined during onboarding and incorporated into the operating procedures for the contract.

3.3 Service Availability

Vendor support shall be provided Monday through Friday during normal business hours, excluding City-recognized holidays. After-hours response will be expected for Emergency and Critical incidents affecting public safety, essential City services, widespread operations, cybersecurity, or systems specifically designated as critical by the City, including support for the Police Department and Fire Department. For such incidents, the Contractor shall respond and participate fully, while City IT remains the incident owner. The Contractor shall work alongside City IT Staff, provide specialized capability and assistance, and document actions taken.

3.4 Out of Scope Services

Out of scope services will require written authorization from the City.

3.5 Current Technology Environment

Technology Category Confirmed Quantity Active Users 251 users Workstations and laptops 218 devices Servers 24 servers Total managed endpoints and servers 242 devices

3.6 Security and Public Safety Systems

Where the Contractor supports systems that access, transmit, store, or otherwise handle Criminal Justice Information (CJI), the Contractor shall comply with applicable FBI Criminal Justice Information Services (CJIS) Security Policy requirements and applicable state and local requirements. The Contractor shall demonstrate experience supporting CJIS-regulated environments and shall cooperate with required screening, audits, documentation, access controls, encryption, logging, and secure handling requirements.

3.7 Third-Party and Law-Enforcement Application Coordination

Where applicable, the Contractor shall coordinate with CAD/RMS, public-safety application providers, telecommunications providers, and other third-party vendors. The Contractor shall not make material changes to public-safety systems without appropriate City authorization.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 8

3.8 Other Services

Proposers may identify other services they believe are necessary to achieve the City’s objectives. Such services shall be clearly identified as included in the base recurring fee, optional, or separately billable.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 9

4. SERVICE LEVELS AND PERFORMANCE REQUIREMENTS

For Emergency and Critical incidents, including after-hours events affecting public safety or essential services, the Contractor shall respond and participate fully. City IT remains the incident owner for City-owned infrastructure. The Contractor’s role is to assist restoration, provide specialized capability, and document actions taken. Service-level commitments shall measure time to engage and quality/timeliness of assistance and shall not assign sole responsibility for restoring City-owned network or systems infrastructure to the Contractor.

Proposers will need to develop service levels including initial response, escalation, and remediation timelines for the following, at a minimum.

Priority Examples Emergency Business Hours

The entire organization, a department, public-safety function, or critical business operation cannot function because of a production-system outage or major cybersecurity incident

Critical A user cannot perform a business-critical job function, no reasonable workaround exists, or the issue presents a significant operational or security impact.

Normal Routine user/system issue with reasonable workaround Scheduled Maintenance

Planned upgrades, maintenance activities, configuration changes, installations, or other scheduled technical services

New User Setup Setup for one new employee or deployment of one new system for an existing employee

Orientation Setup or orientation for two to four new employees or new systems for two to four existing employees

Low A routine issues, information request, minor inconvenience, or inquiry that does not result in a material loss of computing or business function

The response-time requirement is the time to acknowledge and begin active response, not necessarily the time to resolve the incident. For Emergency and Critical incidents involving City-owned infrastructure, City IT remains the incident owner. Proposers shall provide proposed engagement/response targets, collaborative restoration procedures, and escalation procedures. Vendor response commitments measure timely engagement and quality of assistance and do not assign sole restoration responsibility for City-owned infrastructure to the Contractor.

4.1 Normal Support Hours

Unless otherwise proposed and accepted, normal support hours shall be Monday through Friday, 8:00 a.m.

through 5:00 p.m. Eastern Time, excluding City-observed holidays.

4.2 Service-Level Reporting

• Ticket volumes by priority and department.

• Response and resolution performance against SLA commitments.

• Open-ticket aging and escalations.

• Recurring incidents and root-cause trends.

• Patch compliance and endpoint coverage.

• Backup success/failure and restore testing.

• Security incidents and material alerts.

• Service availability and material outages.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 10

5. TRANSITION AND ONBOARDING

The successful Proposer shall provide a 90-day transition and onboarding plan designed to establish an accurate operational baseline, integrate the Contractor into the City’s existing IT environment, and stabilize operations without unnecessary disruption to City services. The transition is intended to validate and document the current environment, identify immediate operational risks, establish support and escalation procedures, and deploy or validate required monitoring and ticketing capabilities. Major redesign, platform replacement, or deep architecture changes are outside the recurring co-managed scope unless separately requested and authorized in writing by the City.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 11

6. REPORTING AND GOVERNANCE

6.1 Monthly Service Review

The Contractor shall provide a monthly service report and participate in periodic service reviews. At a minimum, the report shall address:

• SLA performance

• Ticket activity and aging

• Recurring problems

• Security events

• Patch and endpoint compliance

• Backup status

• Material outages

• Open recommendations

• Project/out-of-scope work

• Upcoming risks and planned activities

6.2 Quarterly Technology Review

At least quarterly, the Contractor shall provide a management-level technology review addressing security posture, network health, lifecycle risks, continuity, strategic priorities, and recommended actions with estimated costs.

6.3 Documentation Ownership

All City-specific documentation developed under the contract shall be maintained in a format reasonably usable by the City. The Contractor shall provide current copies upon request and as part of transition-out activities.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 12

7. OUT-OF-SCOPE AND PROFESSIONAL SERVICES

The recurring managed-services fee shall include all services necessary to perform the required core co-managed scope. The recurring scope is intended to support and stabilize the City’s existing technology environment. Work outside the recurring scope may include major redesign, significant adds/moves/changes, new infrastructure deployment, application implementation, large-scale migrations, platform replacement, deep architecture changes, and other work expressly identified as project services. No out-of-scope work shall be performed without prior written City approval.

No out-of-scope work shall be performed without prior written City approval. Proposers shall provide standard, after-hours, holiday, emergency, and project hourly rates.

7.1 Cloud and Consumption Costs

Cloud consumption-based services, telecommunications charges, software subscriptions, licensing, and other pass-through costs may be billed separately when specifically identified and approved. Proposers shall disclose all such costs and any administrative markup.

7.2 No Automatic Scope Creep

The Contractor shall not reclassify routine managed-service activities as billable professional services solely because they require troubleshooting, escalation, or specialized expertise. Proposed exclusions must be clearly identified in the proposal.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 13

8. PROPOSAL REQUIREMENTS AND FORMAT

Proposers shall submit a clear, concise proposal in the order below. Failure to provide required information may cause a proposal to be deemed non-responsive.

Section 1 – Letter of Transmittal Signed by an authorized representative; include business type, state of organization, headquarters, authorized representatives, and commitment to perform the services.

Section 2 – Firm Information History, ownership, years in business, size, locations, services, public-sector experience, and relevant certifications.

Section 3 – Understanding and Co-Managed Approach Describe how the Proposer will integrate with City IT staff, divide responsibilities, manage escalation, and avoid duplication.

Section 4 – Technical Scope Response Respond specifically to each subsection of Section 3 and identify included, optional, and excluded services.

Section 5 – Cybersecurity and CJIS Describe MDR/SOC, incident response, security architecture, CJIS experience, personnel screening, access controls, logging, encryption, and compliance approach.

Section 6 – Service Levels Provide response and resolution commitments, escalation paths, after-hours support, and service-credit/remediation approach if offered.

Section 7 – Transition Plan Provide onboarding methodology, milestones, staffing, deliverables, and assumptions.

Section 8 – Project Team Identify key personnel, roles, qualifications, certifications, availability, and subcontractors.

Section 9 – Similar Experience and References Provide at least three similar references, preferably municipal/public-sector and, where applicable, public-safety/CJIS references.

Section 10 – Technology and Tools Identify proposed technology and tools.

Section 11 – Cost Proposal Complete Attachment C and identify all recurring, non-recurring, pass-through, project, and optional charges.

Section 12 – Exceptions and Assumptions Complete Attachment D and identify every exception or assumption.

Section 13 – Required Forms Complete and sign all applicable attachments.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 14

9. COST PROPOSAL REQUIREMENTS

The City intends to structure pricing so that proposals can be compared on a consistent basis. Proposers shall complete Attachment C. Alternative pricing may be provided only as a clearly labeled optional alternative and shall not replace the required cost form.

Unless otherwise stated, recurring prices shall be firm for the initial contract term. Proposers shall identify assumptions concerning user counts, endpoints, servers, network devices, sites, licenses, and other pricing units.

9.1 Required Price Categories

Line Description Monthly Recurring Annual One-Time / Other 1 Onboarding / transition

2 Co-managed IT services (Hours per month?)

3 Other required recurring services

4 Standard professional services hourly rate (for Projects/Out of Scope Work)

— — $________/hr

5 Optional Services/Software

9.2 Pricing Transparency

• Identify all third-party licenses and subscriptions included in the recurring fee.

• Identify all pass-through costs and any markup.

• Identify minimum commitments, minimum quantities, annual increases, and renewal assumptions.

• Identify travel or mileage charges, if any.

• Identify proposed price adjustment methodology for renewal years.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 15

10. EVALUATION AND SELECTION

The City intends to evaluate responsive proposals based on qualifications, technical approach, cybersecurity capability, experience, service model, and cost. The City may request clarification, conduct interviews, request demonstrations, and negotiate with one or more qualified Proposers.

Evaluation Factor Suggested Weight Firm and Team Qualifications / Relevant Experience 25% Co-Managed Technical Approach and Scope Response

25%

Cybersecurity and CJIS Experience 20% Service Levels, Transition and Governance 10% Cost Proposal / Overall Value 20% Total 100%

10.1 Interviews / Demonstrations

The City may invite selected Proposers to participate in interviews or demonstrations. Topics may include ticketing, monitoring, cybersecurity response, reporting, transition, Microsoft 365 administration, backup recovery, and co-managed workflows.

10.2 Negotiations

The City may negotiate final scope, pricing, service levels, and contractual terms with the selected Proposer. If negotiations are unsuccessful, the City may discontinue negotiations and proceed with another qualified Proposer, consistent with applicable law and City procurement requirements.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 16

11. GENERAL RFP CONDITIONS

1. The City reserves the right to reject any or all proposals and to waive minor informalities or irregularities where permitted by law.

2. The City is not obligated to reimburse any Proposer for costs incurred in preparing or presenting a proposal.

3. Proposals shall remain firm for at least sixty (60) calendar days following the proposal opening unless the

City specifies a different period.

4. Late proposals shall not be accepted unless otherwise permitted by applicable law and the solicitation documents.

5. All communications concerning the solicitation shall be directed to the designated City contact.

Unauthorized contact with City Council members, evaluation committee members, or City personnel regarding the solicitation may be grounds for disqualification.

6. Proposers shall disclose material conflicts of interest and any existing relationship with the City that could affect the procurement.

7. The successful Contractor shall comply with all applicable federal, state, and local laws, ordinances, regulations, licensing requirements, and City policies.

8. The Contractor shall not assign or subcontract material portions of the work without prior City approval. The Contractor remains responsible for subcontractor performance.

9. The Contractor shall maintain confidentiality of City information and shall implement reasonable administrative, technical, and physical safeguards appropriate to the sensitivity of City information.

10. The Contractor shall not use City data for advertising, marketing, model training, resale, or any unrelated commercial purpose without the City’s express written authorization.

11. All City data shall remain the property of the City. Upon termination or expiration, the Contractor shall cooperate in returning or securely transferring City data and documentation.

12. Contractor personnel shall comply with applicable City security, access, safety, and facility requirements while on City property.

13. Any required software, tools, agents, or administrative access installed on City systems shall be disclosed and approved as part of the onboarding process.

14. Work shall not begin until a fully executed contract and any required Notice to Proceed or purchase authorization has been issued by the City.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 17

12. CONTRACT REQUIREMENTS

12.1 Initial Term and Renewal

The anticipated initial contract term is one (1) year, with the option for annual renewals at the City’s discretion and subject to appropriation, satisfactory performance, and applicable procurement requirements. Pricing quote for subsequent renewal years will be submitted to the City by June 1.

12.2 Termination

The final contract shall establish termination rights, including termination for convenience and for cause, with a 90-day notice. The City may require an orderly transition period following termination.

12.3 Transition-Out

Upon expiration or termination, the Contractor shall provide reasonable transition assistance, current documentation, credentials and configuration information maintained for the City, asset inventories, open-ticket information, backup status, vendor contacts, and other information reasonably necessary to transition services.

12.4 Insurance

The Contractor shall maintain insurance meeting the minimum requirements established by the City. At a minimum, the proposal shall include evidence of commercial general liability coverage. The City may also require workers’ compensation, automobile liability, professional/technology errors and omissions, and cyber liability insurance appropriate to the services and risk profile.

12.5 Georgia E-Verify

The successful Proposer shall provide any affidavit or documentation required by applicable Georgia law concerning employment eligibility verification, including requirements applicable to public contracts for services.

12.6 Indemnification

The final agreement shall contain indemnification provisions acceptable to the City and consistent with applicable Georgia law.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 18

13. REQUIRED FORMS AND ATTACHMENTS

The following forms shall be completed and returned with the proposal. The City may add, delete, or modify forms before issuance.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 19

ATTACHMENT A – PROPOSER INFORMATION FORM

Legal Business Name:

Business Address:

City / State / ZIP:

Business Type:

State of Organization:

Primary Contact:

Telephone:

Email:

Website:

Years in Business:

Number of Employees:

Georgia Business License No. (if applicable):

Authorized Signer:

Title:

Has the firm ever been suspended, debarred, or excluded from a federal, state, or local government contract?

Yes ___ No ___

If yes, attach an explanation.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 20

ATTACHMENT B – REFERENCES

Provide at least three references for similar services. Public-sector and public-safety/CJIS references are preferred where applicable.

Reference 1 Organization:

Address:

Contact Name / Title:

Telephone:

Email:

Dates of Service:

Scope of Services:

Approximate Annual Contract Value:

Reference 2 Organization:

Address:

Contact Name / Title:

Telephone:

Email:

Dates of Service:

Scope of Services:

Approximate Annual Contract Value:

City of Hinesville – RFP 2026-08 Co-Managed IT Services 21

Reference 3 Organization:

Address:

Contact Name / Title:

Telephone:

Email:

Dates of Service:

Scope of Services:

Approximate Annual Contract Value:

City of Hinesville – RFP 2026-08 Co-Managed IT Services 22

ATTACHMENT C – COST PROPOSAL FORM

Proposer shall complete all applicable lines and attach detailed assumptions. Blank fields may be interpreted as no offer.

Line Description Monthly Recurring Annual One-Time / Other 1 Onboarding / transition

2 Co-managed IT services (Hours per month?)

3 Other required recurring services

4 Standard professional services hourly rate (for Projects/Out of Scope Work)

— — $________/hr

5 Optional Services/Software

Authorized Signature: ____________________________________ Date: __________________

Printed Name / Title: _________________________________________________

City of Hinesville – RFP 2026-08 Co-Managed IT Services 23

ATTACHMENT D – EXCEPTIONS / DEVIATIONS

Proposers shall identify every exception, deviation, assumption, exclusion, or alternative to the RFP requirements. Failure to identify an exception may result in the proposal being evaluated as an unconditional commitment to the stated requirement.

RFP Section Requirement Proposed Exception / Alternative Price / Impact

City of Hinesville – RFP 2026-08 Co-Managed IT Services 24

ATTACHMENT E – CONFLICT OF INTEREST CERTIFICATION

The Proposer shall disclose any actual, potential, or perceived conflict of interest involving the City, its employees, officials, agents, or the proposed Contractor team.

1. Does any current or former City employee hold a financial interest greater than five percent (5%) in the Proposer? Yes ___ No ___ Unsure ___

2. Does any immediate family member of a current or former City employee hold a financial interest greater than five percent (5%) in the Proposer? Yes ___ No ___ Unsure ___

3. Has the Proposer or any principal been suspended, debarred, excluded, or had a public contract terminated for cause? Yes ___ No ___ Unsure ___

If any answer is Yes or Unsure, attach a written explanation.

Certification: I certify that the foregoing is true and correct to the best of my knowledge.

Authorized Signature: ____________________________________

Printed Name / Title: ____________________________________

Date: __________________

City of Hinesville – RFP 2026-08 Co-Managed IT Services 25

ATTACHMENT F – GEORGIA E-VERIFY / IMMIGRATION COMPLIANCE AFFIDAVIT

City of Hinesville – RFP 2026-08 Co-Managed IT Services 26

ATTACHMENT G – NON-COLLUSION AFFIDAVIT

NON-COLLUSION AFFIDAVIT RFP

2026-02

(This Affidavit is Part of the Proposal Documents)

PROPOSAL DATE:

PROJECT DESCRIPTION:

STATE OF GEORGIA

CITY OF HINESVILLE

, being first duly sworn, deposes and says that he/she is (sole owner, partner, president, etc.) of ________________________________, the Company making the foregoing Proposal or Bid; that such Proposal/Bid is genuine and not collusive or sham;

that said Company has not colluded, conspired, connived, or agreed, directly or indirectly, with any other Proposer, Bidder, or person, to put in a sham Proposal/Bid, or that such other person refrain from bidding, and has not in any manner, directly or indirectly sought by agreement or collusion, or communication or conference, with any person, to fix the Proposal/Bid Price of affiant or any other Proposer/Bidder, or to fix any overhead, profit or cost element of said Proposal/Bid Price, or of that of any other Proposer/Bidder, or to secure any advantage against the City, or any person interested in the proposed Agreement; and that all statements in said Proposal/Bid are true; and further, that such Company has not, directly or indirectly submitted this Proposal/Bid, or the contents thereof, or divulged information or data relative thereto to any association or to any member or agent thereof.

Affiant:

Sworn to and subscribed before me this day of , 20 .

Notary Public

City of Hinesville – RFP 2026-08 Co-Managed IT Services 27

ATTACHMENT H – INSURANCE REQUIREMENTS

The following minimums are based on the insurance provisions reviewed in the source materials and are presented for City confirmation before advertisement. The final contract and City risk-management requirements shall control.

Coverage Minimum Requirement Commercial General Liability $1,000,000 per occurrence; $2,000,000 aggregate recommended Automobile Liability $500,000 combined single limit Workers’ Compensation As required by Georgia law Technology / Professional E&O $1,000,000 minimum recommended Cyber Liability $1,000,000 minimum recommended

The Contractor shall provide certificates of insurance before contract execution and maintain required coverage throughout the contract term. Policies shall be issued by insurers authorized to do business in Georgia. The City may require additional insured status or other endorsements where permitted and appropriate.

City of Hinesville – RFP 2026-08 Co-Managed IT Services 28

PROPOSER CERTIFICATION AND EXECUTION

By signing below, the Proposer certifies that it has examined this RFP, understands the requirements, has identified all known exceptions, and agrees that its proposal shall remain valid for sixty (60) calendar days following the proposal opening unless otherwise stated by the City.

The undersigned further certifies that the individual signing this proposal is authorized to bind the Proposer.

Company Name ____________________________________________ Authorized Signature ____________________________________________ Printed Name ____________________________________________ Title ____________________________________________ Date ____________________________________________

END OF REQUEST FOR PROPOSALS