Dublin O'Connell House Voice over Internet Provider

18 April 2024 Dublin O'Connell House Voice over Internet Provider Dublin's O'Connell House is looking for a new Voice over Internet Provider. This is an International Location 18 April 2024 Open 3/22/2024 5:00 PM EDT Type Request for Proposal Close 4/23/2024 5:00 PM EDT Number RFP 24-0001 Currency US Dollar 18 April 2024 Contacts Katie Hahaj khahaj@nd.edu 18 April 2024 Commodity Codes None Added 18 April 202418 April 202418 April 202418 April 202418 April 202418 April 202418 April 202418 April 2024 mailto:khahaj@nd.edu Purpose The University of Notre Dame Dublin, hereinafter referred to as the "University" or "Notre Dame," seeks to enter into a contract with a Bidder, hereinafter referred to as the "Bidder," to provide a Unified Communications as a Service (UCaaS) Provider for our Notre Dame International location, specifically O’Connell House, Dublin, Ireland. Scope and Objectives

The current NDI (Notre Dame International) O’Connell House phone system configuration includes one (1) ISDN circuit with an associated block of twenty (20) DID lines. The system provides service to twelve (12) handsets at O’Connell House. All lines are analog handsets. The receptionist handset is a Panasonic KX-T7633; the rest are Panasonic KX- T7630. The original date of contract for this system was circa 2004. O’Connell House has a multiservice access SLA premium internet connection with Eir. The UCaaS provider is expected to be responsible for all equipment installation and PSTN circuit connections, except for end-point handset installation. The purpose of this RFP is to receive a quote to replace the phone systems at NDI Dublin O’Connell House with a single UCaaS system. Contract Term The contract term shall be for an initial period of three (3) years with an option to extend for two (2) additional one-year periods upon written mutual agreement. All prices shall remain firm for the initial three (3) year contract period. The University has identified Dublin, Ireland the place of performance. Attachments Please review all attachments under the "Buyer Attachments" section. RFP Questions & Communications All questions and responses concerning this RFP must be submitted though the University's e-procurement portal. Communication with the evaluation committee or other University employees regarding this RFP is prohibited until awards have been announced. Exceptions to this stipulation must be granted prior to contact by the RFP contact representative. Violation of this provision may result in the immediate rejection of the proposal. RFP Timeline Bidder Questions Due: 03/29/2024 Bidder Response Due: 4/9/2024 Bidder Selection Notice 04/23/2024 Description Required to View Event Prerequisites Required to Enter Bid There are no Prerequisites added to this event. 18 April 202418 April 202418 April 202418 April 202418 April 202418 April 202418 April 2024 Buyer Attachments 1. Dublin O'Connell House VoIP Cover Letter.pdf 2. NDI Dublin O'Connell House RFP.pdf 18 April 202418 April 202418 April 202418 April 202418 April 202418 April 2024 https://bids01.jaggaer.com/apps/Router/PublicEventDownload?file=U291cmNpbmdldmVudC8xMjE4MDg1LTE1ODc5Mzc3ODBORElfRHVibGluX1JGUF9Db3Zlcl9MZXR0ZXIucGRm&auth=MDpBRVMyI0NQNVp4a2IvSnkxZDNIUm81TGpka2h4M0V4bkpBZDlVSkVFUnk5WnZrK2l5eGZjOVRGNkRHUlU9 https://bids01.jaggaer.com/apps/Router/PublicEventDownload?file=U291cmNpbmdldmVudC8xMjE4MDg1LTE1ODc5Mzg3MjJOREkgRHVibGluIE8nQ29ubmVsbCBIb3VzZSBSRlAucGRm&auth=MDpBRVMyI0NQNVp4a2IvSnkxZDNIUm81TGpka2h4M0V4bkpBZDlVSkVFUnk5WnZrK2l5eGZjOVRGNkRHUlU9 Questions Required Questions Group 1: Functional Requirements Instructions: 1.1 Ability to dial local, international, toll free and emergency (emergency dialing must comply with all Ireland 999 calling laws) 1.2 Clarifying Comments for the Previous Question. 1.3 Ability to provide a 1:1 feature parity between hard and soft phones 1.4 Clarifying Comments for the Previous Question. 1.5 Ability to “click to call” from Google Suite contact list 1.6 Clarifying Comments for the Previous Question. 1.7 Integrated voicemail and email with Google Suite 1.8 Clarifying Comments for the Previous Question. 1.9 Ability to support multiple IVR (Interactive Voice Response) menu call trees 1.10 Clarifying Comments for the Previous Question. 1.11 Ability to provide TOD (time of day) call routing for menu call trees 1.12 Clarifying Comments for the Previous Question. 1.13 Ability to mask outbound caller ID to show NDI Dublin main number on a phone by phone basis 1.14 Clarifying Comments for the Previous Question. 1.15 Ability to have outbound time of day outbound calling rights 1.16 Clarifying Comments for the Previous Question. 1.17 Ability to have multiple line presence on administrative assistant phones 1.18 Clarifying Comments for the Previous Question. 1.19 Ability to monitor multiple voicemail boxes from administrative assistant phones 1.20 Clarifying Comments for the Previous Question. 1.21 Ability to manage all facets of the phone system remotely via web browser 1.22 Clarifying Comments for the Previous Question. 1.23 Provide a list of countries you can expand your UCaaS offering to 1.24 Provide cost per minute (if applicable) for calling United States based phone numbers 1.25 Does your system meet General Data Protection Regulation (GDPR) compliance standards? 1.26 Clarifying Comments for the Previous Question. 1.27 Confirm the proposed system is compatible with Polycom VVX250 handsets 1.28 Clarifying Comments for the Previous Question. Group 2: Architecture Instructions: 2.1 Cloud (SaaS) solution has feature parity with your other service offerings? (Answer yes if you only offer a SaaS solution.) 2.2 Clarifying Comments for the Previous Question. 2.3 Proposed solution runs / can run on Amazon Web Services (AWS). (Describe any barriers in Comments area provided below) 2.4 Clarifying Comments for the Previous Question. 2.5 Software can be scaled horizontally (load-balancing or auto-scaling) 2.6 Clarifying Comments for the Previous Question. 2.7 Does your solution have a fully featured web interface (with all the features of your thick client, if one exists)? 2.8 Clarifying Comments for the Previous Question. 2.9 Supplier does not impose performance or throughput throttles on their system that impact either the end user experience or programmatic access to the service (upstream contraints?). Elaborate in the Comments section as necessary. 2.10 Clarifying Comments for the Previous Question. 2.11 Supplier provides development and test environments as part of customer development cycles (elaborate in comments) 18 April 202418 April 202418 April 202418 April 202418 April 2024 2.12 Clarifying Comments for the Previous Question. 2.13 Solution provides an API for data and business process integrations 2.14 Clarifying Comments for the Previous Question. Group 3: Compliance Instructions: 3.1 Is your service compliant with NIST SP 800-122 and thus approved for FERPA data? 3.2 Clarifying Comments for the Previous Question. 3.3 Is your service compliant with NIST SP 800-171 and thus approved for CUI (Controlled Unclassified Information)? 3.4 Clarifying Comments for the Previous Question. 3.5 Service provider explicitly recognizes their potential obligations under FERPA. 3.6 Clarifying Comments for the Previous Question. 3.7 Supplier will sign a BAA? 3.8 Clarifying Comments for the Previous Question. 3.9 Supplier's privacy policy satisfies EU DPD, DoC EU or Swiss Safe Harbor, or Indian requirements? (eleborate in the Comments section) 3.10 Clarifying Comments for the Previous Question. 18 April 202418 April 202418 April 202418 April 202418 April 2024 Product Line Items Product Line Items There are no Items added to this event. 18 April 202418 April 202418 April 202418 April 2024 Service Line Items Service Line Items There are no Items added to this event. 18 April 202418 April 202418 April 2024