Parking Management System

19 December 2022 Parking Management System Arizona State University is requesting proposals from qualified firms for a Parking Management solution at several locations on our campuses. 19 December 2022 Open 12/19/2022 12:00 PM MST Type Request for Proposal Close 2/9/2023 12:00 PM MST Number 322302 Currency US Dollar Sealed Until 2/9/2023 12:00 PM MST 19 December 2022 Contacts Belinda Biggs bmbiggs@asu.edu 19 December 2022 Commodity Codes Commodity Code Description 43-02 Software 19 December 202219 December 202219 December 202219 December 202219 December 202219 December 202219 December 202219 December 202219 December 2022 mailto:bmbiggs@asu.edu Arizona State University is seeking proposals for a comprehensive Parking Management solution that includes technology and applications to help further our smart garage/smart city goals. Other Important Information: For the purposes of the

RFP, the buyer is Belinda Biggs, email Belinda.biggs@asu.edu Bid Open Date: 12:00 PM, AZ Time, 12/19/2022 Deadline for Inquiries: 12:00 PM, AZ Time, 1/19/2023 Bid Close Date: 12:00 P.M., AZ Time, 2/9/2023 Description Required to View Event Prerequisites Required to Enter Bid 19 December 2022 1. Review the Intent, Background and Term of the RFP 2. Review the Instructions to Proposers 3. Review the Pre-Proposal Conference information 4. Review the Evaluation Criteria instructions 5. Review the Small Business & Small Disadvantaged Business Information 6. Review the Cooperative Agreements Information 7. Review Sustainability Requirements 8. Complete the attached Mandatory Certifications and upload in this section 9. Proposer must acknowledge and accept ASU COVID-19 policies. 10. Review the Proprietary/Confidential Statement instructions. 19 December 202219 December 202219 December 202219 December 202219 December 202219 December 202219 December 2022 Buyer Attachments There are no Buyer Attachments added to this event. 19 December 202219 December 202219 December 202219 December 202219 December 202219 December 2022 Questions Required Questions Group 1.1: Scope Overview Instructions: 1.1.1 The University will not consider any proposals that describe a future release. The solution offered must exist today, although specific functionality in future releases can be mentioned and include the availability and/or release date. 1.1.2 A test version of the solution offered must be available for evaluation. 1.1.3 The system shall accommodate at a minimum any or all of the following process functionality: The Parking Management System shall be equipped to offer a multi faceted integrated solution that is designed to provide a robust and advance technology application which incorporates the following systems: Permit and Customer Record Management, Parking Enforcement, Citation and Appeal Management, Data and Financial Management, Parking Access and Revenue Control and Reporting Functionalities. 1.1.4 If not, describe why or how you may be able to meet this requirement. Group 1.2: Permit and Customer Record Management Instructions: 1.2.1 The PERMIT AND CUSTOMER RECORD MANAGEMENT system shall have the ability to securely process sales in person and online for multiple permit types including but not limited to; • Student • Faculty/staff • Community members • Suppliers and campus fleet. 1.2.2 If not, describe why or how you may be able to meet this requirement. 1.2.3 The PERMIT AND CUSTOMER RECORD MANAGEMENT system shall be able to support multiple time period permits such as annual and monthly permits; record and retain full history of permit purchases, renewals, and expirations; allow the creation, management and updating of accounts by parking staff; allow updating by the account holder online based on eligibility, restrictions and security level access. 1.2.4 If not, describe why or how you may be able to meet this requirement. 1.2.5 The PERMIT AND CUSTOMER RECORD MANAGEMENT system shall provide the ability to link, track and query all components of an account, such as but not limited to; • Permit • Person • Vehicle • Citation • Financial transaction history AND Events, Coupon codes, Promo codes, Validations. 1.2.6 If not, describe why or how you may be able to meet this requirement. 1.2.7 The PERMIT AND CUSTOMER RECORD MANAGEMENT system shall provide the ability to maintain, track, report permit inventory and support third party PERMIT Fulfillment. 1.2.8 If not, describe why or how you may be able to meet this requirement. 1.2.9 The Desired Enhancement is an automated system supporting recurring credit card charges. 1.2.10 If not, describe why or how you may be able to meet this requirement. Group 1.3: Parking Enforcement System Instructions: 19 December 202219 December 202219 December 202219 December 202219 December 2022 1.3.1 The PARKING ENFORCEMENT system shall a. Provide a real-time secure data exchange between system components and field staff, such as vehicle information, issued permits, prior citation history, scofflaw information, boot and tow eligibility and any daily or field notes. b.Provide the ability for field staff to view and query all linked components of accounts, such as permit, vehicle and citation information. c. Provide secure real-time ability for field staff to upload information into the system, such as photos, electronic chalking, notes and citation issuance. 1.3.2 If not, describe why or how you may be able to meet this requirement 1.3.3 In addition to the above, the PARKING ENFORCEMENT System shall d. Provide the ability for enforcement staff to issue notification types such as warnings, citations, scofflaws, chalk-times and boots. e. Provide a secure link over cellular and/or Wi-Fi networks. f. Provide the ability to integrate with Genetec License Plate Recognition “LPR” (vehicle mounted and stationary) technology and equipment. g. Provide back-office ability to create, customize and manage multiple citation and notification types. h. Provide a real time integration with digital parking systems for enforcement of payments. 1.3.4 If not, describe why or how you may be able to meet this requirement 1.3.5 The desired system enhancement is the ability to pay fees via a handheld unit. 1.3.6 If not, describe why or how you may be able to meet this requirement. Group 1.4: Citation and Appeal Management System Instructions: 1.4.1 The CITATION AND APPEAL MANAGEMENT system shall: a. Provide a citation appeal process. Both appeal and payment processes must have a secure online presence that provides a user friendly, intuitive process and recordkeeping. b.Provide a customer portal, secure on-line access with the ability to interact with the permit management system to view citation history with field notes, photos and correspondence history. c. Provide the ability to import supporting documents in multiple formats. d. Provide the ability to place a citation on “hold” while the appeal is being processed. 1.4.2 If not, describe why or how you may be able to meet this requirement. 1.4.3 The CITATION AND APPEAL MANAGEMENT system shall also: e. Provide the ability to accept payment and navigate multiple citation parameters including a late fee or early pay discount. f. Provide the ability to void citations or warnings that can be managed completely in-house without the need for external workflow. g. Ensure each account has audit capability. h. Provide customizable communication options that must include text messages, e-mails and mailed letters. 1.4.4 If not, describe why or how you may be able to meet this requirement. Group 1.5: Data and Financial Management System Instructions: 1.5.1 The DATA AND FINANCIAL MANAGEMENT system shall provide multiple payment options through a secure in office integrated POS system and a secure on-line system. 1.5.2 If not, describe why or how you may be able to meet this requirement. 1.5.3 Payment options must include, but are not limited to; • Credit card (PCI Compliant) • Account billing • Payroll deduction • University department billing • Check • On-line pay options (PCI Compliant) • Intra-departmental transfers. 1.5.4 If not, describe why or how you may be able to meet this requirement. 19 December 202219 December 202219 December 202219 December 202219 December 2022 1.5.5 The DATA AND FINANCIAL MANAGEMENT system shall provide financial reporting of cash and non-monetary transactions, such as • Permit sales • Returns/cancellations • Holds • Citation payments • Appeal reductions • Write offs • Boot releases • Purchases of any miscellaneous services. 1.5.6 If not, describe why or how you may be able to meet this requirement. 1.5.7 The DATA AND FINANCIAL MANAGEMENT system shall provide the ability to link a general ledger “G/L” account number to each financial transaction. The University uses Workday. The G/L information must be available with the financial information (description and amount). 1.5.8 If not, describe why or how you may be able to meet this requirement. 1.5.9 In addition, the System must have unique logins for all users; User management controls with internal user access to restricted areas of the software; Provide the ability to restrict access to payment types based on customer type, user type, item purchased, etc.; Provide financial integrity controls with auditing and reconciliation tools. 1.5.10 If not, describe why or how you may be able to meet this requirement. 1.5.11 The System shall allow for data import/export functionality in common formats, such as but not limited to text fixed length, CSV, XML, XLSX, tab delimited files; Allow the creation of custom fields for file exports/integrations, etc.; 1.5.12 If not, describe why or how you may be able to meet this requirement. 1.5.13 The System shall provide a unique receipt number with defined transactional information; Provide the ability for end of day, end of month and end of year close out options with the ability for reconciliation reporting. 1.5.14 If not, describe why or how you may be able to meet this requirement. 1.5.15 The Desired System Enhancements are a. Workday Integration b. PeopleSoft Integration c. Bill to Student Accounts and Payroll Deduction Integration 1.5.16 If not, describe why or how you may be able to meet this requirement. Group 1.6: Parking Access and Revenue Control Instructions: 1.6.1 The Parking Access and Revenue Control System shall have: a. Entry/Exit Station Gated and/or Gateless solution for all garages listed. b.Pay Stations in Lane or in Surface Parking Lots. c.Fee Computers (IPC). d.Barrier Gate and/or LPR or LPI. e.PARCs Software which includes Web Workstation, Access Control, Revenue Management, Count & Monitoring, Report Generator and Validation System. 1.6.2 If not, describe why or how you may be able to meet this requirement. Group 1.7: Reporting Instructions: 1.7.1 The reporting functionalities shall include data insights in real time and cloud based dashboards, with all modes of transportation separated and the ability to provide annual benchmarking. 1.7.2 If not, describe why or how you may be able to meet this requirement. 1.7.3 The dashboards shall harness effective analytics for strategic guided decisions to include but not be limited to a.Standardized and customizable report options eg. Tableau etc. b. The capability to export data to common workplace tools, such as Word or Excel. c. Provide unlimited report views, visual representation of key performance indicators, and the ability to store queries in multiple output formats. d. The capability to run schedule reports on a regular basis which includes the ability to choose the day/time and the frequency. e.Successful Proposer must provide the University a monthly copy of University's data for retention in a format designated by the University. 1.7.4 If not, describe why or how you may be able to meet this requirement. 1.7.5 The Desired System Enhancement includes a robust dashboard that is easy to understand by non parking and transportation specialists. 19 December 202219 December 202219 December 202219 December 202219 December 2022 1.7.6 If not, describe why or how you may be able to meet this requirement. Group 1.8: Additional Requirements Instructions: 1.8.1 SYSTEM REQUIREMENTS: Shall include server & database hosting and management, including all software installations & updates, as well as third party integration updates and maintenance. Proposer shall provide a method for import and export of data on a recurring basis, either through, API, ETL process, or automated file transfer. Meet and agree to University’s data security and accessibility requirements outlined in ASU Terms and Conditions. 1.8.2 If not, describe why or how you may be able to meet this requirement. 1.8.3 System Operations shall include a.The ability to provide technical support, including on-call and online technical assistance, and onsite technician to repair equipment. b. In-house training and software usage resources that are updated as the software changes. c. Customizable documentation of the University’s use of the system. 1.8.4 If not, describe why or how you may be able to meet this requirement. 1.8.5 Integrations shall include a. Support integration methods and required data elements. b. Secure transfer of employee and student data to the parking system records. c. The ability to transfer parking related account charges to student accounts, accept student demographic and enrollment data as well as student housing status and address. d. The ability to import employee demographic and employment status. 1.8.6 If not, describe why or how you may be able to meet this requirement. 1.8.7 Proposers shall develop and/or configure all approved interfaces, reports, workflows and application customizations. 1.8.8 If not, describe why or how you may be able to meet this requirement. 1.8.9 PROJECT MANAGEMENT: Proposers shall be responsible for developing and maintaining the Project Plan and Project Schedule. The Project Plan and Project Schedule shall define and reflect the Proposer’s approach to executing the scope of work. 1.8.10 If not, describe why or how you may be able to meet this requirement. 1.8.11 Project schedules and changes shall be reviewed and approved by the University. 1.8.12 If not, describe why or how you may be able to meet this requirement. 1.8.13 Test Planning : The successful Proposer shall provide necessary test script procedures and templates to complete the testing process. The test scripts should identify the process or business scenario being tested. The successful Proposer shall support University’s testing by establishing adequate test environments, troubleshooting problems, resolving issues, and fixing defects. 1.8.14 If not, describe why or how you may be able to meet this requirement. 1.8.15 Training : a.Successful Proposer will provide comprehensive training on all system functionalities to University’s End Users and Administrator level users. b.Successful Proposer will be informed of the number of users at time of award and an unlimited number of client access users with read only right. c.Provide training and consulting services on the development and maintenance of metadata records and business glossaries. 1.8.16 If not, describe why or how you may be able to meet this requirement. 1.8.17 Maintenance and Support : The proposed system must include continually updated documentation on system configuration, user processes, as well as a user knowledge base, customer forum, and direct support through email or a web-based support portal, and phone. 1.8.18 If not, describe why or how you may be able to meet this requirement. 1.8.19 Post Live Performance And Reliability Period : a.The successful Proposer shall provide online support to assist in the resolution of production issues, to apply any delayed software fixes, and to troubleshoot issues. 1.8.20 If not, describe why or how you may be able to meet this requirement. 19 December 202219 December 202219 December 202219 December 202219 December 2022 1.8.21 Should University require additional assistance and/or modifications, the following support should be included in the rate identified in the bid response (Financial Proposal Section). Support shall be by telephone, onsite and/or online as required by the University and can be used for the following issues, but not limited to: 1. Technical Errors. 2. Questions regarding system use, tools, reports, and other functionality. 3. Data issues. 4. Performance issues. 5. Connectivity issues. 6. Patches and fixes. 1.8.22 If not, describe why or how you may be able to meet this requirement. 1.8.23 Successful Proposer will also proactively provide to University version upgrades to maintain security, regulatory and legal compliance as follows: 1.Customer (User Groups) driven changes either reflecting functional deficiencies identified by customers or new business requirements, or reporting requirements identified by customers. 1.8.24 If not, describe why or how you may be able to meet this requirement. 1.8.25 EXIT STRATEGY AND TRANSITION OF SERVICES : Proposers must provide their exit strategy in the event the University or the successful Proposer terminates the contract. This includes, but not limited to, the client data strategies and possible transition to another supplier. 1.8.26 If not, describe why or how you may be able to meet this requirement. 1.8.27 The successful Proposer must provide complete access to all data and information, as defined in Arizona State University Standard Terms and Conditions (ASU Data) within 30 days of notification. 1.8.28 If not, describe why or how you may be able to meet this requirement. 1.8.29 Data inserted into the Parking Software Solution from University, its members, or other entities shall be the exclusive property of University. Should University contract with another Parking Software provider at the end of the existing contract term or at any time upon request, the successful Proposer shall provide to University a complete electronic copy of ASU data in an easy to read and reasonably transferable format in keeping with industry standards. 1.8.30 If not, describe why or how you may be able to meet this requirement. 1.8.31 SERVICE LEVEL PERFORMANCE REQUIREMENTS: The Service Level descriptions and requirements are as attached. The Successful Proposer shall use commercially reasonable efforts to exceed the Service Level Performance Requirements. Please acknowledge and confirm your acceptance to the attached Service Level Performance Requirements. Group 2.1: Minimum Mandatory Requirements Instructions: Proposers who do not meet the following mandatory requirements will be deemed non-responsive and will not be given further consideration. 2.1.1 Proposals must include profiles of existing clients, which may include Higher Education clients, in support of any or all of the following: • A permit and customer record management system • Parking enforcement including integration with Genetec or other LPR technologies, the ability to aggregate and verify payments from multiple sources • Citation and appeal management • Data and financial management . Parking Access and Revenue Control • Dynamic Reporting tool with easily customizable reports eg. Tableau etc. • System security that operates with current University and Parking software • Single sign on capability for parking staff & customers through LDAP, Shibboleth or similar technology. 2.1.2 Please provide evidence of three (3) consecutive years’ of experience, at the minimum, in Parking Software solutions, that speak to your ability to meet the requirements provided within this RFP. 2.1.3 Please provide professional references of Higher Education experience of similar scope and size. 2.1.4 Only one (1) submission per data catalog and governance solution is permissible. Parking software Solutions that utilize a third party for implementation must ensure that only one (1) SOLICITATION response is submitted to be considered. 19 December 202219 December 202219 December 202219 December 202219 December 2022 2.1.5 Sandbox Environment : Responsive Proposers will be required to build a “sandbox” environment and made available for presentation to the Evaluation Team within five (5) business days of notification to present. Proceeding the presentation, access to the sandbox environment must be made readily available to members of the Evaluation Team, at no cost to the University. 2.1.6 The successful Proposer shall provide access to a sizable number of designated hands-on usability testers from all campuses of the Arizona State University in the Sandbox Environment. This may include faculty, staff, administrators, individuals with disabilities, technology professionals, and students. 2.1.7 In the event that more than one service provider/supplier is selected, each supplier shall collaborate to create a seamless integration of the parking management solution. Group 2.2: Company Overview and Key Personnel Instructions: 2.2.1 Please provide a brief description of the firm’s business or corporate profile including the company or business name, its registered address, the number of years in business, the type of operation, experience, strengths in the industry and business philosophy. 2.2.2 Your proposal shall include the organizational structure of the firm including the organizational structure for the management and operation of the services requested and/or provision of the items referred to in this RFP. 2.2.3 Identify the individuals who will serve as the organization’s primary contact, Project Manager and all other key personnel who will be involved in the installation, training and implementation of the system, including their positions, technical experience and resumes. Support personnel, as applicable, shall also be listed including a description of assignment and responsibilities, resumes, and an estimate of the time (normal Business hours, Monday through Friday, Mountain Daylight/Standard Time) each would be devoted to this project and any other pertinent information. 2.2.4 Please identify the executive team member directly in charge of overseeing the project. The executive team member shall be available during and after normal business hours to assist with any urgent situations. Contact information for this individual shall be provided at the time of contract award. Changes to the assigned executive team member, except for those resulting from separation of services, require prior written consent from the University. The replacement shall have qualifications which meet or exceed the original staff member proposed or the staff member holding the position previously and shall be approved by the University. 2.2.5 Key Onsite Technical Support: Proposers are requested to provide a detailed overview of key on-site personnel supporting the ASU Parking Management Program. Please include; organization charts, scope of responsibilities (including the systems or the equipment supported), rate structures and years of experience. Also, please indicate if these individuals are only on-site for transition or installation or if they will be resident / dedicated for the contract term. These elements should be added to the pricing proposal (Financial Proposal Section). 2.2.6 Proposers must state what is considered as During Business Hours and After BusinessHours. Designated support contacts must be included for such. 2.2.7 Please provide a statement documenting all open or pending litigation initiated by Proposer or where Proposer is a defendant or party in any litigation that may have a material impact on the Proposer’s ability to deliver the contracted services. Group 2.3: Methodology and Capability Instructions: Your proposal shall address the following: 2.3.1 The method for retrieval and updating of vehicle records from state sources. 2.3.2 Experience in providing a Parking Management Software to a Tier 1 Level Research University that manages over 10,000 + parking spaces or comparable. 2.3.3 Examples of how the system manages permit, vehicle, citation, financial, and customer records as well as inventory and utilization of parking spaces on a university campus. 2.3.4 Parking enforcement operations, including integration with Genetec or other LPR technologies, the ability to aggregate and verify payments from multiple sources such as mobile payment vendors, physical pay stations, meters, and web based systems as well as a citation and appeal management solution. 2.3.5 Ability to integrate with campus enterprise software eg. Workday, Peoplesoft. 2.3.6 Overall parking system management operations on a daily, monthly and annual operational period. 2.3.7 Ability to price and restrict permits sales by time of day, day of week, months, semester, and annual access. 19 December 202219 December 202219 December 202219 December 202219 December 2022 2.3.8 Event management and parking payment solutions included in the management software. 2.3.9 Requirements for a host vehicle, vehicle hardware requirements for LPR operations and identify camera systems that are compatible with the proposed system. 2.3.10 Real time integration with Phone App and Digital parking systems for enforcement of payments. 2.3.11 Information that will be provided to field staff and the ability to customize the system and the information. 2.3.12 All supported third party and partner integrations. (Describe type of data integration.) Group 2.4: Project Management Instructions: 2.4.1 Project Plan/Schedule a. Proposals shall include the following: A Project Plan which outlines the Project’s roadmap for key project activities, but not limited to infrastructure setup, needs analysis, configuration, security, report and interface development, testing data conversion, and training. Project Schedule which includes a high level Implementation/integration plan (timeline), highlighting key elements and date for a successful execution. 2.4.2 Please address your approach for effective communication including but not limited to project management phone conferences accessible by a toll‐free dial‐in number, ongoing and continual communication via e‐mails and phone conversations with the University and monthly reports of contract activity and events. 2.4.3 Please discuss your process to accommodate changes on timelines or project schedules, and the required approval processes. 2.4.4 TEST PLANNING : Proposers shall submit a Test Plan that outlines the timing and tasks to accomplish the testing needed to successfully deploy the application in production. The Test Plan shall be a MS Word document that outlines a detailed test plan that identifies the test areas and types of tests to be performed. This document will also identify the internal and external testing participants, testing environments to be utilized, and the timing of the testing, etc. 2.4.5 TRAINING: Proposals shall describe the recommended solution for training staff and students on how to use the proposed system. Include details on the number of training hours provided and type of training (onsite, web and/or remote). 2.4.6 Proposers must describe what training materials will be provided to the University both in the initial stages of adoption and over the long term. 2.4.7 Proposals to include the type of user documentation to be provided with the proposed solution, such as help material, contextual help for user screens, tutorials, and online resources that are available to assist both students/employees and administrators. 2.4.8 Proposers must describe in detail how the ongoing administrator support/training will behandled after the implementation phase and initial training is performed. 2.4.9 MAINTENANCE AND SUPPORT:Proposers must indicate what software maintenance and support options are available. 2.4.10 Proposers must describe how scheduled and unplanned maintenance including downtimes are communicated. 2.4.11 Proposers must describe the process in detail of how major software release upgrades are coordinated and scheduled. 2.4.12 Once software upgrades are released, will your firm be able to share any issues resulting from the latest upgrade on problem solving techniques? How will that information be communicated to the University? 2.4.13 Proposers must indicate the frequency for major software releases. Proposers must provide a schedule of new releases for the past three (3) years. 2.4.14 Proposers must describe their approach to supporting ongoing enhancements of the proposed Solution. 2.4.15 Are there any planned enhancements that the Proposer feels the University should know about while evaluating this proposal? 2.4.16 Are there other support options for the proposed solution that will be beneficial for the University? 2.4.17 The proposal must describe all warranties associated with the system covered maintenance plans. 19 December 202219 December 202219 December 202219 December 202219 December 2022 2.4.18 FINAL DEPLOYMENT PLANNING AND EXECUTION: A Deployment Plan is a narrative outlining the approach for deploying the new LIS in the production environment. It will include the following: a. Building the production environment b. Migrating application configuration to production c. Final data conversion steps d. Detailed transfer matrix outlining the step by step list of tasks for completing the final production application. Proposers shall submit a Deployment Plan that outlines the required steps for the organization to transition to the final production application. The plan will identify all of the prerequisite steps for initiating the transfer to production. The plan will be a tool for preparing users for the final application upgrade. 2.4.19 POST-IMPLEMENTATION MAINTENANCE AND SUPPORT: Proposers must describe the process for customers requesting security review or compliance requirements on a project-by-project basis (in the event that a higher level of security or a BAA is necessary, etc.). 2.4.20 Proposers must describe how they handle the notification of impending cessation of business or that of a tiered provider. Upon the termination, cancellation, expiration or other conclusion of our contract, how is the return and destruction of data handled? Group 2.5: Financial Statements Instructions: 2.5.1 Option A. Proposers who have audited financial statements are to provide the following: Audited financial statements for the two (2) most recent available years. Option B. Proposers who might not have audited financial statements are to provide the following: It is preferred that audited financial statements for the two (2) most recent available years be submitted. However, if not available, provide a copy of firm’s two (2) most recent tax returns or compiled financial statements by an independent CPA. Group 3.1: Pricing Schedule Instructions: 3.1.1 Proposer shall submit a detailed itemized cost proposal to include all aspects of providing the scope of work associated with this Request for Proposal. NOTE: All costs must be identified in your response as the University will not pay for any hidden costs. Please review the attached Financial Proposal requirements. 3.1.2 Please complete the attached cost structure format. Group 4.1: Sustainability Questionnaire Instructions: 4.1.1 Proposer to indicate whether your business is classified as a Small Business or Large business. 4.1.2 Proposer to complete the attached Sustainability Questionnaire - Small Business document. 4.1.3 Proposer to complete the attached Sustainability Questionnaire - Large Business document. Group 5.1: ASU's Terms and Conditions Instructions: 5.1.1 I have read and agree to ASU's Terms and Conditions located at https://www.asu.edu/purchasing/pdf/Stand_TsCs_Provisions.pdf. If "NO", you will be required to submit exceptions with justification and alternate language. Proposals that are contingent upon any changes to these mandatory terms and conditions may be deemed non-responsive and may be rejected. 5.1.2 All exceptions must be submitted with justification and alternate language, and MUST be submitted with the submittal. In no event is a proposer to submit its own standard contract terms and conditions as a response to this Request for Proposal. Group 5.2: Insurance Requirements Instructions: 5.2.1 I have read the attached ASU insurance requirements and all requirements will be met. 5.2.2 All exceptions to insurance must be submitted with justification and alternate language, and MUST be submitted with the proposal. Group 6.1: Proprietary/Confidential Statement Instructions: 19 December 202219 December 202219 December 202219 December 202219 December 2022 6.1.1 Per pre-requisite instructions, If you are submitting any information you consider to be proprietary or confidential, you must create a password protected zip file and upload the document along with a justification in the appropriate area within this RFP. In an email outside of the RFP, send the password directly to belinda.biggs@asu.edu, referencing the RFP number. If the Executive Director of Procurement concurs, this information will not be considered public information. The Executive Director of Procurement is the final authority as to the extent of material, which is considered proprietary or confidential. Pricing information cannot be considered proprietary or confidential. Proprietary or confidential information must be submitted per the Instructions to Proposers, as stated in the Prerequisites section. Any watermarks, footnotes, copyright or reference to proprietary or confidential submitted proposal will be disregarded as boilerplate markings. I have read and understood. 6.1.2 If you have proprietary or confidential information, upload the password protected zip file here and email the Buyer with the password. For each individual document you've included in your zip file, with the exception of Financial Statements properly submitted via the instructions provided (if applicable), you MUST provide a justification explaining for why this is considered proprietary and confidential to your business. Please provide this information via the file attached. If no justification supporting your submitted Proprietary and Confidential information is enclosed, the request will be disregarded. Group 7.1: Instructions: 7.1.1 Attached is Exhibit 1 for your review. 19 December 202219 December 202219 December 202219 December 202219 December 2022 Product Line Items Product Line Items There are no Items added to this event. 19 December 202219 December 202219 December 202219 December 2022 Service Line Items Service Line Items There are no Items added to this event. 19 December 202219 December 202219 December 2022