Data Input Clause Samples

Data Input. The consultant shall establish a base network utilizing computer models such as Synchro, PASSER, TRANSYT-7F, TEAPAC etc. for the study time periods (i.e., morning, midday, p.m., etc.). The typical data used in the model include lane geometry, link speeds and distances, phase numbering, left- and right-turn phasing, existing signal timing (i.e., yellow and all-red intervals, pedestrian walk and flashing don’t walk intervals, minimum green, and detector settings), controller type, and coordinated reference phases. Field observations should be compared with the traffic operation results for each time period in the model. A review of the calibrated model shall be performed prior to moving forward with the timing plan development analysis.

Data Input. (a) HPS is responsible for the quality and accuracy of all data input to KeyBank and Vital and will implement appropriate procedures and take all necessary action to insure that such data is input in the proper sequence and format as specified by KeyBank and Vital. HPS Plan shall be administered in a manner compatible with KeyBank’s and Vital’s program. Any data submitted by HPS for processing which is incorrect will be corrected by HPS at its expense.

Data Input. The salary rates input to the survey shall be the rates paid for normally scheduled hours of work.

Data Input. This is the perhaps the most important stage in the chain of acts that have to be taken into consideration by the web service provider as it defines both the range of actions with regards to processing and the types of data outputs the web service may provide. Data input may belong to the following categories: (I) Input by the user (push model). This may be data manually entered to the system, uploaded as files or provided to the web service through aggregation or APIs. In all three cases the web service provider needs to take reasonable measures in order to ensure that the data provided by the user are granted with such a license so that processing and data output is actually legal. This has to be communicated to the end user through the web service terms and conditions. However, the service provider has no special obligation to clear rights over the input content/ data if the end user agrees with the terms and conditions and declares that all rights have been cleared. A process of notice and take down would be particularly helpful in cases where a third party identifies a rights violation. In any case the service provider has to inform the data/content provider regarding the type of processing (especially if it involves personal data), the degree to which such processing will take place on the web service provider's site or somewhere else, what kind of processing will take place, if the data are going to be retained and to whom the data are to be shared with or disseminated to. (II) Input by collecting data from third sources (pull model). This is the case where the web service provider actively seeks to obtain content from third parties either through specific licensing schemes or through a fair use/ dealing regime. Again, the preceding analysis regarding clearing of rights and what applies to web crawling is useful. The service provider is always encouraged either to use material that fall in the public domain or obtain explicit licenses and only do web crawling after mitigating risks as indicated above. Obtaining the necessary licenses also includes making redistribution agreements, passing licenses to the end user or use Open Public Licenses such as Creative Commons or ▇▇▇▇ licenses. It is important to note that the license should not only cover redistribution but also the types of processing that the web service requires. In the case where the processing is not perceptible to third parties and the service provider provides a data output that is base...

Data Input. Agency is responsible for ensuring that all data and other information entered by or on behalf of Agency or otherwise provided to RideAlong or obtained from Agency in connection with the Service (“Agency Data”) is complete and accurate. Agency Data may include non-public data and information relating to identified or identifiable individuals (“Identifiable Data”). The Service and all information, analyses, and other output provided by RideAlong are based on the Agency Data as received by RideAlong, and RideAlong is not responsible for any error, omission, or inaccuracy of or based on or resulting from Agency Data. Agency hereby grants to RideAlong, (a) a non-exclusive right to access, reproduce, process and otherwise use the Agency Data in connection with the provision of Service hereunder for the term of this Agreement, and (b) a non-exclusive and perpetual right to reproduce, process, distribute, disclose, publish, analyze and otherwise use Agency Data in an anonymized form, including any data or other information generated through the processing of Agency Data in connection with the Agency’s use of the Service (“Data Output”), as long as Agency is not identified as the source of such data. As between the parties, Agency exclusively owns all right, title, and interest in and to the Agency Data and Data Output. Notwithstanding anything in this Agreement to the contrary, ▇▇▇▇▇▇▇▇▇ exclusively owns all right, title, and interest in and to any new features, conclusions, derivative works, and any other proprietary findings developed by RideAlong through its use of the Agency Data and Output Data, including any intellectual property rights therein. The authorizations granted to, and restrictions imposed on, RideAlong under this Agreement, including under this Section 1.6, will extend to service providers and other contractors exercising such rights and licenses on RideAlong’s behalf. RideAlong shall give Agency reasonable notice prior to disclosure of Identifiable Data. Each party will maintain, throughout the term of the Agreement, appropriate administrative, technical, and physical safeguards designed to ensure the security and confidentiality of Identifiable Data, to protect and safeguard against anticipated threats or hazards to the integrity of, and the unauthorized or accidental destruction, loss, alteration, access, or use of, Identifiable Data in the possession or control of such party. Each party shall notify the other party in the event of any unauth...

Data Input. The Solution will be operated by the Customer via workstations. These workstations will be connected to the Solution as set forth in the Specified Configuration.

Data Input. The NACC member carriers provided the following 2011 data: • Cargo Available ton-miles (ATM) • Cargo Revenue ton-miles (RTM) • Available seat-miles (ASM) • Revenue passenger-miles (RPM) • Litres of fuel burned per year Members were also asked to provide information on any activities or initiatives in the following areas: • Aircraft modification and maintenance • Aircraft operating procedures • Cargo and baggage operations • In-flight/catering

Data Input. 1.1 The salary rates input to the survey shall be the rates paid for normally scheduled hours of work. 1.2 Such salaries shall be input for all AMEC NSS engineers at Bachelor and/or post-graduate levels in engineering disciplines, who are engaged in engineering or scientific work (incumbents of M&P 600000 series jobs and of FM&P 860000 series jobs, who are represented by The Society), including engineering trainees who are registered (or eligible for registration) by the OSPE.

Data Input. 4.1 The Customer shall provide the Input Data to the Supplier in the format agreed in the Technical Specification. If the Customer fails to provide the Input Data or fails to provide it in the agreed format, the Supplier shall be under no obligation to provide the Managed Services until such time as the Input Data is provided in accordance with this terms of this Agreement. 4.2 The Customer must transfer the Input Data to the Supplier on the date agreed in the Statement of Works. If the Customer fails to provide the data on the date agreed in a Statement of Work (or otherwise agreed between the parties), the Supplier shall be under no obligation to provide the Managed Services in accordance with the Timetable and revised timelines and any additional costs will need to be agreed between the Supplier and the Customer. 4.3 The Customer must transfer the Input Data to the Supplier using the secure transfer mechanism as defined by the Supplier. If the Customer fails to use the secure transfer mechanism, the Supplier shall be under no obligation to provide the Managed Services until such time as the Input Data is so provided. The Customer will be responsible for any accidental loss, destruction or damage to the Input Data caused as a result of a failure to use the secure transfer mechanism put in place by the Supplier. 4.4 The Customer acknowledges and agrees that it shall not access, store, distribute or transmit any viruses, or any material to the Supplier that: 4.4.1 is unlawful, harmful, threatening, defamatory, obscene, infringing, harassing or racially or ethnically offensive; 4.4.2 facilitates illegal activity; 4.4.3 depicts sexually explicit images; 4.4.4 promotes unlawful violence; 4.4.5 is discriminatory based on race, gender, colour, religious belief, sexual orientation, disability; and/or 4.4.6 is otherwise illegal or causes damage or injury to any person or property.