Development of Web Application for the MSU Veterinary Diagnostics Laboratory (VDL) NDA| MSA

Page 1 of 17 RFP # 737797 for Vet Lab REQUEST FOR PROPOSAL RFP #737797 DEVELOPMENT OF WEB APPLICATION FOR THE MSU VETERINARY DIAGNOSTIC LABORATORY (VDL) RFP Timeline RFP Issue Date May 19th , 2023 Deadline for Respondent Questions to MSU May 30th, 2023 MSU deadline for providing response June 7th, 2023 Written RFP Response Due Date June 15th, 2023, 4:00 pm Eastern Estimated notification of shortlisted Suppliers June 26th, 2023 Detail Evaluation & selection of Supplier June 26th to July 7th, 2023 Contract Negotiations & other technical discussions July 10th to July 21st, 2023 Estimated Contract Award July 31st, 2023 RFP Contact Name: Jainaba Faal Email: faaljain@msu.edu Phone: (517) 884-6173 DESCRIPTION: Michigan State University (the “University” or “MSU”) is soliciting proposals through this Request for Proposal (“RFP”) for a Supplier to develop a Web Application for the MSU Veterinary Laboratory. The application will provide

functionality for ordering diagnostic tests that needs to be processed in the laboratory. The detail Application Functionality is thoroughly described under the “Scope of work & Requirement “Section of this RFP. Firms/Companies intending to respond to this RFP are referred to herein as a “Respondent” or “Supplier.” Page 2 of 17 RFP # 737797 for Vet Lab PROPOSAL INSTRUCTIONS 1. PROPOSAL PREPARATION. The University recommends reading all RFP materials prior to preparing a proposal, particularly these Proposal Instructions. Respondents must follow these Proposal Instructions and provide a complete response to the items indicated in the table below. References and links to websites or external sources may not be used in lieu of providing the information requested in the RFP within the proposal. Include the Respondent’s company name in the header of all documents submitted with your proposal. Document Description Response Instructions Cover Page Provides RFP title and number, important dates, and contact information for MSU Informational Proposal Instructions Provides RFP instructions to Respondents Informational Respondent Information Sheet Company and Contact Information, and Experience Respondent must complete and submit by proposal deadline Scope of Work & Systems functional and Technical Requirements Describes the intended scope of work for the RFP Respondent must complete and submit by proposal deadline Pricing Pricing for goods and services sought by the University through this RFP Respondent must complete and submit by proposal deadline Master Service Agreement Provides legal terms for a contract awarded through this RFP Deemed accepted by Respondent unless information required in Section 8, Master Service Agreement is submitted by proposal deadline MSU Non-Disclosure Agreement (NDA Required when sensitive information will be given to Suppliers. All suppliers that intend to submit a Proposal must sign and submit it before additional information is provided 2. EXPECTED RFP TIMELINE. RFP Timeline RFP Issue Date May 19th , 2023 Deadline for Respondent Questions to MSU May 30th, 2023 MSU deadline for providing response June 7th, 2023 Written RFP Response Due Date June 15th, 2023, 4:00 pm Eastern Estimated notification of shortlisted Suppliers June 26th, 2023 Detail Evaluation & selection of Supplier June 26th to July 7th, 2023 Contract Negotiations & other technical discussions July 10th to July 21st, 2023 Page 3 of 17 RFP # 737797 for Vet Lab Estimated Contract Award July 31st, 2023 3. CONTACT INFORMATION FOR THE UNIVERSITY. The sole point of contact for the University concerning this RFP is listed on the Cover Page. Contacting any other University personnel, agent, consultant, or representative about this RFP may result in Respondent disqualification. 4. QUESTIONS. Respondent questions about this RFP must be submitted electronically by email to the contact listed on the cover page of this RFP. In the interest of transparency, only written questions are accepted. Answers to all questions will be sent to Respondents via email. Submit questions by referencing the following: (i) Question Number, (ii) Document Name, (iii) Page Number, and (iv) Respondent Question. Please refer to Section 2 above for the deadline to submit questions. 5. MODIFICATIONS. The University may modify this RFP at any time. Modifications will be sent via email. This is the only method by which the RFP may be modified. 6. DELIVERY OF PROPOSAL. The Respondent must submit its proposal, all attachments, and any modifications or withdrawals electronically via email to the contact listed on the cover page of this RFP. The price proposal should be saved separately from all other proposal documents. The Respondent should submit all documents in a modifiable (native) format (examples include, but are not limited to: Microsoft Word or Excel and Google Docs or Sheets). In addition to submitting documents in a modifiable format, the Respondent may also submit copies of documents in PDF. Respondent’s failure to submit a proposal as required may result in disqualification. The proposal and attachments must be fully uploaded and submitted prior to the proposal deadline. Do not wait until the last minute to submit a proposal. The University may not allow a proposal to be submitted after the proposal deadline identified in the Cover Page, even if a portion of the proposal was already submitted. 7. EVALUATION PROCESS. The University will convene a team of individuals from various Departments within MSU to evaluate each proposal based on each Respondent’s ability to provide the required services, taking into consideration the overall cost to the University. The University may require an oral presentation of the Respondent's proposal; conduct interviews, research, reference checks, and background checks; and request additional price concessions at any point during the evaluation process. The following criteria will be used to evaluate each proposal: Criteria University’s evaluation of the proposed Application’s ability to meet outlined technical and functional requirements Supplier`s prior experience and Qualification as it relates to this RFP Overall Cost to the University. All Suppliers are required to use the Pricing template provided in the RFP. Failure to comply may result in rejection of proposal. Page 4 of 17 RFP # 737797 for Vet Lab Acceptance of proposed Master Service Agreement (MSA) 8. MASTER SERVICE AGREEMENT. The University strongly encourages strict adherence to the terms and conditions set forth in the Master Service Agreement. The University reserves the right to deem a proposal non-responsive for failure to accept the Master Service Agreement. Nevertheless, the Respondent may submit proposed changes to the Master Service Agreement in track changes (i.e., visible edits) with an explanation of the Respondent’s need for each proposed change. Failure to include track changes with an explanation of the Respondent’s need for the proposed change constitutes the Respondent’s acceptance of the Master Service Agreement. General statements, such as “the Respondent reserves the right to negotiate the terms and conditions,” may be considered non-responsive. 9. CLARIFICATION REQUEST. The University reserves the right to issue a Clarification Request to a Respondent to clarify its proposal if the University determines the proposal is not clear. Failure to respond to a Clarification Request timely may be cause for disqualification. 10. RESERVATIONS. The University reserves the right to: a. Disqualify a Respondent for failure to follow these instructions. b. Discontinue the RFP process at any time for any or no reason. The issuance of an RFP, your preparation and submission of a proposal, and the University’s subsequent receipt and evaluation of your proposal does not commit the University to award a contract to you or anyone, even if all the requirements in the RFP are met. c. Consider late proposals if: (i) no other proposals are received; (ii) no complete proposals are received; (iii) the University received complete proposals, but the proposals did not meet mandatory minimum requirements or technical criteria; or (iv) the award process fails to result in an award. d. Consider an otherwise disqualified proposal, if no other proposals are received. e. Disqualify a proposal based on: (i) information provided by the Respondent in response to this RFP; or (ii) if it is determined that a Respondent purposely or willfully submitted false or misleading information in response to the RFP. f. Consider prior performance with the University in making its award decision. g. Consider total-cost-of-ownership factors (e.g., transition and training costs) when evaluating proposal pricing and in the final award. h. Refuse to award a contract to any Respondent that has outstanding debt with the University or has a legal dispute with the University. i. Require all Respondents to participate in a Best and Final Offer round of the RFP. j. Enter into negotiations with one or more Respondents on price, terms, technical requirements, or other deliverables. k. Award multiple, optional-use contracts, or award by type of service or good. l. Evaluate the proposal outside the scope identified in Section 7, Evaluation Process, if the University receives only one proposal. 11. AWARD RECOMMENDATION. The contract will be awarded to the responsive and responsible Respondent who offers the best value to the University, as determined by the University. Best value will be determined by the Respondent meeting the minimum requirements and offering the best combination of the factors in Section 7, Evaluation Process, and price, as demonstrated by the proposal. The University will email a Notice of Award to all Respondents. A Notice of Award Page 5 of 17 RFP # 737797 for Vet Lab does not constitute a contract, as the parties must reach final agreement on a signed contract before any services can be provided. 12. GENERAL CONDITIONS. The University will not be liable for any costs, expenses, or damages incurred by a Respondent participating in this solicitation. The Respondent agrees that its proposal will be considered an offer to do business with the University in accordance with its proposal, including the Master Service Agreement, and that its proposal will be irrevocable and binding for a period of 180 calendar days from date of submission. If a contract is awarded to the Respondent, the University may, at its option, incorporate any part of the Respondent’s proposal into the contract. This RFP is not an offer to enter into a contract. This RFP may not provide a complete statement of the University’s needs, or contain all matters upon which agreement must be reached. Proposals submitted via email are the University’s property. 13. FREEDOM OF INFORMATION ACT. Respondent acknowledges that any responses, materials, correspondence or documents provided to the University may be subject to the State of Michigan Freedom of Information Act (“FOIA”), Michigan Compiled Law 15.231 et seq., and may be released to third parties in compliance with FOIA or any other law. 14. ADDITIONAL DATA REQUIRED FOR SUBMISSION: There is additional data/information (data relationship diagrams) that you will need to understand the scope of the work. The data relationship diagrams depict how to access and retrieve all records from the Millennium database. The information provided by these diagrams will enable Supplier to study and understand the database schema, taxonomy, relationships between the tables and the views. The data is sensitive, and you are required to sign the MSU Non-Disclosure Agreement (NDA) before the information is provided. The winning Supplier will also be required to sign an additional Non- Disclosure Agreement (NDA) called Confidentiality Statement for Outside Personnel before given access to other sensitive data after contract award. Page 6 of 17 RFP # 737797 for Vet Lab RESPONDENT INFORMATION SHEET Please complete the following Information Sheet in the space provided: Information Sought Response Contact Information Respondent’s sole contact person during the RFP process. Include name, title, address, email, and phone number. Person authorized to receive and sign a resulting contract. Include name, title, address, email, and phone number. Respondent Background Information Legal business name and address. Include business entity designation, e.g., sole proprietor, Inc., LLC, or LLP. What state was the company formed in? Main phone number Website address DUNS# AND/OR CCR# (if applicable): Number of years in business and number of employees Legal business name and address of parent company, if any Has your company (or any affiliates) been a party to litigation against Michigan State University? If the answer is yes, then state the date of initial filing, case name and court number, and jurisdiction. EXPERIENCE: Please note that MSU may verify the information provided below. Describe relevant experiences from the last 5 years supporting your ability to successfully manage a contract of similar size and scope for the services described in this RFP. Experience 1 Company name Contact name Contact role at time of project Contact phone Contact email 1. Project name and description of the scope of the project 2. What role did your company play? 3. How is this project experience relevant to the subject of this RFP? Page 7 of 17 RFP # 737797 for Vet Lab Start and end date (mm/yy – mm/yy) Status (completed, live, other – specify phase) Experience 2 Company name Contact name Contact role at time of project Contact phone Contact email 1. Project name and description of the scope of the project 2. What role did your company play? 3. How is this project experience relevant to the subject of this RFP? Start and end date (mm/yy – mm/yy) Status (completed, live, other – specify phase) Experience 3 Company name Contact name Contact role at time of project Contact phone Contact email 1. Project name and description of the scope of the project 2. What role did your company play? 3. How is this project experience relevant to the subject of this RFP? Start and end date (mm/yy – mm/yy) Status (completed, live, other – specify phase) Page 8 of 17 RFP # 737797 for Vet Lab SCOPE OF WORK & SYSTEMS FUNCTIONAL & TECHNICAL REQUIREMENTS 1. Background. The Michigan State University Veterinary Diagnostic Laboratory is a full-service veterinary laboratory with a test catalog of over 800 offerings. In a given physical year, we have over 10,000 active clients across the United States and around the world. Each month we receive over 19,000 submissions which are shipped by USPS, UPS and Fed Ex arriving daily Monday – Saturday. Currently our clients utilize a paper submission form, available from our website in a fillable format. They complete the submission form, selecting the tests they wish to have run. This form is included with their biologic samples, which are appropriately packaged and shipped to the laboratory. Once received, these packages are opened, triaged and manually entered into our laboratory information management system. This process is labor intensive and is currently supported by 16 employees. An online portal with dynamic forms supporting an online shopping experience would allow us to interface orders directly with our laboratory information system and provide a linked submission form with required information to properly process the submission. This would streamline the receiving process reducing manual data entry and the related errors which are inherit in that process. Other benefits include reduced labor needs, faster turnaround time for diagnostic testing and a streamlined submission process for our clients. This project will support the continued growth being experienced by the laboratory while making great improvements to our sample receiving process. 2. Statistics Relevant for the assignment Currently the MSU Veterinary Diagnostic Laboratory processes 275,000 encounters yearly (16,500 - 23,000 per month). An encounter represents the smallest quantifiable unit in a transaction, but there exists a one-to-many relationship between an encounter and a diagnostic test. The veterinary medical center represents 13-14% of encounters created. The Veterinary Medical Center is the teaching hospital and should be considered an internal client of the MSU Veterinary Diagnostic Laboratory. It has 9,000 active clients in the given calendar year. Clients are representatives of a veterinary clinic or another industry or governmental partner. There exists a one-to-many relationship between clients and users. 3. Scope of Work The selected Supplier will be responsible for building, hosting, and supporting a web application that provides functionality for ordering diagnostic tests to be processed at the MSU Veterinary Diagnostic Laboratory. The web application must meet accessibility, security, functional, brand, and technical requirements of Michigan State University and the College of Veterinary Medicine – Veterinary Diagnostic Laboratory. It is estimated that the system must support a minimum of 600-800 concurrent users. Peak usage of the system would occur during the months of March - June. Page 9 of 17 RFP # 737797 for Vet Lab 3.1. Accessibility Requirements Web Accessibility Guidelines 3.2. Security Requirements • The web application must be routinely scanned for security vulnerabilities. Security vulnerabilities must be patched. • Users must authenticate to access ordering services. • Users must be authorized to order any diagnostic test. • The web application must be accessible over an encrypted protocol (HTTPS). • Ingress network traffic to MSU’s networks and systems must come from a known source, IP address, IP range, and hostname. • The web application and all associated data must be hosted domestically. • All parties with access to production data must engage in a non-disclosure agreement with the MSU Veterinary Diagnostic Laboratory. 3.3. Functional Requirements • User must log into their account to gain access to ordering • User must select a desired test from catalog • The appropriate data form would be presented based on test selected (Multiple data forms would be required to accommodate the test catalog) • Data form would have required fields and drop-down menus to maintain data integrity • Data form would be utilized to capture clinic, owner, and animal demographics • Multiple tests could be added to the shopping cart prior to submission • After an order is placed the user must be presented with a printable submission form to include with their order • Based on the tests ordered user must be presented with shipping requirements 3.4. Brand Requirements MSU Web Standards 3.5. Technical Requirements • Users will be both internal and external. Internal users (MSU users) must use MSU’s SSO service (Okta). External users authentication credentials will be maintained by the vendor preferred platform. • The web application must have a 99.95% uptime • The web application must use a responsive design • The web application is responsible for building HL7 messages for ordering diagnostic tests • The web application is responsible for collecting data through dynamic forms and conditional on the diagnostic test ordered https://webaccess.msu.edu/Policy_and_Guidelines/index.html https://comms.msu.edu/resources/msu-web-standards Page 10 of 17 RFP # 737797 for Vet Lab • The web application must correlate data received by the interface engine with data in the Millennium database (Oracle 19c). • The web application must connect to remote file system to retrieve flat files 4. Qualification and Experience of the Supplier Evaluation of a Supplier`s qualifications and experienced will be based on the criteria outlined below in addition to the response provided in the “Respondent Information Sheet”. You are required to provide detailed information to enable the MSU Team to evaluate. 1. Outline the technologies used in your company and demonstrate the experience your Team have with those technologies. 2. Describe your software design and development process. 3. Provide evidence of working with healthcare Technology 4. List and provide detailed qualification and experience of the Engineers that will be working on this assignment. Clearly outline the number of years they have in writing softwares. 5. Do you have any familiarity with Health Level Seven (https://www.hl7.org/) 6. Explain your experience writing any type of application programming interface. 1. Outline your experience with common data relationships, taxonomy, and constraints of healthcare systems (Electronic Medical Records (EMR), Practice Management System (PMS) , Laboratory Information Management System (LIMS) 2. Outline your experience with security practices and controls when working with healthcare data? 7. What is your experience integrating software with client hosted solutions 8. What is your experience working with Oracle Database Engine 5. Assignment Duration The assignment is expected to commence in August 2023. Contract with the winning Supplier will be signed as follows: • Development Phase: for a period of eighteen (18) months • Maintenance and Support: for an initial period of Five (5) years with possible renewal options with the agreement of both parties. 6. Pricing Provide pricing for the development phase and an annual maintenance and Support pricing for five (5) year’s period including information on any discounts for implementing multi-year support contracts. Therefore, MSU expects you to submit a five (5) year locked Pricing for the maintenance period. Options available are outlined in the pricing section of the RFP. 7. General Requirements 7.1. The selected supplier for this RFP may be subject to the University’s Criminal Background Check Policy, available at: https://upl.msu.edu/common/documents/criminal-back-ground-check.pdf 7.1.1. If the University, at its sole discretion, determines the selected supplier is subject to this Policy, the supplier must sign and deliver the Contractor Certification for Criminal https://www.hl7.org/ Page 11 of 17 RFP # 737797 for Vet Lab Background Checks to University prior to the provision of any services or delivery of any goods 8. Technology Requirements 8.1. Support for Windows 10/Mac OS, iOS, Android 8.2. Hosting, Availability, and Performance Requirements 8.2.1. Describe the hosting options for your solution (e.g., software-as-a-service, private cloud, local on premises, single/multi-tenant). 8.2.2. Describe the hosting requirements and options for the solution. 8.2.3. Identify all third-party software that is required in order to have a fully functional solution. 8.2.4. Provide historical statistics on the availability and performance of the platform that will host the solution and services. 8.2.5. Describe how availability and performance of the platform that will host the solution is monitored and disruptions to services communicated proactively. 8.2.6. Describe how performance testing can be conducted on the solution. 8.2.7. Describe the environments provided and supported for the solution (e.g., DEV, TEST, QA, PROD). 8.3. Intended User Experience Requirements 8.3.1. Describe the browser support policy for the solution. 8.3.2. Describe the mobile capabilities and supported devices for the solution. 8.3.3. Describe how the solution ensures continual compliance with the Americans with Disabilities Act (ADA), and Section 508 of the Rehabilitation Act. 8.3.4. Describe how the solution will meet the MSU web accessibility policy (http://webaccess.msu.edu/Policy_and_Guidelines/web-accessibility-policy.html). 8.3.5. Describe how the solution will maintain the MSU brand standards (http://www.brand.msu.edu/). 8.3.6. Describe the authentication and single sign-on integration options for the solution. 8.3.7. Describe the authorization integration options for the solution. 8.3.8. Describe how the solution establishes and configures roles. Identify pre-defined role definitions and configurable role capabilities. 8.4. Integration Requirements 8.4.1. Identify the integration tools and technologies available to integrate with MSU applications and databases. 8.4.2. The proposed solution should have a capability of integrating with the University`s databases containing student and employee information such as: 8.4.2.1. MSU SSO – for MSU students and employees ease of access. 8.4.2.2. SSO for Guest and/or affiliate access. 8.5. Intended Data Management Requirements 8.5.1. Provide a data dictionary for the solution. 8.5.2. Describe how key business entities are managed to ensure an authoritative system of record. 8.5.3. Describe how the solution minimizes duplication of transactional data. 8.5.4. Describe how the solution decouples data from other ties of the application. 8.5.5. Describe the information lifecycle of data in the solution from creation to rendering to archival processes. 8.5.6. Describe the migration capabilities of data between environments facilitated by your product. Page 12 of 17 RFP # 737797 for Vet Lab 8.6. Security Requirements 8.6.1. Suppliers are required to submit a HECVAT (Higher Education Community Vendor Assessment Tool) as part of their proposal for MSU’s review 8.6.1.1. HECVAT Form can be found at: https://www.ren-isac.net/hecvat/index.html 8.6.2. The HECVAT is the standard security document used by MSU IT Security. If a respondent is unable to submit a HECVAT, they shall required to submit other documentation of their security policies and process for evaluation by MSU. 8.6.3. Describe how the solution adheres to the MSU Institutional Data Policy (https://tech.msu.edu/about/guidelines-policies/msu-institutional-data-policy/) 8.6.4. Provide all requested information identified as part of the Service Provider Security Assessment process. 8.6.5. Describe data security controls and include data breach protection and detection. 8.6.6. Describe data transfer mechanisms and include data breach protection and detection. 8.6.7. Describe all physical location(s) of the data. 8.6.8. Describe your data use policy. 8.6.9. Identify any data storage limits. 8.6.10. Describe the process for MSU to be provided with all data at the conclusion of service. 8.6.11. Describe the data removal process upon conclusion of service. 8.7. Accessibility Requirements 8.7.1. The University is required to comply with the Americans with Disabilities Act of 1990 (ADA), and has adopted a formal policy regarding accessibility requirements for websites and software applications. Supplier’s software must comply, where relevant, with level AA of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. 8.7.2. Suppliers are required to submit a VPAT as part of their proposal for MSU’s review. 8.7.2.1. Additionally, suppliers are free to submit any 3rd Party Accessibility Evaluations completed on their product for University’s consideration 8.7.3. As part of MSU’s review of product accessibility, MSU may request access to a test or sample environment. 8.8. Implementation, Testing, and Training Requirements for the intended solution 8.8.1. Describe the implementation process including data and configuration requirements, data conversion, implementation, and testing. 8.8.2. As part of your implementation approach, tell us what your responsibilities are, and what MSU’s responsibilities are. 8.8.3. Provide a sample high-level project plan indicating key milestones and expected implementation timeline. 8.8.4. Identify the roles and responsibilities of the implementation team, clearly indicating roles provided versus roles expected by MSU. 8.8.5. The selected supplier will be responsible for defining the testing approach to be performed prior to the launch of the proposed solution. 8.8.6. The testing approach should include Unit Testing, System/Integration Testing, Performance Testing and User Acceptance Testing phases, with formal signoff at the conclusion of each phase. 8.8.7. Describe the training method and materials provided as part of the implementation of the solution. https://www.ren-isac.net/hecvat/index.html https://tech.msu.edu/about/guidelines-policies/msu-institutional-data-policy/ Page 13 of 17 RFP # 737797 for Vet Lab 8.8.8. Describe what kinds of technical and end user documentation are provided for the proposed solution. 8.9. Hosting, Availability, and Performance Requirements 8.9.1. Describe the hosting options for your solution (e.g., software-as-a-service, private cloud, local on premises, single/multi-tenant). 8.9.2. Describe the hosting requirements and options for the solution. 8.9.3. Identify all third party software that is required in order to have a fully functional solution. 8.9.4. Describe how availability and performance is monitored and disruptions to services communicated proactively. 8.9.5. Describe how performance testing can be conducted on the solution. 8.9.6. Describe the environments provided and supported for the solution (e.g., DEV, TEST, QA, PROD). 8.10. Maintenance and Support Services Requirements 8.10.1. Supplier shall provide ongoing technical support of the system for the duration of the agreement. 8.10.2. Provide the service level agreement for your support services, including services levels and maximum response time for service from receipt of report of need to initial response to customer. Identify how requests for service are made, logged, tracked, and escalated by your company. 8.10.3. Provide the name, address, telephone number, fax number and email address for your support services. 8.10.4. Provide the standard hours of operation for your support services. If standard hours are not 24 x 7, what support do you provide for “off hours”? 8.10.5. Describe how your company addresses “bug” fixes, updates, and upgrades. As part of your response, indicate the frequency with which you release upgrades or version releases and delivery methods and processes for each. 8.10.6. Identify the length of time your company continues to provide support and services for the solution after a new version of the solution has been released. 8.10.7. Describe the guaranteed response time for updates related to changing regulations and mandatory policies. 8.10.8. Describe the disaster recovery policies and practices in place that ensure protection against institutional data loss. Technical support shall be available (24 hours per day, 7 days per week) 8.10.9. System uptime is required to be no less than 99.95%. (This is part of the Service Level Agreement). 9. Travel (if applicable) 9.1. All travel and costs must be preapproved by the University. 9.2. All travel shall be reimbursed at actual cost and shall be subject to MSU’s Travel Reimbursement Policy set forth at Michigan State University Office of the Controller (msu.edu) 10. Required Documents for RFP Submission 10.1. Written response to proposed Solution 10.2. Respondent Information Sheet 10.3. Signed Pricing Proposal valid for 180days and confirming acceptance of payment terms. 10.4. Implementation and Training Plan http://ctlr.msu.edu/COtravel/TravelReimbursement.aspx http://ctlr.msu.edu/COtravel/TravelReimbursement.aspx Page 14 of 17 RFP # 737797 for Vet Lab 10.5. HECVAT, Full Version 10.6. VPAT, preferred 10.6.1. Other 3rd Party Accessibility Evaluation, optional 10.7. Master Service Agreement (if requesting redlines) 11. Payment Schedule Development Phase: Payment will be based on achievement of key deliverables/milestones of this phase. These milestones will be agreed based on your proposed workplan and percentage payments will be agreed upon during the contract negotiations. Maintenance and Support Phase: payments will be made annually in advance and the first year begins after acceptance of the developed solution. 12. Payment Terms 12.1. Invoice payment terms shall be 2.75% 10, NET 30 from date of receipt of invoice. 12.1.1. Respondents are expected to confirm acceptance of the above payment terms. Confirmation needs to be stated on the pricing schedule page of your proposal. Failure to accept these payment terms may result in a respondent being deemed non-responsive. 13. Invoicing 13.1. Invoice Billings 13.1.1. Each invoice is to be billed on a separate sheet of paper 13.1.2. Each invoice must be billed within 30 days after the completion of the stated work 13.1.3. All invoices are to be emailed or mailed to MSU Accounts Payable. Do not mail or email invoices to Administration Building or MSU Client, they will not be paid and will delay receipt of payment 13.1.4. If invoicing for reimbursement of travel expenses, receipts for actual travel costs shall be provided as supporting documentation along with the invoice 13.1.5. More information on MSU invoice submission requirements can be found at: https://upl.msu.edu/finance-analytics/accounts-payable/submitting-invoices/index.html 13.2. Invoice Requirements 13.2.1. Every invoice must show 13.2.1.1. Company Name 13.2.1.2. University Purchase Order Number 13.2.1.3. Itemized/Breakdown of costs being invoiced https://upl.msu.edu/finance-analytics/accounts-payable/submitting-invoices/index.html Page 15 of 17 RFP # 737797 for Vet Lab PRICING In order to more accurately compare proposals, bidders shall return a pricing proposal per the below. Failure to return a signed version of this form may result in a bidder being disqualified. In addition to this form, bidders are free to also include other pricing information they feel would be of interest to the University (i.e. options, pricing breakdown, etc.). Bidders may indicate a dollar value for each cost (including $0 / no charge) or that cost is “included” in other costs. Development Phase (One Time Costs) Main Steps Estimated hours Hourly Rate Structure and design Development Project Oversight & Quality Assurance Launch Other proposed implementation costs, must be detailed in proposal One Time Cost Sub-total: Annual Maintenance and Support Cost Item Proposed Cost Annual Costs Annual Software Licensing (after completion and user acceptance of the development phase) [Other proposed annual costs, must be detailed in proposal] Annual Cost Sub-total for year 1: Annual Cost Sub-total for year 2: Annual Cost Sub-total for year 3: Annual Cost Sub-total for year 4: Annual Cost Sub-total for year 5: The signature below confirms that this proposal is valid for 180 days after the due date. Supplier Signature: Name: Title: Date: Page 16 of 17 RFP # 737797 for Vet Lab MASTER SERVICE AGREEMENT (attached) Please refer to Section 8 of the RFP Instructions when reviewing the Master Services Agreement terms and conditions. Page 17 of 17 RFP # 737797 for Vet Lab MSU STANDARD NON-DISCLOSURE AGREEMENT (NDA) (attached) This NDA must be signed to get the additional information required to submit your proposal. When the fully executed Non- Disclosure Agreement (NDA) is received, the information will be sent. Upon selection of a Supplier for this RFP, MSU will require signature of another Non- Disclosure Agreement NDA (Confidentiality Statement for outside personnel) before commencement of the assignment.