Field Data Collection Sample Clauses

The Field Data Collection clause outlines the procedures and responsibilities for gathering information directly from a physical site or location relevant to the agreement. It typically specifies who is authorized to collect data, the types of data to be collected (such as measurements, observations, or samples), and any required methods or standards to ensure accuracy and reliability. This clause ensures that all parties have access to consistent and verifiable information, reducing misunderstandings and supporting informed decision-making throughout the project.
Field Data Collection. Due to the size and nature of this study, it will be important that all data is collected during each site visit, and archived properly. Site specific information will be collected at each point source location and recorded digitally on ▇▇▇▇▇▇ Field PCs. An example field PC is presented below. 3 United States Environmental Protection Agency. Protocol for Equipment Leak Emission Estimates. EPA-453/R- 95-017. November 1995. This information will include site characterization data, IR-detected emission data, emission rate testing data and information necessary to the modeling effort. Pre-formatted electronic datasheets stored on the ▇▇▇▇▇▇ Field PCs will be used to record site information and monitoring results. At the conclusion of each day’s point source testing, data stored on the Field PCs will be downloaded to spreadsheets and backed up on dedicated hard drives. All emissions detected with the IR Camera will be video recorded and saved as digital video files. These video files will subsequently be processed using Windows Movie Maker™ software. Processing of raw video files will consist of adding a title slide with timestamp and descriptive information followed by a digital photograph of the emission source. Some editing of the IR Camera video may be performed to improve quality of presentation. The completed video recording will then be saved with a descriptive filename as a Windows Media Video file (*.wmv).
View SourceView Similar (2)
Field Data Collection. Conduct field data collection and site survey for each facility to collect all pertinent electrical component field data. Data shall be compared to existing as built single line drawings for accuracy. As-built single line drawings shall be annotated (“red lined”) with corrections as needed. County Facility Operations staff will accompany the Contractor during the Field Data Collection phase to assist with identifying electrical components for the Arc Flash hazard analysis. County Facility Operations staff will be responsible for disassembling the required electrical equipment and provide field assistance to acquire all the necessary technical data.
View SourceView Similar (2)
Field Data Collection. Project Planning and Approval and Fieldwork Preparation Identifying and Contacting Respondents
View Source
Field Data Collection. Automation The Contractor shall a) conduct inventories of relevant assets tracked in the AF and b) use devices and tools to automate the process of collecting data in the field, and c) ensure that the data is uploaded accurately to the MDMS system. This section refers to manual collection of asset metadata not to meter intervals.
View Source
Field Data Collection. The CONSULTANT shall construct a project centerline for the basemap with stationing beginning at an identifiable point as determined by monuments or curb extensions from an intersecting street. The construction stationing will be generated using a wheel counter in the field. While in the field generating the centerline stationing, the CONSULTANT shall also record all surface features from back of sidewalk to back of sidewalk or where no curb and sidewalk exists, five feet outside of the edge of pavement. This shall include utilities, driveway locations, intersecting street locations, and channelization.
View Source
Field Data Collection. Where crash data is not available, Kittelson will collect field observations during the afternoon / peak period. Field observations will include driver yielding rates, conflict points, and other geometric characteristics that may be influencing crossing safety and/or crash potential.
View Source
Field Data Collection. Perform river substrate analysis to be used as a reference for the replacement crossing design.
View Source
Field Data Collection. Reconnaissance trips to all study sites were conducted in January and February 2011 to gain preliminary insight into the local context (social structures, land use patterns and environmental governance systems) and how the contextual factors influenced human-crane interactions. The bulk of the data presented in this chapter were collected between July and November 2011. In Zimbabwe, data collection took place in July 2011 and Kenya and Uganda, it was undertaken in October and November 2011, respectively. Although comprehensive data collection took place in 2011, subsequent trips (five in total) to the sites between 2012 and 2014 provided opportunities to verify data collected and identify phenomena that might not have been captured. Data collection methods included semi-structured interviews, group discussions and researcher observations. The total number of respondents involved in semi-structured interviews and group discussion participants are presented in Table 2.2. In total, 187 individuals were interviewed in the three countries (ranging from 24% up to 32% of the total households in the catchment areas), and 168 individuals were involved in group discussions (group size ranging from 15 up to 44 people). In Zimbabwe, interviews were conducted in the local language, Shona, the author’s first language. Local translators were hired in Kenya and Uganda to cater for non-English speakers although a significant proportion of respondents understood English. Site Number of respondents involved in semi- structured interviews and group discussions Total number of households in the catchment of the wetland under consideration, percentage of households involved in semi- structured interviews ▇▇▇▇▇▇▇-▇▇▇▇▇▇▇ Crop and livestock producers (18), Community elders /leaders (3), Environmental Officers (2), County administrators (2), Milk buyers (3) Group discussion participants (44) 67 (31,3%) Saiwa Chief (1), Village leaders (2), Wetland plot holders (22), Environmental Officers (2), Forestry Officer (1), Wildlife Officers (2) Group discussion participants (22) 106 (23,6%) Kaku Wetland plot holders (10), Wetland Management Committee members (4), Fishermen (5), Livestock herders (10), Environmental Officers (3), County leaders (2), Nature Uganda Project Assistant (1) Group discussion participants (30) 94 (30,9%) ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇ growers (22), Wetland Management Committee members (4), Cooperative society leaders (6), Environmental Officer (1), Agricultural Officer (1), Nat...
View Source

Related to Field Data Collection

  • Data Collection The grant recipient will be required to provide performance data reports on a schedule delineated within Section A of this contract, Specific Terms and Conditions.

  • Data Collection, Processing and Usage Personal data collected, processed and used by the Company in connection with Awards granted under the Plan includes the Grantee’s name, home address, email address, telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Awards granted, cancelled, exercised, vested, or outstanding. In granting Awards under the Plan, the Company will collect the Grantee’s personal data for purposes of allocating shares of Common Stock in settlement of the Awards and implementing, administering and managing the Plan. The Company collects, processes and uses the Grantee’s personal data in compliance with Company’s Employment Data Protection Standards and the Uses of Employment Data for the Company’s Entities. The Grantee may exercise rights to access, correction, or restriction or deletion where applicable, by contacting the Grantee’s local HR manager or initiating a request through ▇▇▇.▇▇▇▇.gehealthcare.com.

  • Data Collection and Usage The Company and the Service Recipient collect, process and use certain personal information about Participant, including, but not limited to, Participant’s name, home address, telephone number, email address, date of birth, social insurance number, passport or other identification number, salary, nationality, job title, any shares or directorships held in the Company, details of all awards granted under the Plan or any other entitlement to shares awarded, canceled, exercised, vested, unvested or outstanding in Participant’s favor (“Data”), for purposes of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is Participant’s consent.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s ▇▇▇▇ from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth ▇▇▇▇ ▇▇▇▇ identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.