Client Systems Sample Clauses

POPULAR SAMPLE Copied 1 times
Client Systems. Except as otherwise expressly provided in an Order Form, Client shall be responsible for procuring, installing and maintaining the hardware and software needed to use the Hardware, Software or Services purchased from Meridian.
Client Systems. Client agrees to provide and maintain at its sole expense all Client Systems and is responsible for upgrading and configuring Client Systems to be and remain compatible with the Services and Avid Technology. Client is also responsible for confirming that all payment authorization rights are correctly configured and updated as needed.
Client Systems. Clients can integrate the Hosted Services with their website or smartphone applications.
Client Systems. Client shall ensure that Client Systems: (i) are capable of passing and/or accepting data from and/or to the Fiserv System, and (ii) include up-to-date anti-viral software designed to prevent viruses from reaching the Fiserv System through Client Systems.
Client Systems. Client acknowledges and agrees that Client and its Authorized Users are solely responsible for the physical, logical, and technical security, back-up, archival, and recovery procedures, and safeguards for the servers, software, connectivity, and equipment operated, maintained, or provided by Client or its Authorized Users and associated data contained therein.
Client Systems. You represent and warrant that you have all necessary rights or approvals for us to be able to use or access Client Systems and any other systems in your control.
Client Systems. Client shall be solely responsible for procuring and maintaining the necessary hardware and software for accessing and utilizing the Services.
Client Systems. Client is responsible for the procurement and management of any and all telecommunication lines, internet connection or other facilities, software, hardware, mobile devices or equipment required for the use of the Software Services (“Client Systems”). Client shall at its own expense acquire, install and maintain Client Systems in accordance with the recommended technical requirements for the Software Services as more fully described in Poka’s Acceptable Use & IT Requirements Policy.
Client Systems. Client shall take reasonable steps designed to ensure that Client Systems: (i) are capable of passing and/or accepting data from and/or to the Fiserv System (subject to Fiserv having provided complete and accurate specifications required in connection with such data transferred), and (ii) include up-to-date anti-viral software reasonably designed to prevent viruses from transmitting from or through Client Systems.

Related to Client Systems

  • Customer Services Customer Relationship Management (CRM): All aspects of the CRM process, including planning, scheduling, and control activities involved with service delivery. The service components facilitate agencies’ requirements for managing and coordinating customer interactions across multiple communication channels and business lines. Customer Preferences: Customizing customer preferences relative to interface requirements and information delivery mechanisms (e.g., personalization, subscriptions, alerts and notifications).

  • Information Systems The Customer is aware that vehicles manufactured, supplied or marketed by a company within the Volvo Group are equipped with one or more systems which may gather and store information about the vehicle (the “Information Systems”), including but not limited to information relating to vehicle condition and performance and information relating to the operation of the vehicle (together, the “Vehicle Data”). The Customer agrees not to interfere with the operation of the Information System in any way.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment. 5.2 If a Reconex Customer is served by resold Verizon Telecommunications Service or a Verizon Local Switching UNE, subject to any call blocking feature used by Reconex, to the extent reasonably feasible, Verizon will route Voice Information Services Traffic originating from such Service or UNE to the Voice Information Service platform. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.3 Reconex shall have the option to route Voice Information Services Traffic that originates on its own network to the appropriate Voice Information Services platform(s) connected to Verizon’s network. In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow Reconex to route Voice Information Services Traffic originated on its network to Verizon. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.4 Reconex shall pay Verizon such charges in full regardless of whether or not it collects charges for such calls from its own Customers. 5.5 For variable rated Voice Information Services Traffic (e.g., NXX 550, 540, 976, 970, 940, as applicable) from Reconex Customers served by resold Verizon Telecommunications Services or a Verizon Local Switching Network Element, Reconex shall either (a) pay to Verizon without discount the Voice Information Services provider charges, or (b) enter into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from Reconex’s Customers. 5.6 Either Party may request the other Party provide the requesting Party with non discriminatory access to the other party's information services platform, where such platform exists. If either Party makes such a request, the Parties shall enter into a mutually acceptable written agreement for such access. 5.7 In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Information Service serving switch. This trunk group will be utilized to allow Reconex to route information services traffic originated on its network to Verizon.