8-RFQ 549635 - DoIT - Crowdstrike Cyber Security.pdf

Revised 12/2/2025

CITY OF DETROIT

OFFICE OF CONTRACTING AND PROCUREMENT

REQUEST FOR QUOTE

RFQ NO. 549635

DoIT - CrowdStrike Cyber Security

Buyer: Jamillah Watkins

EVENT / ACTIVITY DUE DATE / TIME

ADVERTISEMENT DATE Wednesday, September 16th, 2026

QUESTIONS DUE Wednesday, September 23rd, 2026, by 2:00pm

EST

All questions must be submitted online in the

Supplier Portal

QUOTES DUE DATE * Friday, October 16th, 2026 by 3:00pm EST

In the Supplier Portal as specified in this RFQ.

* Respondents must register in Bonfire (EUNA Procurement) to download bid documents and submit bids. The City cannot guarantee the accuracy of any bid documents obtained from outside of Bonfire, and bids submitted outside of Bonfire will not be accepted. Detailed resources about registering and bidding, including video tutorials and live, virtual office hours, are available at www.detroitmi.gov/suppliersupport.

Questions about the specifics of this RFQ must be asked within the Bonfire Messages interface for the bid on or before the date and time indicated above. Questions asked via phone, email, and/or other means will not be answered.

Quotes must be uploaded in Bonfire on or prior to the date and time indicated above. Late and/or emailed quotes will not be accepted.

https://detroit.bonfirehub.com/ http://www.detroitmi.gov/suppliersupport

1. PROJECT REQUEST

The City of Detroit Office of Contracting and Procurement (OCP) on behalf of the Department of

Innovation and Technology (DoIT) requests quotes from qualified Respondents to render certain technical or professional services ("Services") as set forth in this RFQ to provide licensing for cyber security.

2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

The City of Detroit, Department of Innovation and Technology (DoIT) is requesting quotes for industry leading Cyber Security solutions to advance resiliency and fortify security posture.

Awarded Respondent will work with data from several city departments such as Police, Fire, Homeland security, Building and Safety, Health, and other city departments.

It is the responsibility of the Bidder to review General Conditions. In your quotation a distinction between dollars and cents must be made. Also, illegible bids may be grounds for rejection of your bid. All changes made to the bid form altering, price, terms, quote and/or conditions. MUST be crossed out and initialed. Failure to initial any changes will be grounds for rejection of your bid.

3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

If a contract is awarded as a result of this RFQ, it will be a City of Detroit IT Contract (Attachment

E). The term of the contract will be for two (2) years. Any renewal option exercised under this contract is effective only after the approval of the Detroit City Council and signed by the Chief

Procurement Officer. The City anticipates one or multiple awards as a result of the RFQ.

4. STATEMENT OF WORK

The selected supplier will be responsible for providing the items listed on Attachment C – Price

Proposal.

Professional Services Objectives

Respondents shall be capable of providing the following services:

• Threat management and remediation

• Forensic investigation and analysis

• Project management and implementation services

• System configuration based on manufacture’s recommendations

• Data security plan

• Weekly project status calls

• Monthly executive status updates

• Project risk analysis and mitigation

• Issue escalation process

• Respondent-provided staff and technician training

• Consulting on possible automated responses, the true meaning of reviewed incidents, appropriate response, configuration techniques, reporting options, alerting configuration, storage and maintenance tasks.

• Maintenance, monitoring and management of the system, which will be primarily the responsibility of Respondent

• Robust Test Plan including Integration, Load and User Acceptance Testing

• Support and Maintenance Plan which provides for 24/7/365 support to resolve issues

City of Detroit: Security Compliance Requirements

Cryptographic Products. The Federal Information Processing Standards (FIPS) are a set of US

Government security requirements for data and its encryption. FIPS 140-2 requires that any hardware or software cryptographic module implements algorithms from an approved list. The

FIPS validated algorithms cover symmetric and asymmetric encryption techniques as well as use of hash standards and message authentication.

The Health Insurance Portability and Accountability Act of 1996 (HIPAA), Public Law 104-191, included Administrative Simplification provisions that required HHS to adopt national standards for electronic health care transactions and code sets, unique health identifiers, and security.

• Federal Bureau of Investigation (FBI) Criminal Justice Information Systems (CJIS)

Security Policy Version 5.9.2, and any future versions. This includes specific specifications set forth by the state of Michigan.

• Federal Risk and Authorization Management Program (FedRAMP) standardized security assessment and authorization for cloud products and services used by Government agencies.

Service provider and data storage must be based within the United States.

CJI Requirement Highlights

Auditing:

Develop, document, and disseminate to all personnel when their unescorted logical or physical access to any information system results in the ability, right, or privilege to view, modify, or make use of unencrypted CJI:

1. Organization-level awareness and training policy that:

(a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and

(b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and

2. Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls;

(a) Designate organizational personnel with information security awareness and training responsibilities to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and

(b) Review and update the current awareness and training:

• Policy annually and following changes in the information system operating environment, when security incidents occur, or when changes to the CJIS Security

Policy are made;

• Procedures annually and following changes in the information system operating environment, when security incidents occur, or when changes to the CJIS Security

Policy are made.

Auditable Events and Content (Information Systems):

The information system shall generate audit records for defined events. These defined events include identifying significant events which need to be audited as relevant to the security of the information system. The agency shall specify which information system components carry out auditing activities. Auditing activity can affect information system performance, and this issue must be considered as a separate factor during the acquisition of information systems.

The agency’s information system shall produce, at the application and/or operating system level, audit records containing sufficient information to establish what events occurred, the sources of the events, and the outcomes of the events. The agency shall periodically review and update the list of agency-defined auditable events. In the event an agency does not use an automated system, manual recording of activities shall still take place.

Event Logging:

The following events shall be logged:

1. Successful and unsuccessful system log-on attempts.

2. Successful and unsuccessful attempts to use:

a. access permission on a user account, file, directory or other system resource;

b. create permission on a user account, file, directory or other system resource;

c. write permission on a user account, file, directory or other system resource;

d. delete permission on a user account, file, directory or other system resource;

e. change permission on a user account, file, directory or other system resource.

3. Successful and unsuccessful attempts to change account passwords.

4. Successful and unsuccessful actions by privileged accounts.

5. Successful and unsuccessful attempts for users to:

a. access the audit log file;

b. modify the audit log file;

c. destroy the audit log file.

Content:

The following content shall be included with every audited event:

1. Date and time of the event.

2. The component of the information system (e.g., software component, hardware component) where the event occurred.

3. Type of event.

4. User/subject identity.

5. Outcome (success or failure) of the event.

6. Audit Record Retention

The agency shall retain audit records for at least one (1) year. Once the minimum retention time period has passed, the agency shall continue to retain audit records until it is determined they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoenas, and law enforcement actions.

Encryption for CJI at Rest

When CJI is at rest (i.e., stored digitally) outside the boundary of the physically secure location, the data shall be protected via encryption. When encryption is employed, agencies shall either encrypt CJI in accordance with the standard in the CJIS FBI Policy Section 5.10.1.2.1 or use a symmetric cipher that is FIPS 197 certified (AES) and at least 256-bit strength.

1. When agencies implement encryption on CJI at rest, the passphrase used to unlock the cipher shall meet the following requirements:

a. Be at least 10 characters

b. Not be a dictionary word.

c. Include at least one (1) upper case letter, one (1) lower case letter, one (1) number, and one (1) special character.

d. Be changed when previously authorized personnel no longer require access.

2. Multiple files maintained in the same unencrypted folder shall have separate and distinct passphrases. A single passphrase may be used to encrypt an entire folder or disk containing multiple files. All audit requirements found in Federal CJIS Policy as administered by the

State of Michigan Section 5.4.1 Auditable Events and Content (Information Systems) shall be applied.

Personnel Screening Requirements for Individuals Requiring Unescorted.

Access to Unencrypted CJI

1. To verify identification, state of residency and national fingerprint-based record checks shall be conducted by Detroit Police Department prior to granting access to CJI for all personnel who have unescorted access to unencrypted CJI or unescorted access to physically secure locations or controlled areas (during times of CJI processing). However, if the person resides in a different state than that of Michigan, the Respondent shall conduct state (of the agency) and national fingerprint-based record checks and execute a NLETS (National Law

Enforcement Telecommunication System) CHRI IQ/FQ/AQ query using purpose code C, E, or

J via the local Law Enforcement Agency where the purposed bidder resides.

When appropriate, the screening shall be consistent with:

a. Federal CJIS Policy as administered by the State of Michigan: CFR 731.106;

and/or Supplemental Guidance:

• Federal entities bypassing state repositories in compliance with federal law may not be required to conduct a state fingerprint-based record check.

• See Federal CJIS Policy as administered by the State of Michigan Appendix J for applicable guidance regarding non-criminal justice agencies.

It is recommended individual background re-investigations be conducted every five years unless

Rap Back is implemented.

Personnel Termination

Upon termination of personnel by an interface agency, the agency shall immediately terminate access to local agency systems with access to CJI. Furthermore, the interface agency shall provide notification or other action to ensure access to state and other agency systems is terminated.

5. OPERATIONAL INFORMATION

Awarded Contractor(s) will work closely with City agency staff.

The Respondent is expected to provide service in accordance with the terms of the executed contract and under the rules, regulations, and supervision of the City.

6. MINIMUM QUALIFICATIONS

Proposals will only be accepted from those firms demonstrating a minimum of five (5) years of experience providing log monitoring and managed services as requested in the

RFP for projects with cyber security, licensing, and installation. Firm should be able to detail capabilities utilized in other government entities for multiple tenants, including

Public Safety customers. Firms must be familiar and compliant with Michigan CJIS requirements, HIPAA standards, IRS Pub 1075 and other applicable compliance standards. Firms must also provide proof that they have obtained clearance with another law enforcement agency. Products shall be implemented and designed based on best practices and manufacturers’ recommendations.

7. TECHNICAL INFORMATION

Please refer to heading “City of Detroit: Security Compliance Requirements” under Section 4.

STATEMENT OF WORK for information related to Security the City of Detroit’s Security

Compliance standards. Further information related to the City’s technical environment will be discussed with the selected Respondent.

The City of Detroit is committed to centralizing and warehousing data for the purpose of improving service delivery and enabling cross departmental analytics. For this reason, we expect Contractors, contractual relationships, and resulting software platforms to enable data access, data interoperability, warehousing of resulting data, and adherence to City data standards.

Specifically, the City minimally requires:

• Access to any data via APIs in a machine-readable format.

• Full documentation of APIs (including field names and objects) and the database schema used by the application.

• Ability for City to push data as needed to these software systems to update base datasets.

• Any location-based data or platform utilizes the City’s Base Units geocoder, Base Units

Database, and/or address data standards as applicable. For more information see: https://base-units-detroitmi.hub.arcgis.com/pages/about-base-units

• The ability for the City to use and govern this data as it deems necessary-

- centralizing it, porting it into other systems, and using it for additional and future organizational needs.

The City prefers:

• System or platform has the capacity to store field-level metadata and display it in the user interface when appropriate

• API is able to provide data in a JSON format.

• Data system or data exports integrate easily with ESRI products including feature services.

• Systems or platforms that support data exchanges (pushes and pulls) that can happen dynamically.

Specifications, Change of Specification, and Errors or Omission. Specifications which refer to brand names are given for reference. Respondents may quote on equivalent articles, provided that brand name and catalog number(s) and any deviations are noted on the bid form and complete descriptive literature is furnished. Exceptions will state “Do Not Substitute.”

The decision of the City shall be final.

8. QUESTION DEADLINE

All questions regarding the RFQ shall be submitted through the Supplier Portal no later than the time and date specified on the Cover Page. In the interest of transparency, only written questions will be accepted. Answers to questions will be posted within the Supplier Portal. The

City of Detroit does not guarantee a response to questions not submitted after the question deadline.

Should a Respondent be in doubt as to the true meaning of any portion of this RFQ or find any patent ambiguity, inconsistency, or omission herein, the Respondent must make a written request for an official interpretation or correction in accordance with the instructions for submitting questions as specified in this RFQ.

https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbase-units-detroitmi.hub.arcgis.com%2Fpages%2Fabout-base-units&data=04%7C01%7CSteve.Motz%40detroitmi.gov%7Ca9e347e5722d45e2ae4608d9d5eac148%7Ce154a7601d2d4ef68fd3ebc8b4ef31fd%7C0%7C0%7C637776026508682453%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0pftv3x0FzYBOcb2Ej7bpv8I8ultjXZ0%2FaQYBam8fTc%3D&reserved=0 http://www.michigan.gov/SIGMAVSS

Respondents are advised that no oral interpretation, information or instruction by an officer or employee of the City of Detroit shall be binding upon the City of Detroit.

Respondents requesting changes to the RFQs terms and conditions, specifications, quantities, etc.;

or if clarifications are needed, must make the request in writing by the stated bid submission deadline.

9. REJECTIONS, MODIFICATIONS, CANCELLATIONS

The City of Detroit expressly reserves the right to:

1) accept or reject, in whole or in part, any and all quotes received;

2) waive any non-conformity;

3) re-advertise for quotes;

4) withhold the award for any reason the City determines;

5) cancel and/or postpone the request for quotes, in part or in its entirety, and/or,

6) take any other appropriate action that is in the best interest of the City.

This RFQ does not commit the City of Detroit to award a contract, to pay any cost incurred in the preparation of quotes under this request, or to procure or contract for services.

10. PROTESTS

Protests can be filed with the Office of Procurement. Interested parties aggrieved by a solicitation or the award of any resulting contract may file written notice of protest to the following:

City of Detroit Chief Procurement Officer

2 Woodward Avenue, Suite 1008

Detroit, MI 48226

“Procurement Protest”

At a minimum, such protests shall include:

1) name of protestor.

2) solicitation/contract number and description; and

3) statement of grounds for protest (reference specific text in the solicitation, bid or contract document that is at issue).

The decision of the Chief Procurement Officer and/or the Department Director are final and is not subject to appeal.

11. INVOICES

Vendors must be registered in City of Detroit Vendor Portal and be a registered vendor with the

City of Detroit to submit invoices and receive payments. Go to http://www.detroitmi.gov/Supplier to register.

AUTHORIZATION TO COMMENCE WORK OR SHIP GOODS – READ

CAREFULLY!!!

Contractors may begin work or ship goods upon receipt of the required authorization, which is the CPA (Contract Purchase Agreement), in addition to SPO (Standard Purchase Order), from

Procurement.

http://www.detroitmi.gov/Supplier

The CPA (City Council Approved and Awarded Contract Purchase Agreement) alone is NOT authorization to begin work! NO letter of Intent, or Letter to Commence Work will be issued.

**Work commencing without issuance of the SPO is subject to Payment Delays and/or Non-

Payment! **

Required vendor steps to invoice:

1) Invoices should NOT be uploaded until the Contractor receives confirmation of review and approval from the City of Detroit.

2) Vendors should submit their invoices via City of Detroit Vendor Portal. Portal invoice amount and creation date must match the date on attached invoice. Please follow the below invoice requirements:

Invoice MUST contain or have as attachment:

• Vendor Name and address on Invoice

• Contact Info on Invoice (Accounts Receivable contact with phone and email)

• Remittance information (MUST be included, or the invoice is subject to rejection

• City of Detroit contact (person who authorized work to commence)

• Invoice Date

• Date of service/delivery

• Contract number

• Purchase order number

• Total Invoice amount

Other invoice requirements:

• Invoice must be billed based on Purchase Order rates

• Total invoice amount must tie to the total supporting documents

• Supporting documentation must be attached to the invoice in the portal

Terms are standard NET 30 Days, unless otherwise negotiated, and start from the invoice receipt date, provided that the invoice is submitted timely to our AP department with the necessary supporting documentation.

If you need assistance, please contact the Office of Departmental Financial Services (ODFS) 313-

410-7804.

12. PREVIOUS EXPERIENCE

The City’s experience with the bidder on previous contracts will be considered in determining the award.

13. MISCELLANEOUS

It shall be the responsibility of the Respondent to thoroughly familiarize themselves with the provisions of these specifications. After executing the contract, no consideration will be given to any claim of misunderstanding.

The Respondent agrees to abide by the rules and regulations as prescribed herein by the City as the same now exists or may hereafter from time to time be changed in writing.

Contractors are encouraged to contract with small and minority businesses, women's business enterprises, labor surplus area firms and Detroit businesses. The City strongly encourages the hiring of Detroit residents whenever possible by contacting Detroit At

Work for your hiring needs. Visit the Detroit At Work website at www.detroitatwork.com for specific contact information regarding these opportunities.

14. GENERAL CONDITIONS:

It is the responsibility of the Bidder to review General Conditions located on the City of Detroit’s website.

1. GENERAL CONDITIONS

It is the responsibility of the Bidder to review General Conditions. In your quotation a distinction between dollars and cents must be made. Also, illegible bids may be grounds for rejection of your bid. All changes made to the bid form altering, price, terms, quote and/or conditions. MUST be crossed out and initialed. Failure to initial any changes will be grounds for rejection of your bid. CORRECTION FLUID IS NOT ACCEPTABLE.

2. LOCAL PREFERENCE CONDITIONS

It is the responsibility of the Bidder to review the Local Preference Conditions attached to this bid and comply with all requirements therein.

3. MINOR DEVIATIONS

Specifications referred to herein are used to indicate desired type, and/or construction, and/or operation. Other products and/or services may be may be offered if deviations from specifications are minor and if all deviations are properly outlined and stated in the bid document. Failure to outline all deviations will be grounds for rejection of your bid.

The decision of the City of Detroit, acting through the Chief Procurement Officer, shall be final as to what constitutes acceptable deviations from specifications.

4. RENEWAL

The proposed agreement may be renewed per contract terms. Both parties must agree to an extension under the same terms and conditions as exist in the then current contract.

5. AWARD

One or multiple Awards will be made on a low bid basis, as determined by the City of

Detroit. Blank spaces are considered to be no offer. The City of Detroit reserves the right to delete any item(s) from the award. The City of Detroit reserves the right to limit the amount of the award per contractor.

5.01 STANDBY AWARD

In the case of a single award, the City of Detroit reserves the right to make an award to the second low bidder, on a standby basis. This vendor will be used in the event the successful bidder cannot furnish the quantities and /or services needed in accordance with the delivery requirements of the City of Detroit.

All awards are subject to Ordinance No. 15-00.

6. TERMINATION OF CONTRACT

http://www.detroitatwork.com/

At any time during the contract the City may terminate the agreement for reason of poor or deficient work performance, inability of the Contractor to reason of poor or deficient work performance, inability of the Contractor to supply trained competent technicians, or lack of service as described in this agreement by giving a 10-calendar day notice in writing. EITHER party may terminate the agreement by giving a 30-calendar day written notice to terminate.

7. TERMINATION OF CONTRACT

The City reserves the absolute right to terminate this contract in whole or in part, for the convenience of the City at its sole discretion on thirty (30) days written notice to the

Vendor.

8. SPECIFICATION CHECK

We have read the specifications thoroughly and we:

( ) Are able to meet specifications without deviation.

( ) All deviations are properly outlined on an attached sheet marked

________________ for identification.

SIGNED: __________________________________________

TITLE: ___________________________________________

9. PRICE

All prices quoted are to be FIRM.

The USED EQUIPMENT will also be available for Outright Purchase, as per the enclosed Yellow Sheet, which applies to the outright purchase of the USED

EQUIPMENT ONLY.

INSPECTION: The above used equipment may be inspected Monday through Friday between the hours of 8:00 P.M. - 4:00 P.M. at:

(Using Dept.) «Contract Location Name»

(Contact) _______________________________________________

(Telephone No.) ________________ to arrange for an appointment.

Used Equipment, available for Trade-In as follows:

10. ORDER QUANTITIES

Actual quantities ordered will be contingent on funds available at time of purchase. The

City of Detroit reserves the right to reduce quantities if price quoted exceeds budgetary limitations or to increase quantities if funds are available.

11. ADDITIONAL PURCHASES

( ) We agree

( ) We DO NOT agree to accept additional purchase orders from the City of Detroit for additional units at the same prices and under the same terms and conditions, for a period of one year after date of bid opening.

12. INSURANCE (use the insurance matrix related to your commodity)

The successful bidder must furnish Property Damage Insurance in the sum of

$100,000.00, Commercial General Liability (Bodily Injury) insurance in the sum of

$300,000.00 minimum, or contractor's standard policy, if equal or exceeding limits, and

Workmen's Compensation; City of Detroit shall be named as additionally insured on

Commercial General Liability Insurance Policies.

13. CONTRACT ACCEPTANCE

The successful bidder shall be notified of the execution of a contract by the City of

Detroit upon issuance of a "Contract Award Notice" or a Purchase Order. The "Contract

Award Notice" shall contain the date the contract award was approved.

The signed, accepted bid of the successful bidder will be the contract between the bidder and the City of Detroit, containing the full description of all contractual terms and conditions. A copy of your signed bid will not be mailed to you. Each bidder shall keep a copy of his/her signed bid form for future reference.

14. INSURANCE

14.01 The Contractor shall maintain at its expense during the term of this contract, the following insurance:

14.01.1 Worker’s Compensation insurance with Michigan statutory limits and

Employer’s Liability insurance with limits of $500,000.00 each accident, $500,000.00 each disease, $500,000.00 each disease/each employee. For

Federal and State Funded Training Programs and etc., is required to secure insurance for worker’s compensation for all of its participants and

The City of Detroit should also be listed as an additional insured.

14.01.2 Commercial General Liability insurance with a combined single limit of

$1,000,000.00 per occurrence subject to a minimum aggregate limit of

$2,000,000.00

14.01.3 Automobile Liability insurance covering all owned, hired and non-owned vehicles with personal protection insurance and property protection insurance to comply with the provisions of the Michigan No-

Fault Insurance Act, including residual liability insurance with a minimum combined single limit of $1,000,000.00. Include MCS90 endorsement (if hazardous waste will be transported by vendor’s auto) with minimum property damage limits of $1,000,000.00 each occurrence.

14.02 If during the term of this contract, changed conditions or other pertinent factors, should in the reasonable judgment of the City, render inadequate the insurance limits, the Contractor will furnish on demand such additional coverage as may reasonably be required under the circumstances. All such insurance shall be effected at the contractor's expense, under valid and enforceable policies.

14.03 All policies shall name the Contractor as the insured and shall be accompanied by a commitment from the insurer that such policies shall not be canceled or reduced without at least thirty (30) days' prior notice to the City. The Commercial General Liability insurance policy shall name the City as an additional insured. Certificates of insurance evidencing such coverage shall be submitted to the Finance Department, Office of Contracting and Procurement, prior to the commencement of performance under this contract and at least fifteen (15) days prior to the expiration dates of expiring policies.

15. BID WITHDRAWAL

No bid shall be withdrawn for 90 days from submission deadline. Bidders may reduce this period if stated on bid, but such bids may be rejected on the basis of the reduced time period.

This paragraph supersedes paragraph 14 of the General Conditions.

16. EQUALIZATION FACTOR

Per Section 17-5-12 (c)(1) of the Detroit City Municipal Code, “The bidder that makes the lowest bid, as evaluated or scored, shall be deemed the lowest equalized bidder. If the lowest equalized bid is evaluated or scored below the lowest responsible bid submitted, the lowest equalized bidder shall be awarded the contract, provided that, the contract awarded to such bidder shall not exceed, more than 12 percent above the lowest responsible bid submitted, or $100,000.00, whichever is less.”

The firm making the lowest responsive, responsible bid evaluated according to the

Equalization Allowance Table* shall be deemed the lowest bidder. (see Equalization

Credit Statement).

Vendors who wish to receive Equalization credit for bids submitted must submit their

CRIO-issued Detroit Based Business certificate with their bid document to substantiate eligibility. The CRIO certificate must be submitted with each and every bid response submitted by the vendor. Failure to submit the CRIO certificate will result in equalization credit not being applied to your bid.

17. ALTERNATE BID

Additional bids submitted on brands other than the brands referenced in the specification shall clearly be labeled (ALTERNATE). Alternate bids submitted will be at no cost to the city of Detroit. The decision of the City of Detroit, acting through the Chief

Procurement Officer, shall be final as to what constitutes an acceptable alternate from specifications.

18. PATENTS. The Contractor shall protect and indemnify the City against expense of any nature, shall bear the cost of any lawsuits which may arise and shall pay damages which may be awarded against the City for the use, under this specification, of any patented device, process, apparatus, material or invention.