27_PRO-0009-S - Enterprise Ticketing Platform for Morgan State University.pdf

i

RFP – Rev. 05/13/2019- Office of General Counsel

MORGAN STATE UNIVERSITY™

REQUEST FOR PROPOSALS

FOR

Project Name: Enterprise Ticketing Platform for Morgan State University

Project Number: 27/PRO-0009-S

PROSPECTIVE OFFERORS (“OFFERORS’) WHO OBTAINED THIS REQUEST FOR

PROPOSALS (“RFP”) FROM ANY SOURCE OTHER THAN THE DIRECTOR OF

PROCUREMENT OR AN AUTHORIZED DESIGNEE, SHOULD IMMEDIATELY

PROVIDE THEIR NAMES AND EMAIL ADDRESSES TO THE MORGAN STATE

UNIVERSITY OFFICE OF PROCUREMENT AND PROPERTY CONTROL (“ISSUING

OFFICE”), TO ENSURE RECEIPT OF ADDENDA AND OTHER COMMUNICATIONS

REGARDING THE RFP.

Morgan State University

Office of Procurement and Property Control

2101 E. Biddle Street, Suite 1202

Baltimore, MD 21213

(443) 885-3074

NOTE:

ALL BUSINESSES, INCLUDING MINORITY, WOMEN-OWNED, AND SMALL

BUSINESSES, ARE ENCOURAGED TO RESPOND TO THIS SOLICITATION

https://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&ved=2ahUKEwjXxvzEz7HhAhVqm-AKHWNxB2kQjRx6BAgBEAU&url=https://www.youtube.com/channel/UCg4C8vRdNi_2zfl4LTeh3yA&psig=AOvVaw1TgN_9k2rqJhfdxbbs7L55&ust=1554301784716349 ii

KEY INFORMATION SUMMARY SHEET

Request for Proposals

Enterprise Ticketing Platform for Morgan State University

RFP Issue Date: August 10, 2026

RFP Issuing Office: Morgan State University Office of Procurement and

Property Control

Procurement Officer or

Procurement Officer’s Representative: Devan B. Perry

Office Phone: (443) 885-3364

E-mail: devan.perry@morgan.edu

Mailing Address: Morgan State University

Office of Procurement and Property Control

2101 E. Biddle Street, Suite 1202

Baltimore, MD 21213

Attention: Devan B. Perry

Pre-Proposal Conference Date: N/A

Deadline for Questions: August 17, 2026

Closing Date and Time: September 7, 2026, at 2:00 p.m. Local Time.

Oral Presentations (If Applicable): To Be Determined

Contract Term: One (1) Year – Twelve (12) Month Base Fixed

Price with Four (4) Twelve (12) Month Options

Years.

Morgan State University is committed to ensuring that persons with disabilities have equally effective opportunities to participate in and benefit from Morgan State University's programs and services. Persons who may require reasonable accommodations pursuant to the Americans with

Disabilities Act of 1990 (“ADA”) (42 U.S.C. § 12101 et. seq.) should contact the RFP Issuing

Office at 443-885-3074 at least five (5) days prior to any meeting scheduled in connection with this RFP.

iii

MORGAN STATE UNIVERSITY

NOTICE TO OFFERORS

To help improve the quality of proposal solicitations and to make our procurement process more responsive and "business friendly," we ask that you provide comments and suggestions regarding the enclosed RFP. Please return your comments with your proposal or "no proposal," response, as the case may be. Thank you for your assistance.

Proposal Number: 27/PRO-0009-S Titled: Enterprise Ticketing Platform for Morgan State

University

I. If you have responded with a "no proposal" please indicate the reasons below:

( ) Other commitments preclude our participation at this time.

( ) The subject of the solicitation is not something we normally provide.

( ) We are inexperienced in the work/commodities required.

( ) The specifications are either unclear or too restrictive (Explain below).

( ) The scope of work is beyond our current capacity.

( ) Doing business with Maryland Government agencies is simply too complicated

(Explain below).

( ) We cannot be competitive (Explain below).

( ) Time allotted for completion of the bid/proposal response is insufficient.

( ) Startup time is insufficient.

( ) Bonding/Insurance requirements are prohibitive (Explain below).

( ) Minority Business Enterprise (“MBE”) requirements (Explain below)

( ) Proposal requirements (other than specifications or scope) are unreasonable or too risky (Explain below).

( ) Prior experience with Morgan State University contracts was unprofitable or otherwise unsatisfactory (Explain below).

( ) Payment schedule too slow.

( ) Other:

II. If you have submitted a proposal, but wish to offer suggestions or express concerns, please use the remarks section below.

Remarks:

Offeror Name:

Contact Person:

Signature: Date:

Address:

E-Mail:

Telephone: Fax:

iv

TABLE OF CONTENTS

Morgan State University ............................................................................................................ i

KEY INFORMATION SUMMARY SHEET ......................................................................... ii

NOTICE TO OFFERORS ....................................................................................................... iii

TABLE OF CONTENTS ......................................................................................................... iv

SECTION 1. INFORMATION FOR OFFERORS

1.1 SUMMARY STATEMENT

1.2 ISSUING OFFICE AND PROCUREMENT OFFICER

1.3 PRE-PROPOSAL CONFERENCE

1.4 QUESTIONS AND INQUIRIES

1.5 PROPOSAL DUE DATE

1.6 DURATION OF PROPOSAL OFFER

1.7 PROCUREMENT METHOD

1.8 MULTIPLE OR ALTERNATE PROPOSALS

1.9 MINORITY BUSINESS ENTERPRISE UTILIZATION – (N/A)

1.10 SMALL BUSINESS PROCUREMENT

1.11 EXPRESSIONS OF INTEREST

SECTION 2. GENERAL INFORMATION FOR OFFERORS

2.1 PURPOSE

2.2 ADDENDA TO THE RFP

2.3 PRE-PROPOSAL MODIFICATION OR WITHDRAWAL OF OFFERS

2.4 CANCELLATION OF SOLICITATION/REJECTION OF ALL PROPOSALS

2.5 DISCUSSIONS

2.6 ORAL PRESENTATIONS

2.7 INCURRED EXPENSES

2.8 ARREARAGES

2.9 VERIFICATION OF REGISTRATION AND TAX PAYMENT

2.10 PREPARATION OF PROPOSALS

2.11 PUBLIC INFORMATION ACT NOTICE

2.12 EXECUTION OF PROPOSALS

2.13 DISCREPANCIES, EXPLANATIONS AND CLARIFICATIONS

2.14 ORDER OF PRECEDENCE

2.15 REQUIRED CONTRACT PROVISIONS

v

2.16 OFFEROR RESPONSIBILITIES

2.17 FALSIFICATION/CONCEALMENT OF MATERIAL FACTS/COLLUSION

2.18 PAYMENT TO THE CONTRACTOR; TAXES

2.19 NEWS/PRESS RELEASES

2.20 RECIPROCAL PREFERENCE

2.21 VENDOR ELECTRONIC FUNDS TRANSFER REGISTRATION

2.22 PARKING/TRAFFIC

2.23 DRUGS AND ALCOHOL

2.24 GOOD FAITH

2.25 PROTESTS

2.26 DEBRIEFING OF UNSUCCESSFUL OFFERORS

SECTION 3. SCOPE OF WORK (SOW)

3.1 INTRODUCTION AND BACKGROUND

3.2 OBJECTIVES

3.3 SCOPE OF SERVICES

3.4 DELIVERABLES

3.5 PERIOD OF PERFORMANCE

SECTION 4. CLAUSES

4.1 CLAUSES INCORPORATED IN FULL TEXT

SECTION 5- SPECIAL REQUIREMENTS

5.1 QUALITY CONTROL (QC):

5.2 SOC 2 TYPE 2 AUDIT REPORT:

5.3 SUPERVISION OF EMPLOYEES:

5.4 SUBCONTRACTORS/OR STAFF:

5.5 QUALITY ASSURANCE:

SECTION 6. CONTRACT ADMINISTRATION

6.1 PARTNERING:

6.2 POST AWARD CONFERENCE (THE MSU WILL PAY NO ADDITIONAL COST FOR

ATTENDANCE)

SECTION 7. VENDOR PERFORMANCE RATING

7.1 CONTRACTOR EVALUATION RATINGS

7.2 BUSINESS MEETINGS:

7.3 PRODUCTION MEETINGS:

7.4 ADMINISTRATIVE SUBMITTALS:

vi

7.5 NON-CONFORMING PRODUCTS OR SERVICES:

7.6 REMOVAL OF PERSONNEL:

7.7 CONTRACTOR COMPLIANCE:

SECTION 8. INSTRUCTIONS

8.1 SPECIAL INSTRUCTIONS:

8.2 THE UNIVERSITY SHALL NOT PAY COST INCURRED IN SUBMISSION OF

PROPOSAL:

8.3 INCORPORATION OF PROPOSAL:

8.4 PROPOSAL SUBMISSION:

8.5 PROPOSED PRODUCTS AND/OR SERVICES THAT EXCEED MINIMUM

REQUIREMENTS:

8.6 GENERAL INSTRUCTIONS:

8.7 PRICE PROPOSAL CONTENT AND FORMAT:

8.8 EVALUATION:

APPENDICES

pg. 1

SECTION 1. INFORMATION FOR OFFERORS

This RFP is governed by Morgan State University’s Procurement Policies and Procedures approved by the Morgan State University Board of Regents on January 11, 2005 and the Board of Public Works September 21, 2005.

1.1 SUMMARY STATEMENT

Morgan State University (“the University” or “Morgan”), an agency and instrumentality of the State of Maryland, located at 1700 East Cold Spring Lane, Baltimore Maryland

21251, is a historically Black institution with the unique designation as Maryland’s preeminent public urban research university. Governed by a Board of Regents, Morgan is independent of the University of Maryland System. Currently, the University enrolls approximately 10,000 students and employs over 2,200 individuals. Offering degree programs from the baccalaureate through the doctorate, Morgan has a comprehensive mission which encompasses instruction, research and public service.

This RFP is intended to provide Offerors with sufficient information to prepare and submit proposals for consideration (“Proposals”) in order to provide Morgan with a

Enterprise Ticketing Platform. In addition, this RFP will provide Offerors an opportunity to present their qualifications, experience, and conceptual approach to providing the requested services. This RFP is subject to all applicable laws and regulations, and

Morgan State University policies.

1.2 ISSUING OFFICE AND PROCUREMENT OFFICER

The sole point of contact for the purposes of this RFP is the Director of Procurement or an authorized designee (hereinafter referred to as Procurement Officer) noted on the Key

Information Summary Sheet (Page ii). Only the information communicated by the

Procurement Officer shall be deemed the official position of University; no other State or

University employee, official, or representative has authority to change the requirements of this solicitation. Attempts by an Offeror to contact members of the “Evaluation

Committee” or otherwise circumvent this procedure in any manner may be grounds for disqualification of the Offeror from the procurement process.

1.3 PRE-PROPOSAL CONFERENCE

A pre-proposal conference will be held as noted on the Key Information Summary Sheet

(Page ii). Offerors shall submit questions in writing to the Procurement Officer prior to the pre-proposal conference. Offerors are not required to attend the pre-proposal conference.

However, in order to ensure adequate seating, all Offerors planning to attend the pre-proposal conference should confirm their attendance, in writing, to the Issuing Office, not less than thirty (30) days in advance of the conference date. A site visit of the facility will directly follow the pre-proposal conference. Any other site visits will require advanced scheduling.

pg. 2

Morgan is committed to ensuring that persons with disabilities have equally effective opportunities to participate in and benefit from Morgan's programs and services. Persons who require reasonable ADA accommodation should contact the Issuing Office at least five (5) days prior to the pre-proposal conference, as well as for any other meeting scheduled in connection with this RFP.

1.4 QUESTIONS AND INQUIRIES

Offerors shall direct all communications regarding this solicitation to the Procurement

Officer. Submit questions to the Procurement Officer, in writing (email preferred) not later than the date indicated on the Key Information Summary Sheet (Page ii). Addenda, if required, will be furnished to all potential Offerors known to have received the RFP.

1.5 PROPOSAL DUE DATE

Proposals must be received at the Issuing Office by the time and date indicated in the Key

Information Summary Sheet (Page ii). Any Proposal, request for withdrawal, or modification of a proposal that is not received at the Issuing Office by the designated time and date indicated will be considered late and will not be considered.

Delivery of the Proposal to the specified location at the prescribed time and date is the sole responsibility of the Offeror. Requests for extensions will not be granted, nor will late requests for modification, or late requests for withdrawal be considered.

At the sole discretion of the Procurement Officer, exceptions may be made only when the

University’s reason for receipt of a late Proposal, Proposal withdrawal request or

Proposal modification request is due to the action or inaction of the Procurement Officer.

1.6 DURATION OF PROPOSAL OFFER

Proposals submitted in response to this RFP are irrevocable for ninety (90) days following the closing date for proposals or, if requested by the Procurement Officer, the due date for best and final offers (“BAFO”).

1.7 PROCUREMENT METHOD

This solicitation shall be conducted in accordance with all applicable laws and regulations, as well as the Morgan State University Procurement Policies and Procedures

(Approved by the Morgan State University Board of Regents on January 11, 2005 and

Approved by the Board of Public Works on September 21, 2005 (MSU Item 1-GM)). The procurement method is “Competitive Sealed Proposal” (CSP) – Best Value.

1.8 MULTIPLE OR ALTERNATE PROPOSALS

Multiple or alternate Proposals will not be accepted.

1.9 MINORITY BUSINESS ENTERPRISE UTILIZATION – (N/A)

pg. 3

1.10 SMALL BUSINESS PROCUREMENT

If this solicitation indicates that this procurement has been designated for a small business reserve, the provisions of COMAR Title 21.11.01.06 pertaining to small business reserve shall apply and are incorporated herein by reference.

1.11 EXPRESSIONS OF INTEREST

Expressions of interest shall come due, as identified on the Key Information Summary

Sheet (Page ii). Failure to provide an expression of interest shall not disqualify Offerors from providing a Proposal. Expressions of Interest may be sent to the Procurement

Officer.

SECTION 2. GENERAL INFORMATION FOR OFFERORS

2.1 PURPOSE

The purpose of this solicitation is to provide information to Offerors interested in preparing and submitting proposals to meet the requirements contained herein. Offerors shall familiarize themselves with each section and subsection of this document.

2.2 ADDENDA TO THE RFP

The University reserves the right to amend this solicitation at any time prior to the proposal due date. If any amendments or addenda are required, the Procurement Officer shall send a copy of the amendments to all potential Offerors that are known to have received a copy of the solicitation. All amendments shall include a statement to the effect that Offerors are required to acknowledge receipt of any amendments to the request for proposals. If appropriate, the due date shall be adjusted to ensure that sufficient time is given to prospective Offerors to consider the information contained in the amendment for preparation of their responses.

2.3 PRE-PROPOSAL MODIFICATION OR WITHDRAWAL OF OFFERS

Proposals may be modified or withdrawn by written notice received at the Issuing Office at any time before the proposal due date and time. Any request for withdrawal, or modification, of a Proposal that is not received at the Issuing Office by the designated time and date indicated will be considered late and will not be considered.

At the sole discretion of the Procurement Officer, exceptions may be made only when the

University’s reason for receipt of a late request for withdrawal, or modification, is due to the action or inaction of the Procurement Officer.

2.4 CANCELLATION OF SOLICITATION/REJECTION OF ALL PROPOSALS

The University reserves the right to cancel this RFP, to accept or reject any or all proposals, in whole or in part, received in response to this RFP, and to waive or permit cure of minor irregularities as its best interests may require.

pg. 4

2.5 DISCUSSIONS

MSU intends to evaluate proposals and award a contract without discussions with vendors. Therefore, the vendor’s initial proposal should contain the vendor’s best terms from a cost and price and technical standpoint. MSU reserves the right to conduct discussions if the Contracting Officer later determines them deemed to be necessary. If the Procurement Officer determines that a number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Procurement Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

2.6 ORAL PRESENTATIONS

Offerors may be required to make oral presentations to University representatives. If necessary, the Procurement Office will provide notice of the time and place for presentations.

2.7 INCURRED EXPENSES

The University assumes no responsibility for expenses incurred by Offeror in preparing and submitting a Proposal, making an oral presentation, or participating in discussions or any other activity in response to this RFP.

2.8 ARREARAGES

By submitting a response to this RFP, each Offeror shall be deemed to represent that it is not in arrears in the payment of any obligation due and owing the State of Maryland, including the payment of taxes and employee benefits, and that it shall not become so in arrears during the term of the contract if selected for contract award.

2.9 VERIFICATION OF REGISTRATION AND TAX PAYMENT

Each Offeror ensures that it is appropriately registered to do business in the State of

Maryland, and in good standing with respect to taxes, personal property returns, unemployment insurance, etc., before the closing date. Failure to complete registration with the State Department of Assessments and Taxation (SDAT) may disqualify an otherwise successful Offeror from recommendation for contract award.

2.10 PREPARATION OF PROPOSALS

Proposals should be prepared simply and economically, providing a straight-forward, clear, concise, and cogent description of the Vendor’s ability to fulfill the requirements of this solicitation. Proposals are to be submitted in an attachment in the email and submitted directly to the Procurement Officer named in the Key Information Summary

Sheet.

2.11 PUBLIC INFORMATION ACT NOTICE

Offerors should give specific attention to identification of those portions of the proposals that they deem to be confidential, proprietary information or trade secrets and provide any justification why such materials, upon request, should not be disclosed by the State under the Public Information Act, Title 4, Subtitle 3 of the State Government General

Provisions Article, Annotated Code of Maryland.

pg. 5

2.12 EXECUTION OF PROPOSALS

Proposals shall be typewritten or written legibly in ink, and signed in ink as follows, depending on the Offeror's form of business organization:

1. Sole Proprietorship. The Proprietor shall sign full name, with address.

2. Partnership and Joint Venture. Submit the proposal in the name of the partnership or joint venture. Clearly state the partnership name and the identity of each general partner, and execute all affidavits and certificates on behalf of the partnership, or on behalf of each general partner. No provision of any agreement among partners will be binding on the University unless it is disclosed in the

Offeror’s proposal. Reasonable evidence satisfactory to the University of the authority of one partner to bind other purported partners is required. It is recommended that the proposal contain a copy of the partnership agreement, if one exists. If no partnership agreement exists, and if the number of general partners is reasonably small, each general partner should execute all required documents included in the proposal. At the University's option, all general partners may be required to sign the proposal. Failure to present the University with satisfactory information concerning a purported partnership or joint venture may be grounds for finding a proposal unacceptable.

3. Corporation. An officer or authorized agent of the corporation shall sign with full name, indicate title, and include the name and address of the corporation. In the case of an authorized agent, enclose a letter from an officer of the corporation authorizing said individual to act on behalf of the corporation.

2.13 DISCREPANCIES, EXPLANATIONS AND CLARIFICATIONS

Should an Offeror find discrepancies in the specifications or other provisions included in this solicitation, or be in doubt as to the meaning or intent of any section or subsection, the Offeror shall request clarification from the Procurement Officer. Failure to request clarification prior to the due date shall be a waiver of any claim by the Offeror for expenses made necessary by reason of later interpretation of the contract documents, and the Offeror shall be bound to the University's interpretation. Request clarifications in accordance with the instructions above in Section I. (D) of this RFP.

2.14 ORDER OF PRECEDENCE

The contract to be entered into as a result of the RFP ("Contract") will consist of the following Contract Documents, listed in their order of precedence:

1. The Morgan State University Contract

2. This RFP, including any of its exhibits/attachments

3. The Offeror's Proposal

4. Any other supporting documentation

No modifications to this order of precedence will be accepted.

pg. 6

2.15 REQUIRED CONTRACT PROVISIONS

All proposals submitted, and the contracts executed by the successful Offeror(s), are subject to the applicable Morgan State University Terms and Conditions attached hereto in the Appendices.

By submitting a Proposal in response to this solicitation, the Offeror, if selected for award, shall be deemed to have agreed to and accepted all contract terms and conditions set forth in the Morgan State University contract, which is incorporated by reference.

2.16 OFFEROR RESPONSIBILITIES

The successful Offeror shall be responsible for all products and services required by this

RFP. Subcontractors, if any, must be identified and a complete description of their role relative to the project must be identified.

2.17 FALSIFICATION/CONCEALMENT OF MATERIAL FACTS/COLLUSION

Offerors are advised that pursuant to Section 11-205(b) of the State Finance and

Procurement Article of the Annotated Code of Maryland (MD. State Fin. & Pro. Code §

11-205(b)), a person who, for the purpose of defrauding the State, acts in collusion with another person in connection with the procurement process is liable for damages equal to three (3) times the value of the loss to the State that is attributable to the collusion.

In addition, Offerors are advised that section 11-205.1 of the State Finance and

Procurement Article of the Annotated Code of Maryland (MD. State Fin. & Pro. Code §

11-205.1) provides as follows:

(a) In general. -- In connection with a procurement contract a person may not willfully:

(1) falsify, conceal, or suppress a material fact by any scheme or device;

(2) make a false or fraudulent statement or representation of a material fact; or

(3) use a false writing or document that contains a false or fraudulent statement or entry of a material fact.

(b) Aiding or conspiring with others. -- A person may not aid or conspire with another person to commit an act under subsection (a) of this section.

(c) Penalty. -- A person who violates any provision of this section is guilty of a felony and on conviction is subject to a fine not exceeding $ 20,000 or imprisonment not exceeding five (5) years or both.

2.18 PAYMENT TO THE CONTRACTOR; TAXES

Payment is governed by Title 15, Subtitle 1 of the State Finance and Procurement Article, Annotated Code of Maryland. The State of Maryland is exempt from Maryland Retail

Sales Tax and Federal Excise Tax.

pg. 7

2.19 NEWS/PRESS RELEASES

The successful Offeror shall issue no press release to any publication, including newspapers, with regard to work being conducted under this contract. The University is the only entity that may issue or authorize the issuance of any news or press releases to this RFP, its evaluation, award of any contract, and performance there under relating.

Each Offeror further agrees that any commercial advertising resulting from a contract must receive prior approval from the University.

2.20 RECIPROCAL PREFERENCE

1. The provisions of Section 14-401 of the State Finance and Procurement Article of the Annotated Code of Maryland (MD. State Fin. & Pro. Code §14-401) and COMAR

21.05.01.04 shall apply to this RFP.

2. Offerors, who are non-Maryland residents, submitting a Proposal for this solicitation shall include in its Proposal a copy of the current statute, resolution, policy, procedure, or executive order of the resident state for the non-Maryland resident Offeror that pertains to that state's treatment of non-Maryland resident Offerors.

3. Although Maryland law does not authorize procuring agencies to favor resident bidders in awarding procurement contracts, many other states do grant their resident businesses preference over Maryland contractors. Therefore, according to COMAR

21.05.01.04, the University may apply, where applicable, the same preference against an out-of-state business that the business's home state, or state in which its principal office or base of business is located, or principal location from which the services required under this RFP would be provided, would apply against an Offeror whose principal office or base of business is located in Maryland.

2.21 VENDOR ELECTRONIC FUNDS TRANSFER REGISTRATION

Contractors of the State are required to complete a COT/GAD Form X-10, Vendor

Electronic Funds Transfer (EFT) Registration Request Form, attached hereto in the Appendices, for each new contract with a value greater than $200,000. Vendors must register for EFT by submitting a completed COT/GAD Form X-10 to the Maryland State Comptroller’s General Accounting Division (GAD) or request an exemption from GAD.

Additionally, by submitting a response to this solicitation, the Offeror agrees to accept payments by electronic funds transfer unless GAD grants an exemption. Any request for exemption must be submitted to GAD for approval at the address specified on the COT/GAD Form X-10, Vendor Electronic Funds Transfer (EFT) Registration Request Form and must include the business identification information as stated on the form and include the reason for the exemption.

2.22 PARKING/TRAFFIC

All vehicles on Morgan State University property must strictly observe Morgan’s Parking

& Traffic Regulations at all times. All fines and penalties related to parking, traffic, or other vehicle violations are the responsibility of the contractor. This applies to vendors, salespersons, company vehicles, and contractor employees’ personal vehicles. Morgan

pg. 8

State University’s Parking & Traffic Regulations can be found at:

https://www.morgan.edu/parking

2.23 DRUGS AND ALCOHOL

This RFP is subject to the provisions of COMAR 21.11.08 (Drug and Alcohol-Free

Workplace), and the Morgan State University Drug and Alcohol Abuse Policy (Board of

Regents Approved, May 4, 2010). Pursuant to COMAR 21.11.08, Offerors shall submit with its Proposal a certification concerning a drug and alcohol-free workplace. Morgan

State University is dedicated to providing a campus environment free of the illegal and/or abusive use of alcohol and/or drugs. The illegal and/or abusive use of drugs and/or alcohol by members of the campus community jeopardizes the safety of the individual and the campus community, and is contrary to the academic learning process. Morgan

State University is therefore committed to having a campus that is free of the illegal and/or abusive use of drugs and alcohol. In keeping with this commitment, it is the policy of the University that the illegal and/or abusive use of drugs or alcohol is prohibited on

University property or as part of University activities. Further, the possession and/or consumption of alcoholic beverages is prohibited on University premises, except as expressly permitted in writing by the President or designee. Morgan State University

Drug and Alcohol Abuse Policy can be found at: https://www.morgan.edu/board-of-regents/policies-and-procedures

2.24 GOOD FAITH

Offerors agree to deal in good faith with the University during the solicitation process and, if selected, during the performance of the contract. In determining an Offeror’s responsibility, the Procurement Officer may consider whether the Offeror has dealt in good faith with Morgan or any other agency of the State of Maryland in the past.

2.25 PROTESTS

An Offeror may protest the proposed award or the award of a contract for this procurement. Any protest must be filed in accordance with Morgan State University’s

Procurement Policies and Procedures – Section X, Protests and Claims.

2.26 DEBRIEFING OF UNSUCCESSFUL OFFERORS

Unsuccessful Offerors may request a debriefing. If the Offeror chooses to do so, the request must be submitted in writing to the Procurement Officer within ten (10) days after the Offeror knew, or should have known its Proposal was unsuccessful. Debriefings shall be limited to discussion of the specific Offeror's proposal only and shall not include a discussion of a competing Offeror's proposal. Debriefings shall be conducted at the earliest feasible time.

https://www.morgan.edu/parking https://www.morgan.edu/board-of-regents/policies-and-procedures https://www.morgan.edu/board-of-regents/policies-and-procedures

pg. 9

SECTION 3. SCOPE OF WORK (SOW)

3.1 INTRODUCTION AND BACKGROUND

Morgan State University ("MSU" or "University") seeks proposals from qualified firms to provide a comprehensive, cloud-based ticketing platform and associated professional services to support ticket sales, event management, patron engagement, financial reconciliation, and access control across the University's athletic, academic, cultural, student, alumni, and special event programs.

The selected Contractor shall provide all software, hardware (if applicable), implementation services, integrations, training, maintenance, support, and ongoing enhancements necessary to deliver a fully operational ticketing ecosystem. The solution must support both reserved and general admission events while providing a secure, scalable, and user-friendly experience for patrons, University administrators, event organizers, and operational staff.

The University's objective is to establish a centralized ticketing platform that improves operational efficiency, increases ticket revenue opportunities, enhances customer engagement, and provides robust reporting and analytics capabilities.

3.2 OBJECTIVES

The University seeks a solution that will:

A. Centralize Ticketing Operations

• Provide a single enterprise-wide platform capable of supporting multiple departments and event types while allowing department-specific administrative access and reporting.

B. Improve Customer Experience

• Provide a seamless ticket purchasing experience through mobile, desktop, and kiosk-based channels, allowing patrons to purchase, transfer, manage, and access tickets with minimal effort.

C. Enhance Revenue Generation

• Support dynamic pricing, promotional campaigns, discount codes, memberships, season packages, donor benefits, and upselling opportunities.

D. Strengthen Security

• Protect ticket inventory, customer information, and financial transactions

pg. 10 through industry-standard security controls and fraud prevention measures.

E. Increase Operational Efficiency

• Automate ticket issuance, event setup, access control, financial reconciliation, reporting, and customer communications.

F. Support Data-Driven Decision Making

• Provide robust analytics, dashboards, forecasting capabilities, and customizable reporting tools to support strategic planning and event management.

3.3 SCOPE OF SERVICES

The Contractor shall provide all labor, materials, software, equipment, implementation services, maintenance, support, and related resources necessary to provide a fully operational ticketing solution.

A. Ticketing Platform Capabilities

The proposed solution shall provide, at a minimum:

Event Configuration

● Creation and management of unlimited events.

● Reserved seating, assigned seating, and general admission capabilities.

● Multi-day and recurring event support.

● Event package and season ticket management.

● Waitlist functionality.

● Event capacity management.

● Complimentary ticket issuance.

● Guest list management.

Ticket Distribution

The platform shall support:

● Mobile ticket delivery.

● Email ticket delivery.

● SMS ticket delivery.

● Printable PDF tickets.

● Mobile wallet integration.

● Automated ticket fulfillment.

● Bulk ticket generation and distribution.

pg. 11

Ticket Transfers

The system shall allow:

● Secure ticket forwarding.

● Ticket resale controls.

● Ticket exchanges.

● Ticket cancellation and reissuance.

● Patron self-service ticket management.

Commencement Support

Because commencement activities represent one of the University's largest annual events, the platform shall support:

● High-volume ticket distribution.

● Student-based ticket allocation.

● Departmental allocation controls.

● QR-code verification.

● Guest management functionality.

● Real-time entry monitoring.

Tailgating and Parking Event Management

The platform shall support management of tailgating, parking, and pre-event activities associated with athletic contests and major campus events, including:

● Tailgating permit sales and distribution.

● Reserved tailgate space assignments.

● Parking permit management.

● QR-code or mobile credential validation.

● Real-time occupancy monitoring.

● Group tailgating package sales.

● Donor, alumni, and VIP tailgating access controls.

● Mobile check-in for tailgating areas.

● Integration with parking and event operations staff.

Student Ticket Management

The platform shall support:

● Student-specific ticket allocations.

● Validation through University credentials.

● Student claim and reservation processes.

● Student guest ticket distribution.

pg. 12

● Capacity limits by student classification or event type.

● Fraud prevention measures to reduce unauthorized transfers.

B. Customer Experience and Accessibility

The Contractor shall provide an intuitive user interface designed to maximize ease of use and accessibility.

The solution shall:

● Be fully responsive across desktop, tablet, and mobile devices.

● Support ADA compliance and accessibility standards.

● Provide multilingual capabilities where available.

● Support self-service account management.

● Allow patrons to view purchase history.

● Provide automated confirmations and reminders.

● Support customer service interactions through integrated communication tools.

The platform shall support event-specific communications, including:

● Text message notifications.

● Event reminders.

● Parking and gate-entry instructions.

● Weather-related updates.

● Event schedule changes.

● Emergency communications.

C. Hardware and Event Operations

If hardware is proposed, the Contractor shall provide all necessary equipment specifications and compatibility requirements.

Capabilities should include:

● Handheld ticket scanners.

● Fixed-position scanning devices.

● Mobile point-of-sale devices.

● On-site box office workstations.

● Wireless ticket validation.

● Offline scanning capability.

● Real-time attendance tracking.

pg. 13

The Contractor shall provide testing equipment and a sandbox environment for training and system validation.

Emergency Event Operations

The platform shall support operational coordination during emergency situations, including:

● Real-time attendance counts.

● Zone-based occupancy monitoring.

● Emergency messaging capabilities.

● Event evacuation reporting.

● Access restriction capabilities.

● Integration with campus public safety operations when available.

D. Security and Compliance

The proposed solution shall comply with applicable industry standards and security requirements.

At a minimum, the system shall provide:

● Unique encrypted ticket identifiers.

● Dynamic QR code technology.

● Anti-counterfeiting protections.

● Fraud detection monitoring.

● Secure user authentication.

● Role-based access controls.

● Audit logging capabilities.

● Data encryption in transit and at rest.

● PCI-DSS compliance for payment processing.

● Compliance with applicable federal, state, and University data security requirements.

The Contractor shall immediately notify the University of any security incident affecting

University data.

E. Financial Management and Payment Processing

The solution shall provide comprehensive financial management capabilities, including:

● Multiple payment methods.

● Credit card processing.

pg. 14

● Mobile payment support.

● Refund processing.

● Chargeback management.

● Donation processing.

● Promotional discounts.

● Tax calculations where applicable.

● Revenue reconciliation tools.

The Contractor shall provide:

● Daily sales reports.

● Settlement reports.

● Fee breakdown reports.

● Department-level accounting reports.

● Revenue distribution reporting.

Settlement of ticket revenue shall occur within a timeframe proposed by the Contractor and approved by the University.

F. System Integration Requirements

The Contractor shall provide integration services necessary to connect the ticketing platform with existing University systems.

The proposed solution should integrate with:

● Banner ERP.

● TouchNet.

● CashNET.

● Microsoft Active Directory and Single Sign-On (SSO).

● University websites and event calendars.

● CRM systems.

● Email marketing platforms.

● Mobile applications.

The Contractor shall describe all available APIs and integration methodologies.

G. Reporting and Analytics

The platform shall provide comprehensive reporting capabilities, including:

Standard Reports

pg. 15

● Ticket sales reports.

● Attendance reports.

● Revenue reports.

● Event performance reports.

● Customer activity reports.

Advanced Analytics

● Attendance forecasting.

● Revenue forecasting.

● Demographic analysis.

● Purchasing trends.

● Conversion tracking.

● Marketing campaign effectiveness.

Dashboard Requirements

The University requires configurable dashboards displaying:

● Real-time ticket sales.

● Attendance metrics.

● Revenue performance.

● Event comparisons.

● Operational KPIs.

Reports shall be exportable in multiple formats including PDF, Excel, CSV, and other standard business formats.

H. Training and Knowledge Transfer

The Contractor shall provide comprehensive training for University personnel.

Training shall include:

● System administration.

● Event management.

● Box office operations.

● Financial reporting.

● Access control operations.

● Reporting and analytics.

● End-user support procedures.

Training materials shall include:

pg. 16

● User manuals.

● Quick-reference guides.

● Recorded training sessions.

● Online knowledge base access.

I. Customer Support and Service Levels

The Contractor shall provide ongoing technical and customer support throughout the contract period.

Minimum requirements include:

Support Availability

● 24 hours per day.

● 7 days per week.

● 365 days per year.

Support Channels

● Telephone support.

● Email support.

● Online ticket submission.

● Live chat (if available).

Service Level Expectations

Priority Description Response Time

Critical System unavailable 1 hour

High Major functionality impaired 4 hours

Medium Limited operational impact 1 business day

Low General questions or enhancements 2 business days

J. Vendor Qualifications

Offerors shall demonstrate:

● Minimum five (5) years of ticketing platform experience.

● Experience serving colleges and universities.

● Experience supporting NCAA athletic programs, homecoming celebrations, tailgating operations, commencement ceremonies, concerts, festivals, and other large-scale campus events.

● Financial stability.

pg. 17

● Proven implementation methodology.

● Positive customer references.

The University may request references from at least three higher education institutions of similar size and complexity.

3.4 DELIVERABLES

The Contractor shall provide:

1. Fully implemented ticketing platform.

2. System configuration and customization.

3. Integration with University systems.

4. Hardware and equipment (if applicable).

5. Data migration services.

6. User acceptance testing support.

7. Training and documentation.

8. Go-live support.

9. Ongoing maintenance and support.

10. Quarterly business reviews.

11. Annual system performance reports.

3.5 PERIOD OF PERFORMANCE

The anticipated period of performance shall be one (1) base year plus four (4) one-year option periods, for a total potential contract term of five (5) years. The University reserves the right to exercise option years at its sole discretion based on vendor performance, funding availability, and institutional needs.

pg. 18

SECTION 4. CLAUSES

4.1 CLAUSES INCORPORATED IN FULL TEXT

MORGAN STATE UNIVERSITY PROCUREMENT POLICIES AND

PROCEDURES

APPENDIX A - TERMS AND CONDITIONS

Mandatory Terms and Conditions of Written Solicitations Over $100,000.

1. Instructions and information to vendors concerning the solicitation requirements, including the time and date set for receipt of the responses and the address where responses are to be delivered;

2. The purchase description, delivery or performance schedule, and any special instructions necessary.

3. Whether award shall be made on the basis of the most favorable price or the most favorable evaluated price, or best value, whichever is applicable. If the latter basis is used, measurable evaluation criteria to be used shall be set forth in the solicitation.

4. Acknowledgment of Addenda. The solicitation shall require the acknowledgment of the receipt of all changes issued.

5. Public Information Act Notice.

A Public Information Act Notice is a mandatory provision for all solicitations. The following notice is preferred:

Vendors should give specific attention to the identification of those portions of their responses that they deem to be confidential, proprietary information or trade secrets and provide any justification why such materials, upon request, should not be disclosed by the

University under the Access to Public Records Act, State University Article, Title 10, Subtitle 6, Annotated Code of Maryland."

6. Bid/Proposal Security:

a. Solicitations for construction contracts reasonably expected by the procurement officer to exceed $100,000 shall contain notice of bid security requirements.

b. Solicitations for all other contracts reasonably expected by the procurement officer to exceed $100,000 and for which the procurement officer wishes to require bid security shall contain notice of the bid security requirements.

pg. 19

c. Notwithstanding §§A and B of this regulation, notice of bid security is required if a federal law or a condition of federal assistance for the contract requires it.

7. Minority Business Enterprise Notice:

A minority business enterprise notification is a mandatory provision for all solicitations as follows:

"Minority business enterprises are encouraged to respond to this solicitation".

8. Arrearages:

An arrearages clause is a mandatory provision for all solicitations. The language may be varied but shall contain the following information:

"By submitting a response to this solicitation, a vendor shall be deemed to represent that it is not in arrears in the payment of any obligation due and owing the State of Maryland, including the payment of taxes and employee benefits, and that it shall not become so in arrears during the term of the contract if selected for contract award."

9. Bid/Proposal Affidavit:

Each solicitation shall provide notice that the affidavit prescribed below shall be completed and submitted to the procurement officer.

pg. 20

SECTION 5- SPECIAL REQUIREMENTS

5.1 QUALITY CONTROL (QC):

The offeror shall develop and maintain an effective quality control program (15 days after award) to ensure all services are performed in accordance with the requirements of the contract. The offeror shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The quality control program is the means by which the offeror assures that the work complies with the requirements of the contract. The QC program shall be approved the MSU Technical Representative (TR).

Three copies of the QC program shall be submitted to the Procurement Officer and the

Procurement Technical Representative (TR) within 5 days when changes are made thereafter for approval.

The offeror shall identify and submit the name of the quality control (QC) manager (15 days after receipt of award). This person shall have 5-years of experience overseeing a quality control program and be responsible for reviewing documentation prior to submitting to MSU for approval.

5.2 SOC 2 TYPE 2 AUDIT REPORT:

A SOC 2 Type 2 Audit applies to the Contract.

5.2.1 The applicable trust principles are: << Security, Availability, Processing Integrity, Confidentiality, or Privacy.

The University will choose which of the five trust principles apply as defined in the aforementioned Guidance.

5.2.2 In the event the Contractor provides services for identified critical functions, handles Sensitive Data, or hosts any related implemented system for the

State under the Contract, the Contractor shall have an annual audit performed by an independent audit firm. Critical functions are identified as all aspects and functionality of the Solution including any add-on modules and shall address all areas relating to Information Technology security and operational processes.

These services provided by the Contractor that shall be covered by the audit and will collectively be referred to as the “Information Functions and Processes.”

Such audits shall be performed in accordance with audit guidance: Reporting on

Controls at a Service Organization Relevant to Security, Availability, Processing

Integrity, Confidentiality, or Privacy (SOC 2) as published by the American

Institute of Certified Public Accountants (AICPA) and as updated from time to time, or according to the most current audit guidance promulgated by the AICPA or similarly-recognized professional organization, as agreed to by the University, to assess the security of outsourced client functions or data (collectively, the

“Guidance”) as follows:

1. The type of audit to be performed in accordance with the Guidance is a

SOC 2 Type 2 Audit (referred to as the “SOC 2 Audit” or “SOC 2

pg. 21

Report”). All SOC 2 Audit Reports shall be submitted to the Contract

Owner (Program or Contract Monitor). The initial SOC 2 Audit shall be completed within a timeframe to be specified by Morgan State University.

The audit period covered by the initial SOC 2 Audit shall start with the

Contract Effective Date unless otherwise agreed to in writing by the

Contract Monitor. All subsequent SOC 2 Audits after this initial audit shall be performed at a minimum on an annual basis throughout the Term of the Contract, and shall cover a 12-month audit period or such portion of the year that the Contractor furnished services.

2. The SOC 2 Audit shall report on the suitability of the design and operating effectiveness of controls over the Information Functions and Processes to meet the requirements of the Contract, including the Security

Requirements identified by the University relevant to the trust principles as defined in the aforementioned Guidance.

3. The audit scope of each year’s SOC 2 Report may need to be adjusted

(including the inclusion or omission of the relevant trust services principles of Security, Availability, Processing Integrity, Confidentiality, and Privacy) to accommodate any changes to the environment since the last SOC 2 Report. Such changes may include but are not limited to the addition of Information Functions and Processes through modifications to the Contract or due to changes in Information Technology or the operational infrastructure. The Contractor shall ensure that the audit scope of each year’s SOC 2 Report engagement shall accommodate these changes by including in the SOC 2 Report all appropriate controls related to the current environment supporting the Information Functions and/or

Processes, including those controls required by the Contract.

4. The scope of the SOC 2 Report shall include work performed by any subcontractors that provide essential support to the TO Contractor or essential support to the Information Functions and Processes provided to the University under the Contract. The Contractor shall ensure the audit includes all such subcontractors operating in performance of the Contract.

5. All SOC 2 Audits, including those of the Contractor, shall be performed at no additional expense to the University.

6. The Contractor shall provide to the Contract Owner/Monitor, within 30 calendar days of the issuance of each SOC 2 Report, a complete copy of the final SOC 2 Report(s) and a documented corrective action plan addressing each audit finding or exception contained in the SOC 2 Report.

The corrective action plan shall identify in detail the remedial action to be taken by the Contractor along with the date(s) when each remedial action is to be implemented.

pg. 22

7. If the Contractor currently has an annual, independent information security assessment performed that includes the operations, systems, and repositories of the Information Functions and Processes being provided to the University under the Contract, and if that assessment generally conforms to the content and objective of the Guidance, Morgan State

University will determine in consultation with appropriate University

Department/s and audit authorities whether the Contractor’s current information security assessments are acceptable in lieu of the SOC 2

Report(s).

8. If the Contractor fails during the Contract term to obtain an annual SOC 2

Report by the date specified in Section AA.2.1, the University shall have the right to retain an independent audit firm to perform an audit engagement of a SOC 2 Report of the Information Functions and

Processes utilized or provided by the Contractor under the Contract. The

Contractor agrees to allow the independent audit firm to access its facility/ies for purposes of conducting this audit engagement(s), and will provide the necessary support and cooperation to the independent audit firm that is required to perform the audit engagement of the SOC 2 Report.

The University will invoice the Contractor for the expense of the SOC 2

Report(s), or deduct the cost from future payments to the Contractor.

9. Provisions in Section AA.1-2 shall survive expiration or termination of the

Contract. Additionally, the Contractor and shall flow down the provisions of Section AA.1-2 (or the substance thereof) in all subcontracts.

5.3 SUPERVISION OF EMPLOYEES:

The offeror's employees shall remain under the offeror's direct supervision at all times.

Although MSU will coordinate within the scope of the contract, detailed instruction for the offeror's employees and supervision shall remain the responsibility of the offeror.

5.4 SUBCONTRACTORS/OR STAFF:

The offeror is responsible for overseeing all work in accordance with the contract. The

Procurement Officer may require, in writing, that the offeror remove from the work any employee the Procurement Officer deems incompetent, careless, or otherwise objectionable.

5.5 QUALITY ASSURANCE:

MSU shall evaluate the offeror’s performance under this contract in accordance with the formal Quality Assurance Surveillance Plan (QASP) if over $500,000. This plan is primarily focused on what the University must do to ensure that the Offeror has performed in accordance with the performance standards.