Customer’s Obligation to avert and reduce Damages. Service Provider will create daily backup copies of the whole system on which Customer Data is stored to enable restoration of these system data in case of data loss. However, Service Provider does not restore Customer Data of individual Customers e.g. in case of accidental data loss caused by Customer. Customer shall therefore be obliged to take adequate measures to avert and reduce damages due to data loss.
Customer’s Obligation. Customer shall indemnify, defend, and hold harmless MobiChord, its officers, directors and employees against any Claim alleging that Customer Data infringes any patent, copyright or trademark, misappropriates any third party trade secret, or violates any third party privacy rights.
Customer’s Obligation. 5.1. The Customer shall provide the Company with:
5.1.1. The necessary co-operation in all matters relating to this Agreement; 5.
Customer’s Obligation. 6.1. Unless otherwise stated in the quotation, the Client shall supply all necessary data and information to enable the Company to prepare its designs and working drawings and ensure that the terms of its order are complete and accurate.;
6.2. The Customer shall provide at the Site, and at its expense, adequate and appropriate equipment and manual labour for unloading the Goods.
6.3. The customer shall accept delivery of the Goods to the Site and/or as agreed in the Acknowledgement of Order, and allow the Company access to the Site for such delivery and where installationwork is carried out by the Company:
6.3.1. allow the Company free and unimpeded access tothe Site for the purpose of carrying out the works;
6.3.2. be responsible for obtaining all statutory approvals necessary for installation and operation of the Goods;
6.3.3. off-load and check Goods and materials delivered to Site prior to the arrival of the Company's personnel. Provide secure undercover storage (where appropriate) adjacent to the site for all Goods and materials;
6.3.4. be responsible for Site safety and proper provision of health welfare facilities on Site.
Customer’s Obligation. During the continuance of this Agreement the Customer shall:
Customer’s Obligation. 1. 8.1 The customer shall:
a. provide the supplier with:
i. all necessary co-operation in relation to this agreement; and
ii. all necessary access to such information as may be required by the Supplier; in order to provide the Services, including but not limited to Customer Data, security access information and configuration services;
b. without affecting its other obligations under this agreement, comply with all applicable laws and regulations with respect to its activities under this agreement;
c. carry out all other Customer responsibilities set out in this agreement in a timely and efficient manner. In the event of any delays in the Customer's provision of such assistance as agreed by the parties, the Supplier may adjust any agreed timetable or delivery schedule as reasonably necessary;
d. ensure that the Authorised Users use the Services and the Documentation in accordance with the terms and conditions of this agreement and shall be responsible for any Authorised User's breach of this agreement;
e. obtain and shall maintain all necessary licences, consents, and permissions necessary for the Supplier, its contractors and agents to perform their obligations under this agreement, including without limitation the Services;
f. ensure that its network and systems comply with the relevant specifications provided by the Supplier from time to time; and
g. be, to the extent permitted by law and except as otherwise expressly provided in this agreement, solely responsible for procuring, maintaining and securing its network connections and telecommunications links from its systems to the Supplier's data centres, and all problems, conditions, delays, delivery failures and all other loss or damage arising from or relating to the Customer's network connections or telecommunications links or caused by the internet.
Customer’s Obligation. 3.1. The Customer shall provide the Company with:
3.1.1. the necessary co-operation in all matters relating to this Agreement; 3.
Customer’s Obligation. 6.1 Customer must carry out all operations that are necessary prior to the launch of the WHOOSH Service and on an on-going basis, in particular: • Opening and maintenance of the remote selling account throughout the duration of the agreement, • Supply of all of the city data for parameterisation of the solution (mapping of parking payment terminals, prices, zone, etc.) • Setting up of the system to verify electronic tickets and supply interface data, if applicable • Training of the city's employees • And, more generally, transmit to Parkeon any information useful to the implementation of the WHOOSH Service. It is hereby stipulated that the above list is given for indicative purposes and that it can be supplemented at the start of the project based on Customer’s specific characteristics.
6.2 Customer undertakes to render the WHOOSH Service in accordance with Parkeon’s recommendations and pursuant to the terms and conditions of the WHOOSH Service, provided to the User on the WHOOSH application and on the WHOOSH web site.
6.3 Customer undertakes not to use or authorise a third-party to exploit the information obtained from the use of the WHOOSH Service for purposes other than those related to the WHOOSH Service.
6.4 Customer acknowledges that the WHOOSH Service is paid for by credit card. Any transfer of information associated with the payment shall take place in a secure context. In particular, at the time of a payment, a credit card number and its validity date are transferred in a secure context using protocols in force, on the server of the service provider chosen by Parkeon. In this connection and pursuant to standard terms of the service provider chosen by Parkeon, Customer acknowledges the importance of complying with the security rules. For complete information on the security rules to be followed, Customer can refer to the PCI DSS (Payment Card Industry Data Security Standards) available, for example, on the Internet site of Visa or MasterCard, or from Financial Institutions. In addition, Customer undertakes to: • Ensure the application of the security patches on all of its machines, as well as setting up the machines’ secure configurations. • Never store on any type of medium information that is sensitive, such as credit card numbers or visual cryptograms (CVCs/CVVs) • Protect all of its passwords and change these regularly, in particular, the password needed to obtain access to the Account of the payment service provider • Protect access to its ser...
Customer’s Obligation. 6.1 Customer must carry out all operations that are necessary prior to the launch of the XXXXXXXX.xxx Service and on an on-going basis, in particular: • Opening and maintenance of the remote selling account throughout the duration of the agreement, • Supply of all of the city data for parameterisation of the solution (mapping of parking payment terminals, prices, zone, etc.) • Setting up of the system to verify electronic tickets and supply interface data, if applicable • Training of the city's employees • And, more generally, transmit to Flowbird any information useful to the implementation of the XXXXXXXX.xxx Service. • Verify signs including QR-codes if used on a regular bases in the field It is hereby stipulated that the above list is given for indicative purposes and that it can be supplemented at the start of the project based on Customer’s specific characteristics.
6.2 Customer undertakes to render the XXXXXXXX.xxx Service in accordance with Flowbird’s recommendations and pursuant to the terms and conditions of the XXXXXXXX.xxx Service, provided to the User on the XXXXXXXX.xxx application and on the XXXXXXXX.xxx web site.
6.3 Customer undertakes not to use or authorise a third-party to exploit the information obtained from the use of the XXXXXXXX.xxx Service for purposes other than those related to the XXXXXXXX.xxx Service.
6.4 Customer acknowledges that the XXXXXXXX.xxx Service is paid for by credit card. Any transfer of information associated with the payment shall take place in a secure context. In particular, at the time of a payment, a credit card number and its validity date are transferred in a secure context using protocols in force, on the server of the service provider chosen by Flowbird. In this connection and pursuant to standard terms of the service provider chosen by Flowbird, Customer acknowledges the importance of complying with the security rules. For complete information on the security rules to be followed, Customer can refer to the PCI DSS (Payment Card Industry Data Security Standards) available, for example, on the Internet site of Visa or MasterCard, or from Financial Institutions. In addition, Customer undertakes to: • Ensure the application of the security patches on all of its machines, as well as setting up the machines’ secure configurations. • Never store on any type of medium information that is sensitive, such as credit card numbers or visual cryptograms (CVCs/CVVs) • Protect all of its passwords and change these regul...
Customer’s Obligation. 7.1 The Customer must:
(a) Provide its acceptance for term and condition as provided under this Agreement by direct execution or by giving an approval as provided in the Website.
(b) not use anyone else to supply any Services to Vessels within the Port for the term of this Agreement;
(c) guarantee that any Container used by the Customer is in compliance with all applicable laws of Indonesia and international standards, including but not limited in respect to safety, stability, worthiness, fitness for purpose and security
(d) promptly pay all invoices issued in accordance with clause 10;
(e) promptly perform each task allocated to it in Schedules 4, 5 and 6 (if any);
(f) comply with the Operator’s Berthing Requirements described in Schedule 4;
(g) provide regular sailing schedules and notification of ETAs of Vessels in accordance with Schedule 4;
(h) submit to the Operator not later than 24 hours before the Vessel arrives one (1) complete set of Cargo documentation as is necessary for the orderly and efficient discharge/loading of that Vessel. Such documentation shall include, without limitation;
i. A complete and up-dated container stowage plan. The status, together with the respective gross weight, shall be shown against the individual container to be handled;
ii. A list of all containers to be discharged for subsequent delivery from the terminal upon which stowage position, holding temperature (if applicable), commodity, size, over dimensional, height, type, gross weight, status, port of discharge, transport mode and IMO code shall be shown against each individual container number;
iii. A detailed heavy lift or break-bulk cargo summary showing quantity, weight, measurement, type of cargo, packing, stowage, IMO codes, special lifting requirements and any other requirements and relevant information;
iv. Full information and required documentation on hazardous cargo;
(i) arrange for the delivery of Containers or Cargo to the Berth in accordance with the cut-off procedures described in Schedule 5 and supply not later than twenty four
