Data Connectivity Sample Clauses

Data Connectivity. Converge shall not be responsible for any data connectivity. In order to access and make use of the Products, the Customer must ensure: (a) there is full connectivity and internet access through a cellular, fixed-line or Wi-Fi connected device (as applicable and as needed), including, without limitation, for Connected Hardware to accurately send Sensor Data to the Products; and (b) it and each Product User has appropriately configured any hardware in accordance with Converge’s instructions to allow it to access the Products (including, without limitation, the guidelines, specifications, minimum requirements and recommendations provided to the Customer in respect to the use, configuration and installation of the Products.). Converge is in no way responsible for the operation or failure of operation or availability of or access to any mobile or internet services resulting in any Product User being unable to use the Products. For the avoidance of doubt, in the event that Converge Hardware specified in the Customer Order is unable to connect to the Converge Software specified in the Customer Order, unless caused directly by Converge, all Fees payable by the Customer shall remain payable.
Sample 1Sample 2
AutoNDA by SimpleDocs
Data Connectivity. The Service Provider will provide voice and data connectivity between the Service Provider’s delivery centres and network to the Customer. The Service Provider will be responsible for specifying the connectivity solution to enable the services to be provided as set in Schedule 2 (Service Description) and to meet the Service Levels as defined in Schedule 3 (Service Levels and Service Credits). The connectivity specification will make provision for organic growth over time, peak loads and anticipate the use of additional services over the life of the agreement, for example increased use of video services. The Service Provider will deliver the data connectivity between the Service Provider’s delivery centres and Customer Locations through the provision of a primary MPLS based connection and by secondary VPN connection as a backup. The primary and backup links will offer divergence of routing so that in the event of an outage in the primary link, traffic will be automatically directed onto the secondary link. Over this transport path, the data connectivity will be used for Service Provider staff to access the Customer Network from its delivery centres enabling access to the Customer’s Applications, Tools and data using [***] VDI unless otherwise agreed by the Customer in writing. The Service Provider will provide voice services over separate dedicated and resilient network links. These links and associated software will ensure that the quality of the calls enable the provision of the services in Schedule 2 (Service Description) and meet the Service Levels defined in Schedule 3 (Service Levels and Service Credits). The voice system will be fully integrated into the Customer current voice services so that internal callers see the Service Provider services as an internal extension number both when dialling to Service Provider staff and the Service Desk, and when receiving calls from Service Provider staff.
Sample 1
Data Connectivity. As illustrated in the Architecture Diagram, the proposed solution will require a VPN connection from both OC SSA call center locations to the CALNET2 network‐based platform. Connectivity requirements for Agents and Supervisors are as follows: UGenesys Agent Desktop / Genesys Supervisor Desktop • 32 Kbps per Supervisor x 40 supervisors = 1280 Kbps • 8 Kbps per Agent x 200 concurrent agents = 1600 Kbps EU nterprise Reporting Solution (ERS) • 500 Kbps total Total data connectivity required for this solution is estimated to be 3.380 Mbps. Additional bandwidth could be required for Workforce Management; Workforce Management bandwidth requirements will be determined during WFM Operational Discovery Workshop. It is assumed that sufficient bandwidth exists at each call center location to accommodate the connectivity requirements specified above.
Sample 1
Data Connectivity. Client’s Sales Tool application is accessed over the Public Internet.
Sample 1
Data Connectivity. Data connectivity will be through a *** via a Client provided, dedicated *** connection. Client will also provide a *** to serve as a backup. Client will provide all required *** to establish the *** connection between PeopleSupport's data center *** and Client's data center. It is Client's responsibility to ensure that the network connectivity between Client's facility and PeopleSupport's data center is adequate to support the required applications and user level. Client is responsible for *** associated with *** between the Client *** and PeopleSupport's ***. ***CONFIDENTIAL MATERIAL REDACTED AND SEPARATELY FILED WITH THE COMMISSION. -------------------------------------------------------------------------------- This document contains unpublished, confidential and proprietary information of PeopleSupport, Inc. No disclosure, duplication or use of any portion of the contents of these materials, for any purpose, may be made without the prior express written consent of PeopleSupport, Inc. CONFIDENTIAL TREATMENT REQUESTED. CONFIDENTIAL PORTIONS OF THIS DOCUMENT HAVE BEEN REDACTED AND HAVE BEEN SEPARATELY FILED WITH THE COMMISSION. a VeriSign(R) company NETWORKSOLUTIONS(R) PEOPLESUPPORT -------------------------------------------------------------------------------- PeopleSupport and client will both monitor the communication link between the two data centers as well as applications supporting the client program. All email routed to and from PeopleSupport email servers shall be ***.
Sample 1
Data Connectivity. NYCT will provide and NYCT forces will maintain, at NYCT’s cost, all hard-wired and cellular connectivity to the Kiosks and all service levels and performance requirements applicable to Agency Messaging-Only Communications Devices shall apply to the Kiosks.
Sample 1
Data Connectivity. (1) This Agreement does not constitute any obligation of EFAG to accept any TES Message for- warded using the Data Connectivity or the Eurex GUI. (2) TPIP’s use of the Data Connectivity as well as the use of Eurex GUI, is limited to the purpose of fulfilling its obligations under this Agreement and TPIP may not sell, lease, transfer, assign, sublicense or otherwise convey the Data Connectivity or the use of the Eurex GUI to any third party other than to its affiliates in accordance with Section 18 (1) of this Agreement. TPIP shall not be entitled to send any data via the Data Connectivity which does not conform to the Interface Specification and TPIP may not use the Data Connectivity or the Eurex GUI to com- municate with other recipients or IT Systems than the Eurex System. (3) TPIP shall be responsible for keeping any Credential provided to TPIP hereunder confidential and protected against access of unauthorized third parties. TPIP must immediately notify EFAG and request a change of Credential when TPIP has reason to assume that a user ID, password or credential has been compromised. (4) TPIP shall use commercially reasonable efforts to keep any and all computer systems it is responsible for that directly or indirectly interface with the Data Connectivity or the Eurex GUI free from malware, including but not limited to, computer viruses, worms, trojan horses etc. at all times. (5) EFAG shall be entitled to suspend the performance of this Agreement and reject any messages sent to it via the Data Connectivity or the Eurex GUI or refuse their entry into the Eurex System, withdraw the use of the Eurex GUI and to discontinue the provision of any technical access services – if any - provided under other agreements, if and to the extent TPIP does not fulfil its obligations hereunder or if Eurex decides in its sole discretion that such suspension or discon- nect is required for the protection of either EFAG’s, TPIP’s or Participant’s IT security or the protection of the security of the Eurex Exchanges. EFAG shall inform TPIP about any measure taken according to this Paragraph without undue delay as soon as reasonably practical.
Sample 1
AutoNDA by SimpleDocs
Data Connectivity. 6.2.1 [***] The system will be capable of [***] to and [***] with an [***]. This [***] will support [***] of [***] a [***]. Customers will be required to perform some [***] to [***] this [***]. A [***] will be created and maintained that will detail a [***] of [***] and [***].
Sample 1

Related to Data Connectivity

  • Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.

  • Internet Connection Certain Solutions may require an active and stable connection to the Internet in order to function. It is therefore your responsibility to ensure that you have at all times an active and stable Internet connection.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Network PHARMACY is a retail, mail order or specialty pharmacy that has a contract to accept our pharmacy allowance for prescription drugs and diabetic equipment or supplies covered under this plan. NETWORK PROVIDER is a provider that has entered into a contract with us or other Blue Cross and Blue Shield plans. For pediatric dental care services, network provider is a dentist that has entered into a contract with us or participates in the Dental Coast to Coast Network. For pediatric vision hardware services, a network provider is a provider that has entered into a contract with EyeMed, our vision care service manager.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!