7-RFP 545272 - CRIO - Cannabis Licensing Software.pdf

City of Detroit Office of Contracting and Procurement (OCP)

Request for Proposal – 545272

CRIO – Cannabis Licensing Software

Revised 12/2/2025 Page 1 of 17

CITY OF DETROIT

OFFICE OF CONTRACTING AND PROCUREMENT

REQUEST FOR PROPOSALS

RFP NO. 545272

Buyer: Jamillah Watkins

EVENT / ACTIVITY DUE DATE / TIME

ADVERTISEMENT DATE Monday, April 27th, 2026

QUESTIONS DUE Monday, May 11th, 2026, by 2:00pm EST

All questions must be submitted online in the Supplier Portal as indicated in Section

3.3 of this RFP.

PROPOSAL DUE DATE * Wednesday, May 27th, 2026 @ 3:00pm

EST

In the Supplier Portal as specified in

Section 4.5 of this RFP.

* Respondents must register in EUNA Bonfire to download bid documents and submit bids. The

City cannot guarantee the accuracy of any bid documents obtained from outside of EUNA, and bids submitted outside of EUNA 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 RFP must be asked within the EUNA 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.

Proposals must be uploaded in EUNA Bonfire on or prior to the date and time indicated above.

Late and/or emailed proposals will not be accepted.

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

Revised 12/2/2025 Page 2 of 17

TABLE OF CONTENTS

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

Section 2. Statement of Work

2.1. SERVICES TO BE PERFORMED

2.2. OPERATIONAL INFORMATION

2.3. TECHNICAL INFORMATION

Section 3. Proposal Evaluation and Selection Process

3.1. MINIMUM QUALIFICATIONS

3.2. ADHERENCE TO TERMS OF PROPOSALS

3.3. QUESTION DEADLINE

3.4. EVALUATION CRITERIA

3.5. EVALUATION PROCEDURE

3.6. ORAL PRESENTATION/DEMONSTRATION

3.7. REJECTIONS, MODIFICATIONS, CANCELLATIONS

3.8. PROTESTS

Section 4. Required Proposal Content and Submission Process

4.1. ACCURACY AND COMPLETENESS OF INFORMATION

4.2. REQUIRED PROPOSAL CONTENT AND FORMAT

4.3. REQUIRED COST PROPOSAL

4.4. ECONOMY OF PREPARATION

4.5. SUBMITTAL INSTRUCTIONS

Section 5. General Conditions and Requirements for RFP

5.1. CONTRACT APPROVAL

5.2. PAYMENT

5.3. INVOICES

5.4. ASSIGNMENT

5.5. MODIFICATION OF SERVICES AFTER CONTRACT APPROVAL

5.6. NEWS RELEASE

5.7. MISCELLANEOUS

5.8. OFFICE OF INSPECTOR GENERAL

RFP Attachments List

Revised 12/2/2025 Page 3 of 17

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

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

Rights, Inclusion and Opportunity Office of Cannabis Affairs (CRIO/OCA) requests proposals from qualified Respondents to render certain technical or professional services ("Services") as set forth in this RFP to provide the development and maintenance of a comprehensive licensing software platform for the City’s marijuana licensing program. The Software will streamline and automate the licensing and renewal processes, ensuring efficient management of various marijuana licenses issued by the City of Detroit.

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

The Office of Cannabis Affairs (OCA) oversees cannabis business licensing with a focus on efficiency, transparency, and customer service to maintain a thriving, compliant, and responsible business community. Moreover, the OCA connects Detroiters and social equity applicants with technical and educational resources, as well as employment and networking opportunities. The

OCA also manages the social equity fund for economic development initiatives developed from statutory cannabis revenue sharing, which is intended to support very low-income entrepreneurs and justice-impacted individuals. Additionally, the OCA advocates for cannabis policies, regulations, and laws that align with the City of Detroit's mission and promotes a safe and healthy family-and-business-friendly cannabis environment in the City of Detroit.

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

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

E). The term of the contract will be for two (2) years with two (2) one-year renewal term options.

Any renewal option exercised under the Contract is effective only after the approval of the Detroit

City Council and the signature of the Chief Procurement Officer. The City anticipates one or multiple awards as a result of the RFP.

Revised 12/2/2025 Page 4 of 17

Section 2. Statement of Work

2.1. SERVICES TO BE PERFORMED

The successful proposer will be required to develop and maintain a comprehensive licensing software platform for the City. The Software will streamline and automate the licensing processes, ensuring efficient management of various marihuana licenses and permits issued by the City of

Detroit.

The successful proposer will be required to conduct a thorough analysis of the City of Detroit's marihuana licensing requirements. This will involve meetings with key stakeholders, understanding existing processes, and identifying pain points and opportunities for improvement.

Software Design and Development:

Based on the gathered requirements, the successful proposer will design and develop the Software.

The Software must include the following key features and functionalities:

• Online Application Portal: A user-friendly web-based portal allowing applicants to submit marihuana license/permit applications electronically.

• Workflow Automation: Automated routing and approval processes to streamline the application review and approval process.

• Document Management: Secure storage and retrieval of supporting documents associated with license applications.

• Payment Integration: Integration with secure payment gateways to facilitate online fee payments.

• Renewal and Expiration Management: Automated reminders and notifications for license renewal and expiration dates.

• Reporting and Analytics: Comprehensive reporting capabilities to generate insights and track licensing activities.

• User Management: Role-based access control to ensure appropriate access levels for different user groups.

• Integration Capabilities: Ability to integrate with existing systems, such as City of

Detroit databases or CRM systems, as required.

• Payment Card Industry (PCI) Compliant: The Software must be PCI Compliant.

• Customer access to accounts and internal and external messaging required

User Acceptance Testing (UAT):

The successful proposer will be required to conduct thorough testing of the Software in collaboration with City of Detroit representatives. UAT will validate the Software’s functionality, usability, and performance, ensuring it meets the City of Detroit’s functional requirements and expectations.

Deployment and Training:

The successful proposer will be required to oversee the deployment of the Software into the City of Detroit's infrastructure. The successful proposer must provide comprehensive training on operation and use of the Software. Training materials, user manuals, and documentation will be provided to ensure smooth adoption and usage.

Revised 12/2/2025 Page 5 of 17

Ongoing Maintenance and Support:

The successful proposer will be required to provide ongoing maintenance and support services to ensure the platform's optimal performance. This will include bug fixes, updates, and enhancements.

Additionally, a dedicated support channel must be established to address any technical issues or queries experienced by the City of Detroit staff.

Project Management:

The successful proposer will assign a project manager responsible for overseeing the entire

Contract lifecycle. The project manager will regularly communicate with the City of Detroit representatives, provide status updates, and ensure timely delivery of the project milestones.

Timeline and Deliverables:

The successful proposer will be required to provide a detailed project plan with defined milestones, deliverables, and associated timelines. Regular progress reports will be shared with the City of

Detroit to track the project's status.

2.2. 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.

2.3. TECHNICAL INFORMATION

Creating the Software will involve various technical aspects. The following features the key technical information and considerations for this project:

Software Architecture:

Define the overall Software architecture, including the choice of technology stack, such as programming languages, frameworks, and databases. Consider scalability, maintainability, and security aspects when designing the architecture.

User Interface (UI) Design:

Design an intuitive and user-friendly UI that enables easy navigation and efficient completion of licensing and compliance-related tasks. Consider responsive design principles to ensure compatibility across different devices and screen sizes.

Software Development:

Develop the software application using appropriate programming languages and frameworks based on the chosen architecture. Implement features such as user registration, login/authentication, application submission, workflow management, document storage, reporting, and integration capabilities.

Data Management:

Establish a robust database schema to store licensing and compliance-related data securely.

Determine the data model, relationships, and data storage requirements based on the application's functionality. Implement data validation, integrity checks, and data privacy measures.

Revised 12/2/2025 Page 6 of 17

Workflow Automation:

Implement workflow management capabilities to automate the routing and approval processes involved in license applications. Define the workflows, roles, and permissions to ensure the appropriate stakeholders are involved in the review and approval process.

Payment Integration:

Integrate with secure payment gateways to enable online fee payments for license applications.

Implement secure communication protocols and encryption mechanisms to protect sensitive payment information.

Document Management:

Develop a document management system to store and manage supporting documents associated with license applications. Implement features such as document upload, storage, retrieval, versioning, and access control to ensure document security and compliance.

Reporting and Analytics:

Implement reporting functionalities to generate comprehensive reports and analytics related to licensing and compliance activities. Design and develop customizable reports, dashboards, and data visualization components to provide insights and track performance.

Integration Capabilities:

Determine the integration requirements with external systems, such as municipality databases, CRM systems, or payment gateways. Implement APIs or integration mechanisms to exchange data securely and seamlessly between the licensing software application and other systems.

Security and Compliance:

Implement robust security measures to protect sensitive data, prevent unauthorized access, and ensure compliance with data protection regulations. Implement encryption, secure authentication, role-based access control, and audit trails to maintain data integrity and security.

Testing and Quality Assurance:

Conduct thorough testing, including functional testing, integration testing, performance testing, and security testing, to ensure the software application meets the required quality standards. Implement automated testing frameworks and practices to streamline testing processes.

Deployment and Hosting:

Plan the deployment strategy, including infrastructure requirements, server configurations, and cloud hosting options. Ensure scalability, high availability, and disaster recovery measures to maintain uninterrupted access to the licensing and compliance software application.

Maintenance and Support:

Provide ongoing maintenance and support services to address bug fixes, performance optimizations, updates, and enhancements. Establish a support mechanism to address user inquiries, technical issues, and provide regular software updates.

These technical considerations are essential in building the Software application that meets the

City's requirements and ensures efficient management of marihuana licensing processes.

Revised 12/2/2025 Page 7 of 17

DELIVERABLES:

Software Development: The successful proposer will be required to design, develop, and implement a robust licensing Software capable of checking and validating over 15 types of documents. The Software will be designed to handle large volumes of data and ensure high performance and reliability.

User Profile Management: The Software must feature a user profile system, where applicants can create personal accounts, upload required documents and track their submission history. This feature will allow users to review all their submissions over time and maintain a complete record of their applications.

Document Verification System: The Software must be equipped with a comprehensive document verification system that will review the validity of the documents uploaded by the users. It must be able to check for authenticity and completeness, ensuring that all necessary information is present and accurate.

Security and Privacy: The Software will ensure the utmost security and privacy of the user's data.

It will comply with all relevant data protection and privacy laws and regulations, as well as the data protection and use provision included in the contract (as hereinafter defined). Encrypted data transmission and secure storage solutions must be employed to protect sensitive data.

Technical Support and Maintenance: The successful proposer will be required to provide ongoing technical support and maintenance services post-deployment. These services will include troubleshooting, Software updates, security patches, and system enhancements to ensure Software performance and reliability over time.

Training and Documentation: The successful proposer will be required to provide necessary training to the City's team to effectively operate and use the Software. Comprehensive user manuals and documentation must also be provided to aid in understanding the software's functionalities.

Feedback and Improvement: The successful proposer will regularly monitor user feedback and make necessary improvements to the Software. This will ensure that the Software continues to meet the needs of its users and remains user-friendly and efficient.

Revised 12/2/2025 Page 8 of 17

Section 3. Proposal Evaluation and Selection Process

3.1. MINIMUM QUALIFICATIONS

In addition to the outlined scope of services to be performed, the selected contractor must meet the following requirements:

1. Experience: The contractor must have at least three to five (3-5) years of experience successfully implementing and managing payment platforms for at least three (3) municipalities or government entities of similar or larger size than the City of Detroit.

2. Functional capability and user interface: the contractor must be able to provide elite, effective, and efficient customer and back-end user functionality, including items described in the scope of services to be performed.

3. Financial Stability: The contractor must have a strong financial position and be able to demonstrate financial stability.

4. Security: The contractor must maintain robust security measures to protect sensitive financial information.

5. Customer Service: The contractor must provide excellent customer service and be able to handle inquiries and disputes promptly.

3.2. ADHERENCE TO TERMS OF PROPOSALS

A proposal, once accepted by the City of Detroit, may become a binding contractual obligation of the Respondent. The failure of a successful Respondent to accept this obligation and to adhere to the terms of the Respondent’s proposal may result in rejection of the proposal and the cancellation of any provisional award to the respondent. Respondents are not permitted to take advantage of any errors or omissions in specifications since full instructions will be given should they be discovered before bid submission date.

3.3. QUESTION DEADLINE

All questions regarding the RFP shall be submitted through the Supplier Portal no later than the time and date specified in the solicitation. 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 submitted after the question deadline.

Should a Respondent be in doubt as to the true meaning of any portion of this RFP 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 RFP.

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 RFPs terms and conditions, specifications, quantities, etc.;

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

http://www.michigan.gov/SIGMAVSS

Revised 12/2/2025 Page 9 of 17

3.4. EVALUATION CRITERIA

Technical Proposals will be evaluated before Cost Proposals are reviewed.

Proposal Evaluation Criteria Possible

Points

1. Respondent Experience / Organization 15

2. Respondent Approach & implementation Plan 20

3. Technical Requirements & Deliverables 60

4. Pricing 5

Total Points Possible 100

Detroit Equalization Credits according to the following table shall be applied after the technical and price evaluation. (Please see Equalization Credit Statement for more information)

Detroit Equalization Credits – Prime Contractor Possible

Points

Detroit Headquartered Business 5

Detroit Based Business 2

Detroit Resident Business 5

Detroit Small Business 1

Detroit Micro Business Concern 2

Joint Venture 2

Mentor Venture 1

Business can only be either a Detroit Small Business or Detroit Micro Business Concern but not both. Business can only be a Joint Venture or a Mentor Venture but not both.

Detroit Equalization Credits – SubContractor Possible Points

Detroit Headquartered Business 5 x % of work

Detroit Based Business 2 x % of work

Detroit Resident Business 5 x % of work

Detroit Small Business 1 x % of work

Detroit Micro Business Concern 2 x % of work

Maximum Points Possible 10

3.5. EVALUATION PROCEDURE

Following the receipt of proposals, a City designated Evaluation Committee will evaluate each response. All PROPOSALS, which meet the required format of this RFP, will be evaluated. Any proposals determined to be non-responsive to the specifications or other requirements of the RFP, including instructions governing submission and format, will be disqualified unless the City determines, in its sole discretion, that non-compliance is not substantial or that an alternative proposed by the Respondent is acceptable.

Revised 12/2/2025 Page 10 of 17

The City may also, at its discretion, request oral presentations, make site visits at Respondent’s facility and may request a demonstration of Respondent’s operations. If scheduled, a final determination will be made after the oral presentations and/or demonstrations are complete.

The City may also at its sole discretion, elect to rank order the qualified proposals, and negotiate with some limited number of the highest scored qualified respondents. A final determination would include the cumulative inputs of this evaluation procedure. All decisions reached by the Evaluation

Committee will be by consensus.

Any of the additional data specs and standards described in Section 2.3 that are met will be factored positively into the overall score.

3.6. ORAL PRESENTATION/DEMONSTRATION

The City reserves the right, at its own discretion, to request oral presentations regarding proposals submitted in response to the RFP. Failure to make an oral presentation will be grounds for rejection of your proposal. Respondents will be notified by the Office of Contracting and Procurement of the date, time and location for oral presentations.

3.7. REJECTIONS, MODIFICATIONS, CANCELLATIONS

The City of Detroit expressly reserves the right to:

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

2) waive any non-conformity;

3) re-advertise for proposals;

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

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

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

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

3.8. PROTESTS

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

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).

Revised 12/2/2025 Page 11 of 17

An actual or prospective bidder or offeror whose direct economic interest would be affected by the award of a contract or the failure to award a contract has the right to protest any aspect of the solicitation, evaluation, or selection process of a City of Detroit procurement.

A protest by a prospective bidder which challenges the terms of the solicitation itself must be received by the City no later than 4:00 p.m. EST of the business day prior to the date scheduled for the bid closure. Failure to meet this deadline shall result in a protester waiving its ability to challenge the terms of the solicitation.

A protest by a bidder which challenges a contract award must be received no later than 4:00 p.m.

EST five (5) business days after the award of a City procurement. Failure to meet this deadline shall result in a protester waiving its ability to challenge the contract award.

All protests must be submitted in writing and received by the required timeframe.

The Chief Procurement Officer (CPO), or as delegated, the Deputy CPO, has the sole authority to respond to, decide and act upon supplier protests.

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

Revised 12/2/2025 Page 12 of 17

Section 4. Required Proposal Content and Submission Process

4.1. ACCURACY AND COMPLETENESS OF INFORMATION

All information pertaining to the prospective respondent’s approach in meeting the requirements of the RFP shall be organized and presented in the prospective respondent’s proposal. The instructions contained in this RFP must be strictly followed.

Accuracy and completeness are essential. Omissions and ambiguous or equivocal statements will be viewed unfavorably and may be considered in the evaluation. Since all or a portion of the successful proposal may be incorporated into any ensuing contract, all prospective respondents are further cautioned not to make any claims or statements that cannot be subsequently included in a legally binding agreement.

4.2. REQUIRED PROPOSAL CONTENT AND FORMAT

To be considered responsive, each proposal must, at a minimum, respond to the following RFP sections in their entirety, responses must be uploaded in the Supplier Portal along with the Affidavit of Disclosure Interests Form and Non- Collusion Affidavit found under requirements section of the of RFP#545272:

Required Response Item

1. Attachment A – Respondent Questionnaire

Respondent shall provide their Organization Experience, per the requirements provided in

Attachment A.

2. Attachment B – Proposal Introduction and Solution / Approach

Respondent shall provide their Proposal Introduction and Solution / Approach and

Capacity/Staffing, per the requirements provided in Attachment B.

3. Attachment C – Pricing Matrix

Respondent shall provide their Pricing proposal, per the requirements provided in

Attachment C.

4. Attachments D1 & D2 – Forms, Affidavits and Documents – Bid Requirements

Respondent will be required to provide completed Forms, Affidavits, Insurance and

Documents, Financial Statements (from last 3 years), and, if applicable, the completed

Acknowledgement of any RFP Amendments.

5. Attachment E – Model Professional Services Contract

Respondent shall provide their agreement to the Model Professional Services Contract or note any exceptions provided in Attachment E.

4.3. REQUIRED COST PROPOSAL

Respondents are requested to make a firm cost proposal to the City of Detroit, through the completion of Attachment C. If a contract is entered into as a result of this RFP, it will be a contract for fees as related to providing all requested services, with a price not to exceed the total price quoted in the proposal. The City of Detroit reserves the right to select proposals from the most responsible Respondents with the most reasonable costs. The City reserves the right to select one or more firms to perform all or separate parts of this function.

Revised 12/2/2025 Page 13 of 17

4.4. ECONOMY OF PREPARATION

Proposals should be prepared simply and economically providing a straightforward, concise description of the Respondent’s ability to meet the requirements of the RFP. Emphasis should be on the completeness and clarity of content.

4.5. SUBMITTAL INSTRUCTIONS

All proposals must be submitted through the Bonfire/EUNA Procurement Supplier Portal at detroit.bonfirehub.com. Each Respondent is responsible for ensuring that its proposal is received by the City on a timely basis. Faxed or mailed proposals will not be accepted.

Firms shall not distribute their proposals to any other City office or City employee. Proposals received become the property of the City. The City is not responsible for any costs associated with preparation or submission of proposals. All proposals submitted by the due date will be recorded in the Supplier Portal. Responses received will not be available for review. Proposals received will be subject to disclosure under the state of Michigan’s Freedom of Information Act. An officer of the company authorized to bind the company to a contractual obligation with the City must sign the proposals in the Supplier Portal. The successful respondent will receive an award letter.

Respondents who are not awarded will receive a notification that the award decision has been made.

Support Channels for Technical Difficulties and Questions

Visit https://detroitmi.gov/suppliersupport for:

- Guides on how to register in EUNA

- Guides on how to submit a response to the solicitation

- FAQs

Contact Bonfire’s technical support in the portal for:

- Technical issues with the e-bidding portal

- Registration problems

- Help submitting responses through the system

Contact the City (eprocurement@detroitmi.gov) for:

- General procurement process questions

- City-specific requirements and policies

For Solicitation/Project-Specific Questions:

- Submit all solicitation-related questions through the Public Q&A tab in the Bonfire/EUNA

Procurement portal. This ensures all vendors receive the same information and maintains transparency in the bidding process. Emails and calls regarding solicitation-specific questions will not receive a response.

https://detroitmi.gov/suppliersupport https://detroit.bonfirehub.com/portal/support mailto:eprocurement@detroitmi.gov

Revised 12/2/2025 Page 14 of 17

Section 5. General Conditions and Requirements for RFP

5.1. CONTRACT APPROVAL

Upon contract award, the City and the successful Respondent shall execute a professional services contract, which shall contain all contractual terms and conditions in a form provided by the City.

No contract shall become effective until the contract has been approved by the required City

Departments and Detroit City Council and signed by the City of Detroit Chief Procurement Officer.

Prior to the completion of this approval process, the successful Respondent shall have no authority to begin work under the contract. The Chief Financial Officer shall not authorize any payments to the successful Respondent prior to such approvals; nor shall the City incur any liability to reimburse the successful Respondent regarding any expenditure for the purchase of materials or the payment of services.

5.2. PAYMENT

All properly executed invoices submitted by the successful Respondent will be paid in accordance with the City of Detroit Prompt Payment Ordinance.

5.3. 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.

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) Vendors should submit their invoices via City of Detroit Oracle Vendor Portal.City of

Detroit Oracle Vendor Portal. Portal invoice amount and creation date must match the date on attached invoice. Please follow the invoice requirements below:

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 http://www.detroitmi.gov/Supplier https://ebkk.login.us8.oraclecloud.com/oam/server/obrareq.cgi?ECID-Context=1.006GbR8nJ1j0zkVay1Na6G001bnV0000sM%3BkXjE

Revised 12/2/2025 Page 15 of 17

• Contract number

• Purchase order number

• Total Invoice amount

• The wording “ Goods/Services” (must be noted on every invoice)

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 payment assistance, please contact the Office of Departmental Financial Services

(ODFS) 313-410-7804.

For technical assistance, please visit detroitmi.gov/suppliersupport.

5.4. ASSIGNMENT

The services to be performed by the successful Respondent shall not be assigned, sublet, or transferred, nor shall the successful Respondent assign any monies due or to become due to him under any contract entered into with the City pursuant to these specifications, without prior written approval of the City.

5.5. MODIFICATION OF SERVICES AFTER CONTRACT APPROVAL

The City reserves the right to modify the services provided by the successful Respondent awarded a contract. Any modification and resulting changes in pricing shall be made by amendment to the contract by the successful Respondent and the City.

5.6. NEWS RELEASE

News releases pertaining to these proposal specifications or the provisions to which they relate shall not be made without prior approval of the City and then only in coordination with the City.

5.7. 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 for specific contact information regarding these opportunities.

https://urldefense.com/v3/__https:/descmiworks.org/business-services/__;!!NcXZSU8rfchoEksI!efgwb7Az7YQ1WNYz08X3skt7ah9Lt0tZnoFrliM4GlUH9iYP4Dtz_l03Xya-8iVDi2esZRdC59m0O9Xl8DlelS4a5w$

Revised 12/2/2025 Page 16 of 17

Contractors are encouraged to employ innovative approaches, including ethically and responsibly leveraging artificial intelligence and advanced technologies, to enhance goods delivery, services, and operational performance. Vendors using AI solutions will be asked to provide information on how the AI solution functions.

5.8. OFFICE OF INSPECTOR GENERAL

5.8.1. In accordance with Section 2-106.6 of the City Charter, this Contract shall be voidable or rescindable at the discretion of the Mayor or Inspector General at any time if a Public Servant who is a party to the Contract has an interest in the Contract and fails to disclose such interest.

5.8.2. This Contract shall also be voidable or rescindable if a lobbyist or employee of the contracting party offers a prohibited gift, gratuity, honoraria or payment to a Public Servant in relation to the Contract.

5.8.3. A fine shall be assessed to the Contractor in the event of a violation of Section 2-106.6 of the

City Charter. If applicable, the actions of the Contractor, and its representative lobbyist or employee, shall be referred to the appropriate prosecuting authorities.

5.8.4. Pursuant to Section 7.5-306 of the City Charter, the Inspector General shall investigate any

Public Servant, City agency, program or official act, contractor and subcontractor providing goods and services to the City, business entity seeking contracts or certification of eligibility for City contracts and person seeking certification of eligibility for participation in any City program, either in response to a complaint or on the Inspector General’s own initiative in order to detect and prevent waste, abuse, fraud and corruption.

5.8.5. In accordance with Section 7.5-310 of the City Charter, it shall be the duty of every Public

Servant, contractor, subcontractor, and licensee of the City, and every applicant for certification of eligibility for a City contract or program, to cooperate with the Inspector

General in any investigation pursuant to Article 7.5, Chapter 3 of the City Charter.

5.8.6. Any Public Servant who willfully and without justification or excuse obstructs an investigation of the Inspector General by withholding documents or testimony, is subject to forfeiture of office, discipline, debarment or any other applicable penalty.

5.8.7. As set forth in Section 7.5-308 of the City Charter, the Inspector General has a duty to report illegal acts. If the Inspector General has probable cause to believe that any Public Servant or any person doing or seeking to do business with the City has committed or is committing an illegal act, then the Inspector General shall promptly refer the matter to the appropriate prosecuting authorities.

For purposes of this Article: “Public Servant” means the Mayor, members of City Council, City Clerk, appointive officers, any member of a board, commission or other voting body established by either branch of City government or the City Charter, and any appointee, employee or individual who provides services to the City within or outside of its offices or facilities pursuant to a personal services contract.

Revised 12/2/2025 Page 17 of 17

RFP Attachments List

The following Attachments are available to download on the Supplier Portal.

Attachment A: Respondent Questionnaire

Attachment B: Proposal Introduction & Solution / Approach

Attachment C: Pricing Matrix

Attachments D1 & D2: Forms, Affidavits, and Documents

Attachment E: Model Professional Services Contract