Input Data Clause Samples
The Input Data clause defines the requirements and responsibilities related to the data provided by one party for use in a project or service. Typically, it specifies what data must be supplied, the format and timing of delivery, and any quality or accuracy standards that must be met. For example, a client may be required to provide accurate customer information or technical specifications before a service provider can begin work. This clause ensures that all necessary data is available and suitable for the intended purpose, thereby preventing delays, misunderstandings, or errors in the execution of the agreement.
POPULAR SAMPLE Copied 6 times
Input Data data that is generated, collected, recorded, or uploaded either by, from or in connection with, the Connected Equipment, including utilisation information regarding the Connected Equipment and the standard industry data SAE J1939 but excluding any data or information regarding ▇▇▇▇▇▇▇’▇ equipment control systems including how to achieve functional performance.
Input Data. The ▇▇▇▇ Payment Services are performed based on information provided by User. Inaccurate information provided by User will result in inaccurate functioning of, or failure to adequately complete, the ▇▇▇▇ payment process. It is User’s sole responsibility to provide complete and accurate information, and Autobooks will have no responsibility or liability in connection with errors, omissions, or failure to fulfill any ▇▇▇▇ payment request through the ▇▇▇▇ Payment Services which result from User’s failure to provide complete or accurate information.
Input Data. The Accounting Services are performed based on information provided by User. Inaccurate information provided by User will result in inaccurate reporting, journal entries, billed amounts, and the failure of other functions within the Accounting Services. It is User’s sole responsibility to provide complete and accurate information, and Autobooks will have no responsibility or liability in connection with errors or omissions in the Accounting Services which result from User’s failure to provide complete or accurate information.
Input Data. Accurate, complete, and correct data necessary for LEC to perform its services hereunder shall be the sole responsibility of LEA. LEC shall not be responsible for any delays or failure to prepare a claim because of incomplete, inaccurate, or incorrect data provided by LEA. LEC shall be responsible for the input of all information given to LEC by LEA in a reasonably accurate, complete and correct form provided same is provided to LEC by LEA. Any errors, mistakes or liability in connection with the failure of LEC to input such data, provided such data has been accurately, completely and correctly transmitted to LEC, shall be the sole responsibility of LEC and shall be corrected by LEC.
Input Data. The Bill Payment Services are performed based on information provided by User. Inaccurate information provided by User will result in inaccurate functioning of, or failure to adequately complete, the bill payment process. It is User’s sole responsibility to provide complete and accurate information, and Autobooks will have no responsibility or liability in connection with errors, omissions, or failure to fulfill any bill payment request through the Bill Payment Services which result from User’s failure to provide complete or accurate information.
Input Data. Client will provide Processor input data in a format acceptable to or designated by Processor. Input data shall be complete and correct, in a condition suitable for machine processing and compatible with the data processing equipment and programs of Processor. If the data submitted by the Client to the Processor are incorrect, incomplete, or not in the form designated by Processor, Client will pay Processor for any additional work performed to correct or complete the data. Processor may rely upon any data, information, or instructions provided by Client. If any error results from incorrect input supplied by Client, Client shall be responsible for discovering and reporting such error and supplying the data necessary to correct such error.
Input Data. There were four annotators involved in the annotation of the data used for the evaluation – an experienced annotator (annotator 1) and three students of the Czech language (annotators 2, 3 and 4). The annotation was started by annotators 1, 2 and 3, at the end of 2002 annotator 1 left and was replaced by annotator 4. Therefore we can compare three versions of annotation for each file concerned. The whole data set consists of 441 triples of annotated sentence structures. Table 1 gives an overview of the files annotated in parallel and their respective sizes in the number of trees and nodes. Phase # files # trees # nodes Annotators 1 (spring 2002) 2 94 1338 1, 2, 3 2 (autumn 2002) 1 48 825 1, 2, 3 3 (spring 2003) 1 52 702 2, 3, 4 4 (autumn 2003) 5 247 3537 2, 3, 4 Total 9 441 6402 Table 1: Data annotated in parallel All the numbers have been obtained using specific computational tools and subsequently manually checked and classified. The classification criteria and procedures will be described in corresponding subsections.
Input Data. Buyer retains all rights that Buyer already holds in data and other information that Buyer or persons acting on Buyer´s behalf input, upload, transfer, or make accessible in relation to, or which is collected from Buyer or third party devices or equipment by, the Work (“Input Data”).
Input Data. The input data of the MT will include SPOT 5 (SPOT: “Système Pour l’Observation de la Terre”; 10 m resolution) and SPOT 5 VEGETATION 2 satellite images from 2010. Regarding SPOT 5 images altogether data for five dates is available (06 July; 27 August; 28 September, 03 October, 08 November). In terms of SPOT 5 VEGETATION 2 data can be provided from the first decade in June 2010 to the last decade in October 2010. Note that there is one image available per decade. The images and processed data will be provided in the JPEG format (JPEG: Joint Photographic Experts Group) including figures with histograms.
Input Data. Two types of input data have been used to generate the C-RAID drifter data set: • The original drifter Argos messages transmitted by the drifters. They are collected, processed and distributed to users by CLS; • The archive of already decoded data available at the GDP ftp site (▇▇▇://▇▇▇.▇▇▇▇.▇▇▇▇.▇▇▇/pub/phod/buoydata/unkriged/); The main provider of original Argos data in the C-RAID project is our partner CLS. During the C-RAID Phase 1, CLS realized their tasks of data recompilation exclusively measured by drifters and all the treatment that this entails. Meanwhile, we collected drifter Argos data available in an AOML ftp site (▇▇▇://▇▇▇.▇▇▇▇.▇▇▇▇.▇▇▇/phod/pub/▇▇▇▇▇/data/argos_cd) and we used them in order to develop our tools to generate the delivery products of the C-RAID project. In C-RAID Phase 2, CLS transferred a comprehensive delivery of Argos messages emitted by drifting buoy. From C-RAID Phase 2 hereafter, the CLS delivery is our main source of data to decode drifter data.
3.1 GDP Drifter Argos messages
1. Each DS file contains satellite messages emitted by different drifters concerning location and geophysical parameter.