2-RFP 3614-10 Plagiarism.docx
DOCX document 203 KB Posted
- Attached to
- Plagiarism Detection State and local contract opportunity
- Solicitation number
- RFP 3614-10 Plagiarism Detection
- Issued by
- Maricopa County, Arizona
About this file
RFP #3614-10: Plagiarism Detection
This Request for Proposal issued by the Maricopa County Community College District (MCCCD) seeks a qualified vendor to provide an online plagiarism detection and learning tool for use within the district's Learning Management Systems, Canvas and RioLearn, as well as other popular platforms including Desire2Learn, Moodle, and Blackboard. The proposed tool must integrate seamlessly with existing LMS functions, provide intuitive assignment creation and management for instructors, support draft checking without institutional repository submission, enable manual file uploads, accept submissions through standard LMS features, and review various assessment types including quizzes, short answer questions, laboratory assignments, and discussion posts. The tool must support multiple file formats and languages, with particular preference for Arabic, Chinese, French, German, Greek, Italian, Japanese, Latin, Navajo, Pima, Portuguese, Russian, and Spanish. Additionally, the solution must include AI-detection capabilities that are automatically updated, provide accessible visual reports meeting WCAG 2.1 AA standards, offer comprehensive tutorials and training, and maintain ADA compliance. The RFP was released on March 13, 2026, with questions due by March 27, 2026, and proposals due by April 16, 2026, at 3:00 PM local time. Interviews, if required, are scheduled for mid-May, with a proposed contract award in June 2026 and an anticipated contract start date of July 1, 2026. The district intends to award a one-year initial contract with four optional annual renewals for a potential total contract term of five years.
Proposers must submit complete applications through the MCCCD Procurement Portal, including signed signature pages, scope of work responses, Attachment A (bidder statement with three client references), Attachment B (data confidentiality and security addendum), pricing schedules, respondent questionnaires, and the HECVAT security assessment. Pricing proposals must identify annual license costs and any one-time setup fees, with all overhead and profit included. The RFP does not constitute a commitment to award and MCCCD reserves the right to waive informalities, reject proposals, or cancel the solicitation. Proposers may request deviations from the General Terms and Conditions only through a separate "REQUESTED DEVIATIONS" document; deviations to Special Terms and Conditions may be considered but will be evaluated as part of the overall proposal. All proposals must comply with specified format requirements and may not exceed 40 typewritten pages plus exhibits. Contractor must carry Network Security and Privacy Liability insurance of not less than $5,000,000 per claim and annual aggregate, maintain appropriate data security and confidentiality measures consistent with industry standards and applicable laws, and comply with FERPA, HIPAA, and other relevant regulations. MCCCD retains ownership of all records and data, requires annual third-party security audits, and mandates immediate notification of any security incidents. No work may commence and no payment shall be made without a signed purchase order or procurement card from the MCCCD Purchasing Department.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| 1-Notice of Proposal RFP 3614-10 Plagiarism.doc | DOC document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
RFP# 3614-10
Section Eleven: ATTACHMENT B Rev 090817
MARICOPA COUNTY COMMUNITY COLLEGE DISTRICT
REQUEST FOR PROPOSAL #3614-10
Plagiarism Detection
Proposal Due Date April 16, 2026 3 PM (local time)
MARICOPA COUNTY COMMUNITY COLLEGE DISTRICT
RFP # 3614-10
Plagiarism Detection
SCHEDULE OF EVENTS
| ACTIVITY |
| DATE |
| Release RFP |
| March 13, 2026 |
| Questions Due |
| Mach 27, 2026 |
| Proposals Due |
| April 16, 2026 |
| Interviews (if required) |
| Mid-May |
| Proposed Contract Award |
| June 2026 |
Table of Contents
| GENERAL | 1 |
| PROPOSAL INSTRUCTIONS | 4 |
| SCOPE OF WORK | 8 |
| PROPOSAL REQUIREMENTS | 12 |
| EVALUATION CRITERIA | 15 |
| PRICING SCHEDULE | 16 |
| SPECIAL TERMS AND CONDITIONS | 17 |
| GENERAL TERMS AND CONDITIONS | 24 |
| SIGNATURE PAGE | 35 |
| ATTACHMENT A | 36 |
| ATTACHMENT B | 40 |
GENERAL
1.1 INTRODUCTION
The Maricopa Community College District (MCCCD) intends to contract with a company who can provide a tool for the purposes of teaching and learning regarding plagiarism. This tool should be accessible within the District’s adopted Learning Management Systems, Canvas and RioLearn.
1.2 MCCCD DISTRICT MAKE-UP
MCCCD comprised of ten colleges, and numerous education centers dedicated to educational excellence by meeting the needs of the businesses and the citizens of Maricopa County. Each college is individually accredited, yet part of a larger system, the Maricopa County Community College District (MCCCD or District). The MCCCD is one of the largest higher education systems in the nation. As the largest provider of health care workers and job training in Arizona, it is a major resource for business and industry and for individuals seeking education and job training. More than 200,000 students attend the Maricopa Community Colleges each year taking credit and non-credit courses. MCCCD employs nearly 4,800 full-time faculty and staff and more than 6,800 part-time faculty and staff.
1.3 HISTORY
MCCCD ranks as one of the nation’s largest systems of its kind and is the largest single provider of higher education in Arizona. MCCCD educates and trains thousands of students year-round. What’s more, thousands of employees from both local and relocating businesses and industries are enrolled in customized workforce training programs with the MCCCD system. MCCCD’s administration, faculty and staff are committed to working collectively and responsibly to meet the life-long learning needs of our diverse students and communities.
A seven-member governing board governs MCCCD. Five members are elected from geographical districts within Maricopa County, while two are elected on a countywide basis. The chief executive officer of MCCCD is the Chancellor; and a president heads each of the colleges. MCCCD is a political subdivision of the State, and the elected governing board has the power to levy taxes. Funding comes from property taxes, student tuition, and federal, state and private grants.
1.4 CURRENT ENVIRONMENT
The Maricopa County Community College District, along with most educational entities in the State of Arizona, has been dealing with decreased funding support from the State for many years. In 2015, the State of Arizona eliminated all of the funding it was providing to help support MCCCD’s operations. In addition to the loss of all funding from the State, MCCCD has experienced a decrease in student enrollment, which is a typical trend for all community colleges during strong economic times.
It is the philosophy of MCCCD that this loss of funding and decreased enrollment should not be bridged by raising student tuitions or by burdening the public with increases in their taxes. The result of these funding reductions has created a need to rethink the traditional model of customer and vendor so that MCCCD can continue to provide the best learning environment for our student population as well as practice good stewardship of the public support we receive.
It is the District’s desire to move towards a model that is being utilized by many other higher learning institutions throughout the country which is to evolve the previous customer/supplier relationships associated with our contractors to that of becoming our Strategic Partners. By cultivating strategic partnerships, it will enable MCCCD and the awarded contractor to help identify potential cost reductions, maximize efficiencies, and tap unexplored value-added opportunities to maximize resources and support to the benefit of both parties. Any potential strategic initiatives can be established during negotiations.
1.5 STRATEGIC PARTNERSHIPS
In addition to providing the services listed in this Request for Proposal, MCCCD is continually seeking to expand its relationships with contractors who can evolve into a strategic partner. We are seeking companies that can help expand the boundaries of what has been thought of as traditional consulting contracts by infusing the program with new concepts, out-of-the box thinking, and value-added offerings that may not have existed before.
1.6 VALUE-ADDED OFFERINGS:
MCCCD would be interested in receiving any suggestions that would bring added value to this contract. As stated in section 1.4, the previous sources of State revenue support have been cut and in order to continue to provide the quality of education our students deserve MCCCD is open to considering new resources and ideas to help alleviate these short-falls. These proposals may be a one-time occurrence or recurring in nature, revenue producing (such as incentives or rebates) or other offerings that would bring added value to our organization. Provide details how leveraging a strategic partnership with your company can assist MCCCD in achieving our goals. Creative solutions are encouraged and should be clearly labeled in the proposal as an attachment.
Potential value-added offerings may be proposed in general in the attachment but will not be reviewed and considered until after the competitive evaluation process has been completed. Once a susceptibility of award is determined by the evaluation team further negotiations regarding these added value offerings may occur and must be completed prior to a final contract award.
The negotiation of any of these offerings is separate from the evaluation process. Changes / additions to these offerings may be made if agreed upon in writing by both parties and included as a signed contract amendment.
MCCCD reserves the right to exclude items offered under this section from co-operative use unless also agreed upon by the awardee.
Section One: GENERAL Rev 090817
PROPOSAL INSTRUCTIONS
2.1 PROPOSAL QUESTIONS
All questions regarding this Request for Proposal should be submitted online via the MCCCD Procurement Portal. The deadline to submit questions is: March 26, 2026, 5:00 PM (local time).
We will not respond directly to the company asking the question. All questions received within the question period will be acknowledged even if an answer cannot be provided. Responses to the questions received by the deadline will be answered in the form of an addendum. The addendum will be posted on the MCCCD Procurement Portal, and an email notification sent to all known potential respondents who have answered “Yes” to the Intent to Bid question or anyone who has downloaded documents from the portal. The addendum will be made available on/about April 1, 2026.
2.2 PROPOSAL SUBMISSION
MCCCD uses a portal hosted by Euna Procurement (formerly Bonfire) for accepting and evaluating proposals. Registration for a Euna Procurement account will be necessary to view and respond to the RFP. It shall be the responsibility of the Proposer to confirm that proposals contain all required documents and are submitted electronically through the MCCCD Procurement Portal located here:
https://maricopa.bonfirehub.com/portal/?tab=openOpportunities Upon upload, proposals are automatically timestamped and will remain secure and sealed until after the submission deadline has passed. Your proposal should include all items listed in Section 4.6: Format and Submittal Requirements. Your proposal is available for you to edit or change any time up to the RFP submission deadline.
Please contact Euna Procurement at support.bonfire@eunasolutions.com for technical questions related to your submission or difficulties in accessing the RFP documents. You can also visit their help forum at:
https://maricopa.bonfirehub.com/portal/support
Your proposal must be completed and uploaded to our site no later than 3:00 P.M. (local time), April 16, 2026. Submissions after this date and time will automatically be rejected by the system. The time on the MCCCD Procurement Portal shall be the official submittal time of record.
It is the proposer’s responsibility to be aware of the submission deadline and allow sufficient time to complete any uploads needed to finalize your submission. Any technical or internet-related issues that may arise during your submission are not grounds to extend the deadline. It is strongly recommended you begin your submission upload process at least one (1) day prior to the deadline.
2.3 AWARD DETERMINATION
This Request for Proposal does not constitute a commitment by the District to award a contract. The District reserves the right to waive any informalities and to reject any or all proposals and/or to cancel the Request For Proposal. The award shall be made on the proposal(s) that serves the best interest of the District and will not be evaluated solely on a monetary basis. The District reserves the right to negotiate a contract with the selected awardee. Even after the execution of a contract document or Notice of Award, the selected vendor may not initiate contract performance or incur any contract costs until it receives a District-issued purchase order or Procurement card.
2.4 PROPRIETARY INFORMATION
All materials submitted as part of a response to a solicitation are subject to Arizona public records law and will be disclosed if there is an appropriate public records request at the time of or after the award of the contract.
In the event any Proposer shall include in the Proposal any information deemed "proprietary" or "protected", such information shall be separately packaged from the balance of the proposal and clearly marked as to any proprietary claim. A “Confidential Information” section is included in the solicitation’s Requested Information. See section 4.6.
If a Proposer wants to assert that a proposal contains a trade secret or other proprietary information, a Proposer shall include with the submission a statement supporting this assertion. A Proposer shall clearly designate any trade secret and other proprietary information, using the term “confidential” and include it in the “Confidential Information” submittal section. Contract terms and conditions, pricing, and information generally available to the public are not considered confidential information.
The District discourages the submission of such information and undertakes to provide no more than reasonable efforts to protect the proprietary nature of such information. The District, as a public entity, cannot and does not warrant that proprietary information will not be disclosed. The District shall have the right to use any or all information included in the proposals submitted unless the information is expressly restricted by the Proposer. The District reserves the right to make its own determination of Proposer’s proprietary materials.
Requests to deem the entire proposal or price as confidential will not be considered.
When submitting a response containing “Confidential” information, Proposer agrees to defend, indemnify and hold harmless the District, its officers and employees, from every claim, demand, loss, expense, cost, damage or injury, including attorney’s fees, arising out of or resulting from the District withholding information that offeror marked as “Confidential”.
2.5 PROPOSAL FORM
All proposals must be submitted in writing, using the accepted file formats listed. Each proposal shall be prepared simply, providing the straightforward, concise description of the proposer's ability to meet the requirements of the RFP. Emphasis should be on completeness and clarity of contents. No proposal shall exceed forty (40) typewritten pages in length plus any pricing schedule(s), exhibits, resumes, proposed draft revenue sharing agreement, or attachments. Please refer to Section 4.6 Format and Submittal Requirements. Proposals that do not follow the Format and Submittal Requirements outlined in Section 4.6 may be disqualified.
2.6 PROPOSER MODIFICATIONS TO PROPOSALS
Proposals may be modified after submittal to the MCCCD Procurement Portal by accessing your Euna Procurement account. Any modifications must be made and the files re-uploaded to the MCCCD Procurement Portal by the published opening date and time. No modifications to proposals are permitted by the proposer after the published RFP opening date and time.
2.7 WITHDRAWAL OF PROPOSAL
Any Proposer may withdraw their proposal by accessing their Euna Procurement account prior to the deadline set for receipt of proposals. No proposal may be withdrawn or modified after that deadline and shall be binding upon Proposer for a period of ninety (90) days after due date. Withdrawn Proposals may be resubmitted up to the time designated for the receipt of Proposals provided that they are then fully in conformance with the general terms and conditions of the RFP.
2.8 PROPOSAL COSTS
Any and all costs associated with the preparation of responses to this Request for Proposal, including site visits, oral presentations and any other costs shall be entirely the responsibility of the Proposer and shall not be reimbursable in any manner.
2.9 ORAL PRESENTATIONS
Proposers may, after opening and prior to award, be required to make oral and visual presentations at the request of the MCCCD. The MCCCD will schedule the time and location for any presentations as requested. Oral presentations will be evaluated.
2.10 AWARD WITHOUT DISCUSSION
The MCCCD reserves the right to make an award(s) without further discussion of the proposals received. It is therefore critical that all proposals be submitted initially in the most favorable terms possible, both economically and technically.
2.11 CONTRACT COMMENCEMENT/TERM
It is the intent of the District to award a 1-year contract, with 4 optional renewals, for a total potential contract term of five (5) years. However, if a mutually beneficial strategic agreement can be reached that would benefit from a longer term, those terms will also be considered.
A written Notice of Award with a specific contract start date will be made prior to commencement of performance. The contract start date is expected to be approximately July 1, 2026. No billable work is to be done without a signed PO.
2.12 MCCCD MODIFICATIONS TO PROPOSALS
Any interpretation, correction, or change of this RFP will be made by written Addendum. Interpretations, corrections, or changes of this RFP made in any other manner will not be binding, and Proposers shall not rely upon such interpretations, corrections, and changes. Any changes or corrections will be issued by MCCCD Purchasing. Addenda notification will be e-mailed to all known potential respondents who have answered “Yes” to the Intent to Bid question on the portal or anyone who has downloaded documents from the portal. Addenda will also be posted to the proposal documents on the MCCCD Procurement Portal located at:
https://maricopa.bonfirehub.com/portal/?tab=openOpportunities
2.13 NON-COLLUSION
The MCCCD encourages free and open competition. Whenever possible, specifications, proposal invitations and conditions are designed to accomplish this objective, consistent with the necessity to satisfy the MCCCD’s needs and the accomplishment of a sound economical operation. The Proposer's signature on its proposal guarantees that any prices offered have been established without collusion with other eligible Proposers and without effort to preclude the MCCCD from obtaining the most advantageous proposal.
RFP# 3614-10
Section Two: PROPOSAL INSTRUCTIONS Rev 090817
SCOPE OF WORK
3.1 Minimum Requirements
3.1.1 Must provide an online plagiarism detection/learning tool that integrates with Maricopa’s current Learning Management Systems (LMSs), Canvas and RioLearn, as well as other popular LMSs such as Desire2Learn, Moodle, and Blackboard.
3.1.2 Must provide an integration that does not disrupt the function of other tools within the LMS (e.g., LMS rubrics must still be editable for instructors and display to students on assignments when using the plagiarism detection tool).
3.1.3 Must provide an integration that is intuitive for instructors to create and manage assignments, ideally allowing instructors to create and manage assignments within the LMS without requiring additional logins or complicated setup.
3.1.4 Must provide the option for students and faculty to check drafts either directly or within the LMS in which the submission is NOT submitted to the institution repository.
3.1.5 Must provide the ability for instructors to upload files manually for on-demand reports.
3.1.6 Must provide the ability for students to submit assignments through the LMS assignment feature.
3.1.7 Must provide the ability to review quizzes, short answer exam questions, laboratory assignments, and discussion posts for plagiarism and/or AI detection.
3.1.8 Must accept and review submissions in multiple file formats, such as MS Office documents including MS Word doc and docx, Powerpoint, Adobe Creative Suite files such as PDF, and Google Suite files such as Google Docs and Slides.
3.1.9 Must support submissions in multiple languages. Responses must include a list of supported languages or any limitations and disclose measured accuracy/false‑positive rates per language. MCCCD prefers support for all of the following languages: Arabic, Chinese, French, German, Greek, Italian, Japanese, Latin, Navajo, Pima, Portuguese, Russian, and Spanish.
3.1.10 Must check against a large variety of databases representing previously submitted student papers to the plagiarism service, academic resources, archived web pages, Internet searches, and institution submissions (indicate the number and longevity of databases used).
3.1.11 Must provide detailed reports that identify and match student content to original sources and provide links to the original sources when available.
3.1.12 Must generate reports for assignment submissions made after the due date.
3.1.13 Must have the option to rerun reports when removing particular matches.
3.1.14 Must be able to save and/or export reports.
3.1.15 Must provide visual reports that distinguish sources using accessible indicators and do not rely solely on color.
3.1.16 Must allow instructors the ability to filter out identical content including citations, bibliographies, and small matches.
3.1.17 Must be ADA compliant and meet WCAG 2.1 AA standards.
3.1.18 Must provide a turn-key solution.
3.1.19 Must provide online tutorials, training, and support for faculty, students, and the institution. Must include detailed documentation and a support team for LMS integration.
3.1.20 Must include an AI-checking element that is automatically updated as technology advances and that can be filtered out. The vendor must describe how AI detection works, clearly separate AI detection results from plagiarism, the percentage similarity score, and include the AI tool used.
3.1.21 Prefer students have the ability to self check for percentage of plagiarism and/or AI usage, without an instructor-initiated assignment.
3.1.22 Prefer instructors have the ability to use the plagiarism check against all types of assessments within the LMS including discussions, tests, and individual test questions.
3.1.23 Prefer instructors have the ability to upload files directly in the LMS for on-demand reports.
3.1.24 Prefer students have the ability to get feedback reports within the LMS incorporating all of the features listed above.
3.1.25 Share the minimum word count for reliable AI detection
3.1.26 Provide a description of the detection approach
3.1.27 Share your documented process for challenging AI flags (e.g., student interviews, supplemental drafts), with vendor guidance on due process and appeal timelines. Enable human review and AI scores (detecting full AI, combined human and AI, and human written) to facilitate making academic integrity decisions.
3.1.28 Outline the data residency, retention, and deletion SLAs.
3.1.29 Prefer that instructors are able to control the ability to have multiple drafts for an assignment. This allows for linked assignments (Initial Draft->Second Draft->Final Draft), where earlier drafts will not be included in later assignment draft plagiarism repositories, but all draft copies are kept in the repository for future plagiarism checks.
3.1.30 Provide details on how plagiarism and/or AI detection is supported for programming and markup language file types if available in the tool.
3.2 Respondent Questionnaire
3.2.1 Provide a description of your firm. Include your firm’s experience, number of years in business providing the requested services.
3.2.2 List specific individuals who would be directly assigned to this account. Provide a brief description of their respective roles and responsibilities and resumes.
3.2.3 Provide the names, addresses, and telephone numbers of your three (3) largest clients to whom you have provided similar services during the past three years. Use Attachment A to list contact details of each of these clients.
3.2.4 Address in detail your knowledge, expertise, and experience in providing the services requested in Section 3.1, Scope of Work, and your understanding and ability to comply with the requirements of this RFP.
3.2.5 Provide any other examples, justification, or experiences that would further demonstrate your ability to provide the services requested in this RFP.
3.2.6 Provide your average response time following significant weather event where multiple trees are down.
3.2.7 Provide a list of any additional goods and/or services that your firm provides that are not addressed in the RFP. The District retains the absolute and sole discretion to examine and consider these additional goods/service options for inclusion in the contract awarded under this RFP.
RFP# 3614-10
Section Three: SCOPE OF WORK/SPECIFICATIONS
PROPOSAL REQUIREMENTS
The following is a listing of general and specific criteria used for the evaluation of this RFP. The areas include, but are not limited to:
4.1. MINIMUM REQUIREMENTS
4.1.1 Must be licensed by the State that the business is in, if services requested require such licensure.
4.1.2 Must have carefully read and understand all parts of the RFP and certified that the Proposal is made in accordance therewith.
4.1.3 Must submit written answers to the Respondent Questionnaire. All answers must be in the order in which the questions were asked and labeled with the specific section number.
4.1.4 The Proposer must submit a signed Signature Page (Section 9). Electronic signatures are acceptable. Failure to submit a signed proposal may result in rejection of the Proposal.
4.1.5 Must provide a completed Pricing Schedule (Section 6) signed by an authorized company signatory confirming its offer and acknowledging its understanding of the requirements of this Request for Proposal.
4.1.6 Must acknowledge your agreement to comply with items listed under the Minimum and Specific Requirements of this Request for Proposal.
4.1.7 Must submit a completed copy of the Higher Education Community Vendor Assessment (HECVAT) Lite security questionnaire assessment form. The HECVAT Lite may be downloaded from here:
https://library.educause.edu/resources/2020/4/higher-education-community-vendor-assessment-toolkit
4.2 DEVIATIONS FROM RFP
Proposers must specifically provide a separate listing of each circumstance in which their proposal differs from any terms or conditions of this Request for Proposal. Failure to list such a deviation will result in the terms of the proposal being disregarded in favor of the corresponding term(s) of the RFP. Material deviations from the requirements of this RFP shall result in rejection of the proposal.
The term “material deviations” includes both deviations from the MCCCD contract terms set forth in this RFP and additional contract terms that the Proposer requests the MCCCD to consider. Be aware that the absence of a term on a subject in the RFP, particularly a general contract term and condition, does not mean that the Proposer should feel free to offer one. The MCCCD considers the General Terms and Conditions of this RFP to be a fair allocation of risk between a contractor and the MCCCD. It will not accept terms – revised or additional ones - that shift those risks or provide the Proposer with additional discretion. The Proposer in choosing the respond to this RFP must demonstrate in its Proposal that it accepts the terms upon which the MCCCD is conducting the competition.
To submit deviations the Proposer must state in the separate listing all deviations, including any additional terms, in the following format:
· Title your listing “REQUESTED DEVIATIONS”.
· Cite the specific page and section number of each term and condition change request. Include the original MCCCD RFP Term and Condition.
· Provide a legal redline version of the original RFP language to include the requested change(s). Or immediately below the original RFP Term and Condition include the specific language you want MCCCD to consider adding or replacing.
MCCCD will consider deviation requests, both the total number and the overall scope, in determining the most advantageous offer. Deviations may affect the possibility of an award and any requests should be considered carefully.
Deviations that a winning Proposer submits after it has been selected for award, such as through a vendor standard template contract, will not be considered. If a Proposer submits a Proposal without specific deviations, and the Proposal is accepted by MCCCD, Proposer will be deemed bound by the terms of the RFP without exception.
4.3 SIGNATURE
The Contractor shall furnish and include all requested information with their proposal. Statements are required to be complete and accurate, and the proposal shall be signed by an authorized signatory of the company (sworn to and notarized, if requested). A proposal submitted by an agent will have a current Power of Attorney attached certifying the agent’s authority to bind the Proposer. Omission, inaccuracy, or misstatement may be sufficient cause for rejection of the proposal.
4.4 AWARD CONSIDERATION
From the total information requested, determination shall be made of the Proposer's ability to serve the MCCCD. Only proposals from responsible organizations or individuals, as determined by the MCCCD, which have the capability of providing the required services under this RFP, shall be considered. Representatives from the MCCCD reserve the right to conduct interviews with the individual proposers for clarification of the proposals presented. The MCCCD reserves the right to negotiate any and all provisions presented in the proposals.
4.5 PROTESTS AND APPEALS OF CONTRACT AWARDS
Bid protests or appeals of contracts and awards shall be submitted per Chapter Nine of the Purchasing Procedures Manual.
4.6 FORMAT & SUBMITTAL REQUIREMENTS
The requested information for your RFP submittal is listed below. The documents must be submitted via the MCCCD Procurement Portal before the due date here:
https://maricopa.bonfirehub.com/portal/?tab=openOpportunities Proposals that do not follow the Format and Submittal Requirements as outlined in the table below may be disqualified.
| Document Name |
| File Type (PDF, Word, Excel, etc.) |
| # of Files Permitted |
| Required/Optional |
| Signature Page |
| PDF (.pdf) |
| One (1) |
| Required |
| Scope of Work |
| PDF (.pdf) |
| One (1) |
| Required |
| Attachment A |
| PDF (.pdf) |
| One (1) |
| Required |
| Attachment B |
| PDF (.pdf) |
| One (1) |
| Required |
| Deviations to Terms and Conditions |
| PDF (.pdf) |
| One (1) |
| Optional |
| Pricing Schedule |
| PDF (.pdf) |
| One (1) |
| Required |
| Respondent Questionnaire |
| PDF (.pdf) |
| One (1) |
| Required |
| HECVAT |
| PDF (.pdf) |
| One (1) |
| Required |
| Supplemental Information |
| Any |
| Multiple |
| Optional |
Important Notes:
· Take note of the type and number of files allowed. The maximum upload file size is 1000 MB.
· Do not embed any documents within your uploaded files. They will not be accessible or evaluated.
· Uploading documents may take significant time, depending on the number and size of the file(s) and your Internet connection speed.
· You will receive an email confirmation receipt with a unique confirmation number once you finalize your submission.
RFP# 3614-10
Section Four: PROPOSAL REQUIREMENTS Rev 022718
· Minimum system requirements: Internet Explorer 11, Microsoft Edge, Google Chrome, or Mozilla Firefox. JavaScript must be enabled. Browser cookies must be enabled.
RFP# 3614-10
Section Five: EVALUATION CRITERIA Rev 090817
EVALUATION CRITERIA
The following is a listing of general and specific criteria used for the evaluation of this RFP. The areas include, but are not limited to:
5.1 General quality of responsiveness of proposer:
A. Ability to meet all terms and conditions B. Completeness and thoroughness of proposal C. Grasp of scope of work to be performed D. Description of approach to be taken E. Evidence of effective organizational and management practices F. Qualifications of personnel G. Experience and past performance
5.2 Specific areas that will be evaluated and scored except as described in STEP THREE below:
A. Past experience in providing comparable services to other clients.
B. Responses to Minimum and Specific Requirements.
C. Respondent Questionnaire responses.
D. Pricing.
Proposals will be evaluated in accordance with the following three-step process:
STEP ONE - Verification of each proposer's compliance with the RFP general terms and conditions as listed in Section 1, 2, 7, and 8 of this RFP.
STEP TWO - Verification of each proposer's compliance that all required written responses/confirmations are thoroughly submitted.
STEP THREE – All proposals meeting the criteria as presented in Steps One and Two will be evaluated with a "points-earned compliance matrix". An evaluation committee will evaluate and score the proposals. The proposals will be ranked on a "points-earned" technical, service and financial compliance matrix. The evaluation committee may continue to evaluate proposals after the initial scoring of them by any means that it deems reasonable. If the evaluation committee schedules oral presentations, the presentations may or may not be scored and that scoring may, but is not required to be added to the previous scoring of the proposals. The evaluation committee reserves the right to use additional advisory committees or subject matter experts at any time during this RFP to assist with the evaluation.
Section Six: EVALUATION CRITERIA Rev 090817
PRICING SCHEDULE
The undersigned has read and understands all conditions and terms of RFP 3613-10, is authorized to submit this proposal on behalf of the company, and hereby offers to perform the services for the pricing indicated below:
6.1 Cost/Fee Proposal
| Annual License Cost | $____________ |
| One Time Set Up Cost | $____________ |
6.2 Other required services/fees, if any, not specifically requested in the RFP (list below)
Costs/Fees listed shall include all overhead and profit. No billing will be accepted that shows any other costs than those listed. This includes, but is not limited to, travel, any out-of-pocket costs, meetings, secretarial, printing, delivery, rent, phone calls, postage, overnight mail service, accounting, fuel charges, office supplies, etc.
Billing to MCCCD should be in a manner in which all locations and their associated costs can be identified for our accounting processes.
Any contractor that MCCCD is doing business with must agree to e-billing.
Please confirm that the authorized agent preparing this Proposal has read, understands, and will ensure his/her firm’s compliance with the provisions of this section:
Authorized Agent’s Name and Initials: __________________________________ _____
You may submit a more detailed pricing schedule (using the same formatting) in lieu of the above as an attachment to this page, but the pricing schedule must be completed, initialed and included with your proposal.
RFP# 3614-10
Section Seven: PRICING SCHEDULE Rev 090817
SPECIAL TERMS AND CONDITIONS
**Any deviations to the Special Terms and Conditions MAY be considered in this proposal** These General Terms and Conditions, the other provisions of the RFP and amendments to it, the Proposer proposal, and MCCCD’s purchase order terms (“Contract Documents”) along with any engagement letter will constitute the provisions of the contract between MCCCD and successful Proposer (“Contract”). MCCCD reserves the right to negotiate with the successful Proposer and modify any of the provisions of the Contract upon mutual written agreement of the parties. The RFP, amendments to it, and MCCCD’s purchase order terms will take precedence over any inconsistent terms in a proposal or other documents. The term “days” as used in this Contract means business days, unless otherwise specified.
7.1 INSURANCE REQUIREMENTS
The insurance requirements herein are minimum requirements for this contract and in no way limit the indemnity covenants contained in this contract. MCCCD in no way warrants that the minimum limits contained herein are sufficient to protect Contractor from liabilities that arise out of the performance of the work under this contract by the contractor, its agents, representatives, employees, or subcontractors and the contractor is free to purchase additional insurance.
Contractor shall maintain during the term of this Agreement insurance policies described below issued by companies licensed in the State of Arizona or hold approved non-admitted status on the Arizona Department of Insurance List of Qualified Unauthorized Insurers. Insurers shall have an A.M.
Best rating of A - VII or better. At the signing of this Agreement, Contractor shall furnish the MCCCD with certificates of insurance evidencing the required coverages, conditions, and limits required by this Agreement. Certificate of Insurance shall be sent to:
Representative’s Name (person who is collecting the certificate) College or District Office and address Phone number and email address
The insurance policies, except Worker’s Compensation, must be endorsed as require by this written agreement to name MCCCD and its agents, officers, officials, employees, and volunteers as additional insureds or its equivalent:
The Maricopa County Community College District and its agents, officers, officials, employees, and volunteers are hereby named as additional insureds as their interest may appear.
The insurance policies shall contain a waiver of subrogation endorsement in favor of Maricopa County Community College District, its agents, officers, officials, employees, and volunteers for losses arising from work performed by or on behalf of the contractor.
Contractor and, if applicable, any subcontractors will notify the MCCCD Risk Manager by certified mail promptly if it receives notice or the expiration, cancellation, suspension, or material change in its insurance coverage, but in no case fewer than 30 days before the action specified in the notice. The Contractors insurance must be primary, and any insurance or self-insurance maintained by MCCCD will not contribute to it. If any part of the Agreement is subcontracted, these insurance requirements also apply to all subcontractors.
The contracting College or District Office, with approval from MCCCD Risk Management, reserves the right to review or make modifications to the insurance limits, required coverages, or endorsements throughout the life of this contract, as deemed necessary. Such action between the College or District Office and MCCCD Risk Management will not require a formal Contract amendment but may be made by administrative action.
In the event any professional liability insurance required by this Contract is written on a “claims made” basis, Contractor warrants that any retroactive date under the policy shall precede the effective date of this Contract; and that either continuous coverage will be maintained or an extended discovery period will be exercised for a period of three (3) years beginning at the time work under this Contract is completed. Contractor’s work or services and must be evidenced by annual certificates of insurance.
Contractor shall notify the MCCCD Risk Manager by certified mail promptly if it receives notice or the expiration, cancellation, suspension, or material change in its insurance coverage, but in no case fewer than 30 days before the action specified in the notice. The Contractor’s insurance must be primary, and any insurance or self-insurance maintained by MCCCD shall not contribute to it. If any part of the Contract is subcontracted, these insurance requirements also apply to all subcontractors.
Commercial General Liability (CGL) – Occurrence Form Policy shall include bodily injury, property damage, and broad form contractual liability coverage, including but not limited to, the liability assumed under the indemnification provisions of this Contract.
· General Aggregate $2,000,000
· Products – Completed Operations Aggregate $1,000,000
· Personal and Advertising Injury $1,000,000
· Damage to Rented Property $50,000
· Each Occurrence $1,000,000
If applicable, Commercial Automobile Liability insurance with a combined single limit for bodily injury and property damage of not less than $1,000,000.00 each occurrence with respect to the Contractor’s and, if applicable, the sub-contractor’s owned, hired, and non-owned vehicles.
Worker’s Compensation insurance with limits statutorily required by any Federal or State law and Employer’s Liability insurance of not less than $1,000,000 for each accident, $1,000,000 disease for each employee, and $1,000,000 disease policy limit.
If applicable, Professional Liability insurance covering acts, errors, mistakes, omissions rising out of the work or services performed by the Contractor, or any person employed by the Contractor, with a limit of not less than:
· Each Claim $2,000,000
· Annual Aggregate $2,000,000
Network Security and Privacy Liability coverage in an amount not less than $5,000,000 per claim and annual aggregate, covering all acts, errors, omissions, negligence, infringement of intellectual property (except patent and trade secret); network security and privacy risks, including but not limited to unauthorized access, failure of security, breach of privacy perils, wrongful disclosure, collection, or other negligence in the handling of confidential information, privacy perils, and including coverage for related regulatory defense and penalties; data breach expenses, in an amount not less than $5,000,000 and payable whether incurred by MCCCD or Contractor including but not limited to consumer notification, whether or not required by law, computer forensic investigations, public relations and crisis management firm fees, credit file or identity monitoring or remediation services in the performance of services for MCCCD or on behalf of MCCCD hereunder. The policy shall include coverage for third party claims. The policy shall contain an affirmative coverage grant for contingent bodily injury and property damage emanating from the failure of the technology services or an error or omission in the content/information provided. Such insurance shall be maintained in force at all times during the term of the agreement and for a period of three years thereafter for services completed during the term of the agreement. MCCCD shall be given at least 30 days’ notice of the cancellation or expiration of the aforementioned insurance for any reason.
Please also refer to Attachment B, Data Confidentiality and Security Addendum, incorporated herein by reference.
7.2 OBLIGATIONS TO PROTECT CONFIDENTIAL INFORMATION
PLEASE ALSO REFER TO ATTACHMENT B, DATA CONFIDENTIALITY AND SECURITY ADDENDUM, INCORPORATED HEREIN BY REFERENCE.
7.3 RECORD AND DATA RETENTION, OWNERSHIP, ACCESS AND DECOMMISSIONING
7.3.1 As a political subdivision of the State of Arizona, MCCCD is subject to applicable laws related to the inspection and production of public records. A public record entails any record, either paper or electronic, made by a public officer (including members of the Governing Board, faculty, staff and administrators) and kept as a memorial of an official transaction. Pursuant to Arizona Revised Statutes §41-151.12, MCCCD must retain records according to established retention periods. Records required for ongoing or foreseeable official proceedings such as audits, lawsuits or investigations must be retained until released from such official proceedings. Thus, if applicable, the Contractor’s hosted system shall have the ability to:
A. Archive records according to variable time periods/life cycles;
B. Search and retrieve records based upon content;
C. Place a litigation hold on records to ensure that they are not deleted;
D. Grant direct access to MCCCD for its own search and production of records;
E. Preserve meta data;
F. Produce electronic records in their native format; and G. Comply with the Americans with Disabilities Act.
7.3.2 MCCCD owns all of the records and data of which Contractor has custody on MCCCD’s behalf. Contractor will not disclose, use, destroy, transfer or otherwise manage those records and data except as provided in this Contract or, if the Contract is silent, without the express written approval of an authorized MCCCD representative. Contractor will work with MCCCD to transfer all of MCCCD’s records and data to MCCCD on the termination or expiration of this Contract.
7.3.3 Contractor agrees to provide MCCCD access to records and Confidential Information that Contractor holds or uses on behalf of MCCCD upon written request of MCCCD with reasonable advance notice. Further, Contractor agrees to make amendments to Confidential Information as directed by MCCCD and will maintain a record of those changes.
7.3.4 Contractor agrees to maintain, and provide to MCCCD if requested, a record of when and to whom Confidential Information is disclosed.
7.3.5 MCCCD agrees to provide Contractor with adequate notice of any further limitations or restrictions on the use of Confidential Information, and modifications to the amendment of records or accounting of disclosures.
7.3.6 Confidential Information of the disclosing party will be returned to the disclosing party or securely destroyed promptly upon request of the disclosing party without retaining any copies thereof, with any destruction confirmed in writing by receiving party, with any destruction confirmed in writing by receiving party, except to the extent copies are required by law to remain with Contractor.
7.4 MCCCD EXTERNAL ENTITY SECURITY AND HOSTING PRACTICES AND STANDARDS
PLEASE REFER TO ATTACHMENT B, DATA CONFIDENTIALITY AND SECURITY ADDENDUM, INCORPORATED HEREIN BY REFERENCE I. Data Management/Protection Deletion of Environments: Upon termination of services or at MCCCD’s request, External Entity will delete the Environments located on External Entity computers in a manner designed to ensure that they cannot reasonably be accessed or read, unless there is a legal obligation imposed on External Entity preventing it from deleting all or part of the Environments. Unless otherwise specified in writing, External Entity will archive Environments on tape for six months following termination of the services. MCCCD shall be entitled to request a recovery of such backed-up Environments within the six months following termination.
Disclosure of Data: External Entity will not disclose data located on External Entity systems, including text and images, except in accordance with MCCCD’s contract, MCCCD’s instructions, or to the extent required by law. External Entity will use diligent efforts to inform MCCCD, to the extent permitted by law, of any request for such disclosure before disclosure is made.
Crisis Management and Escalation Management: External Entity policy will provide a detailed plan to address an identified infection or high-risk security breach (high-risk event). Such policy will include the detailed activities that address escalation of the resolution of the high risk event, up to an executive level crisis management.
II. Access Control Account Provisioning and Passwords: External Entity must maintain the following standards for provisioning access to and creating passwords for the Environments that are in the control of External Entity:
· Access is provisioned on a need-to-know basis.
· Passwords conform to the strong password guidelines that include complexity, expiration, duplicity and length. Passwords will not be written down or stored online unencrypted.
· Passwords are treated as External Entity confidential information.
· At MCCCD’s request, External Entity will agree with MCCCD on a schedule for periodic password changes.
· User IDs and passwords to MCCCD’s systems are not communicated to any other person without MCCCD’s prior authorization.
General Access: In the event of employee terminations, deaths or resignations, External Entity will take immediate actions to terminate network, telephony and physical access for such former employees. External Entity security will periodically review accounts of terminated employees to verify that access has been terminated and that stale III. Additional External Entity Practices Computer Virus Controls: External Entity must maintain the following computer virus controls for computers issued to External Entity employees:
· External Entity maintains a mechanism within the External Entity network that scans all email sent both to and from any External Entity recipient for malicious code and deletes email attachments that are infected with known malicious code prior to delivery.
· External Entity requires all External Entity employee laptops or other devices that can access MCCCD’s network to be loaded with virus protection software. External Entity maintains mechanisms to ensure that virus definitions are regularly updated, and that updated definitions are published and communicated to employees and other device users. These mechanisms also give employees and other device users the ability to automatically download new definitions and update virus protection software. From time to time, External Entity security will conduct compliance reviews to ensure employees and other device users have the virus software installed and up-to-date virus definitions on all desktops and laptops.
Information Security Managers: External Entity should have ISMs, who function as advocates within External Entity and carry the accountability to:
1. Ensure information security awareness to External Entity employees and management, and
2. Work collectively with that group to help implement and comply with External Entity’s corporate security practices, policies and initiatives.
IV. Human Resources Security Personnel: All External Entity employees, independent contractors, and temporary employees must be required to abide by the External Entity code of ethics and by MCCCD rules, when visiting MCCCD sites. External Entity must place strong emphasis on reducing risks of human error, theft, fraud, and misuse of facilities. External Entity’s efforts should include screening personnel, making personnel aware of security policies, and training employees to implement security policies. For example, employees are expected to have a clear understanding of password policies and policies concerning the handling of confidential information (in any form or shape).
Employee Security Requirements External Entity employees must be required to take various measures to protect the security of the Environments. Employee obligations include written confidentiality agreements and compliance with company policies concerning protection of confidential information (e.g., External Entity code of conduct, acceptable use and information protection policies). Employees also are required to take the following measures to protect MCCCD’s data:
· Store materials containing data securely and share those materials internally only for the purposes of providing the services.
· Dispose of paper copies of confidential materials and materials containing data in shredding bins designated for confidential information, and not in non-secure recycling bins or trashcans.
Subcontractors
· External Entity will obtain a written confidentiality agreement from each subcontractor before the subcontractor provides services. In addition, subcontractors that require access to MCCCD’s Environments are required to sign a services provider agreement and a network access agreement. Included in the services provider agreement are the External Entity standards, which require the subcontractor to implement physical, technical and administrative safeguards consistent with External Entity’s obligations under MCCCD’s order and this document.
· External Entity is responsible for assuring that its subcontractors access, use, and protect the security of the Environments in a manner consistent with the terms of MCCCD’s order and this document.
Employee Training
· All External Entity employees are required to complete information protection awareness training upon hiring and at least every two years thereafter. The course instructs employees on their obligations under the various central External Entity privacy and security policies. The course also trains employees on data privacy principles as well as data handling practices that may apply to their jobs at External Entity and are required by company policy, including those related to notice, consent, use, access, integrity, sharing, retention, security and disposal of data.
· External Entity performs periodic compliance reviews to determine if employees have completed the online data privacy awareness-training course. If External Entity determines that an employee has not completed this training, the employee will be promptly notified and instructed to complete such training…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .