Data Collection and Management. 3.1. To optimise the experience for users of our website and ARE members, we use the following sections and third-party services to collect data from our visitors and members.
4.2. By agreeing to this privacy policy, you guarantee that the personal data you have provided, are complete and correct.
4.3. By agreeing to this privacy policy, partners that provide personal data of third parties (e.g. their employees, members, board members, staff, subcontractors, and contracting parties) to ARE guarantee that (i) these personal data are lawfully obtained and (ii) that the partner is authorised to transfer these personal data to ARE. These partners will comply with the Privacy Legislation. These partners will indemnify ARE against, hold ARE harmless against and shall compensate ARE for all claims that would result from non-compliance with the abovementioned guarantees and Privacy Legislation.
Data Collection and Management. Participating States and Purchasing Entities will have the ability to capture and display transaction data as made available from the merchant; as well as overall Purchase Card program information. Below are the transaction data and card acceptance requirements.
3.1 System will capture and display transaction data at the following minimum levels: ▪ Cardholder ▪ Approving official ▪ Entity office or unit ▪ Account/billing (available at different levels) ▪ Entity Program Administrator or alternates (available at different levels) ▪ Participating State (all state entity transactional data, statewide administrative level and compliance review group)
3.2 System will have the ability to view transaction authorization/declines in real time.
3.3 System will post transactions within twenty-four (24) to forty-eight (48) hours of receipt from merchant.
3.4 System will have the ability to capture and display Level 1, Level 2, and Level 3 transaction data as made available from the merchant.
3.5 System will allow for Users to add notes, comments, and additional descriptions to a transaction in a separate field. This field must: ▪ Allow for alpha, numeric, and special characters. ▪ Be searchable ▪ Be reportable ▪ Be accessible to all hierarchies within the system
3.6 System will be able to capture and display merchant Tax Identification Number (TIN).
3.7 System will allow for user to input a minimum of 150 character of Entity defined accounting code structure/segments at the transaction level.
3.8 System will allow for the Purchasing Entity to set requirements for accounting code segments (i.e. mandatory, non-mandatory, etc.)
3.9 System will allow for Purchasing Entity to define, edit, maintain, and upload valid value tables for each accounting code segment.
3.10 System will actively validate accounting segment data against valid value table data as determined by the Purchasing Entity.
3.11 System will allow for Program Administrator to assign, edit, and delete "default" accounting codes for all program hierarchies within the Purchasing Entity.
3.12 System will allow for User to save and edit frequently used accounting codes.
3.13 System will allow for a minimum of 99 accounting code splits per transaction.
3.14 System will allow for User to manually enter tax detail at the transaction level.
3.15 System will allow Program Administrator to download the entire Purchase Card number for use in other systems.
3.16 Participating States and Purchasing Entities have a need to ...
Data Collection and Management. A. Program Participant Data Collection
1. Grantee must collect unduplicated participant demographic information (age, sex, ethnicity, and race) for each onsite, in-classroom direct education series included in the Grantee approved State Plan regardless of number of sessions in the series to provide actual counts in the Annual Education and Administration Reporting System (EARS)
Data Collection and Management. 12.1. In connection with providing the Service, OmboriGrid, its Affiliates, and/or Approved Partners will collect, store, and process Customer Data, where such collection, storage and processing is necessary to provide, develop or improve the Service, or to allow OmboriGrid and/or its Affiliates to fulfil its obligations under this Agreement. The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data, as well as its compliance with this Agreement and the Acceptable Use Policy and warrants that it has all rights, consents and approvals necessary to submit any Customer Data for the aforementioned purposes. Any and all Customer Data, which, in OmboriGrid’s sole discretion, infringes applicable laws, this Agreement, or the Applicable Use Policy, may be deleted by OmboriGrid without prior notice.
12.2. The Customer shall indemnify and hold OmboriGrid harmless from and against any damages, claims, losses and costs resulting from offensive, unlawful or objectionable Customer Data and shall indemnify and hold OmboriGrid harmless and defend or settle any claim suit or proceeding brought against OmboriGrid that is based upon a claim that any part of the Customer Data infringes any third-party intellectual property rights.
12.3. The Customer agrees and acknowledges that OmboriGrid, its Affiliates and Approved Partners have the right to create, obtain, collect, store, process and use Derived Data. All rights, title and interest in relation to Derived Data will be exclusively retained by OmboriGrid. OmboriGrid, its Affiliates and Approved Partners may freely use, amend or share any Derived Data for their business purposes as they deem fit, including, but not limited to, for the purpose of developing and improving the Service. Derived Data will not contain any Personal Data and OmboriGrid will not use the Derived Data in a way, which identifies the Customer or any User. The Customer acknowledges and agrees that OmboriGrid will not provide any copies of or information about Derived Data to the Customer, and that OmboriGrid may retain Derived Data upon termination of an Account, the Service, this Agreement, or otherwise.
Data Collection and Management. Reviewing IRB is not responsible for compliance with the requirements of any applicable federal, state, and local laws, rules, and regulations regarding electronic data management, including but not limited to: (1) the Privacy Rules at 45 CFR Part 146; and (2) rules governing electronic records at 21 CFR Part 11. Reviewing IRB is responsible only for providing the IRB Services and other obligations specified in Section I and accepts no additional responsibilities not herein described. Reviewing IRB certifies that they are an Association for the Accreditation of Human Research Protection Programs, Inc. (AAHRPP)-accredited IRB and will maintain an accreditation status of “Full Accreditation” throughout the term of this Agreement. Obligations of Relying Institution. For each research project, Relying Institution agrees to: Relying Institution agrees to submit an application to Reviewing IRB. Ensure investigators are appropriately qualified and meet Relying Institution’s standards for eligibility to conduct research including, but not limited to, completion of human subjects protection training, and collection and maintenance of conflicts of interest disclosure forms; Communicate to Reviewing IRB, on the IRB application for each research project, local context information, including requirements of any applicable state or local laws, regulations, institutional policies, standards, or other local factors relevant to each research project; Ensure compliance with Reviewing IRB’s determinations, provided there are no legal or policy concerns that would arise with compliance. In the event Relying Institution identifies legal or policy concerns that would arise with compliance, Relying Institution and Reviewing IRB shall address those concerns and make a good faith effort to resolve them. If Relying Institution’s concerns cannot be resolved in a mutually acceptable way, Relying Institution will withdraw its IRB application for that research project. Relying institution will also comply with all applicable federal, state, and local laws, rules, and regulations, including but not limited to: (1) 45 CFR Part 46, Subpart A (the Common Rule) governing protections for human research subjects; (2) the safety procedures specified in the Federal Food, Drug and Cosmetic Act at 21 U.S.C. § 301 et seq.; and (3) 21 CFR Parts 50, 56, 312, and 812 governing the review of research involving human subjects; Ensure appropriate monitoring of research and conduct internal checklists up...
Data Collection and Management. In order to build the strong technical foundation necessary to achieve the Guiding Principles, several technical teams were formed. Among those technical teams is the Data, Monitoring and Investigations Team (“DMIT”). The primary goal of the DMIT is to ensure that available hydrologic, environmental, and other pertinent data collected throughout the region is of a quality that can be used for the CFWI and is identified, inventoried, and accessible to support the CFWI technical initiatives and CFWI regulatory activities. As part of the Districts’ continuing coordination within the CFWI, the Districts commit to continuing their participation on the DMIT through appropriate technical staff. In order to further the goal of the DMIT, the Districts also agree to cooperate as follows:
Data Collection and Management. In order to track record for both outputs and outcomes indicators, a numbers of M&E tools will be used. These tools and techniques include; surveys, questionnaires, meeting records, most significant success stories, observations and so forth. The DFs and local coordinator will be provided with a template to provide their regular reports on dialogue activities, visitors to the Peace Libraries and mediation activities. The detailed process of data collection and management is as follows. Use Information for modifying the project activities if necessary Source (16 communities in 12 districts) Collection (DFs, Local Coordinators Reporting (This information will be reported to USAID team in bi-yearly basis)
Data Collection and Management. 3.1. To optimise the experience for users of our website and ARE members, we use the following sections and third-party services to collect data from our visitors and members.
Data Collection and Management. 1. Develop a data collection plan that outlines the methods, tools, and frequency of data collection.
2. Establish a data management system that ensures data integrity, confidentiality, and accessibility.
3. Train relevant staff on data collection techniques and ensure consistency and accuracy in data collection processes.
Data Collection and Management. All the collected data and data sources are summarized in the scheme of the data collection management shown in Figure 35. First, to ensure granularity, the functional structure has been derived from the IVG Product Development Cost Management (PDCM) system. The Functional Structure groups all the vehicle parts according to five levels of aggregation, starting from the vehicle itself (level 0) and arriving to “Funzione Tecnica” (level 4). Second, IVG has provided the bill of materials (BoM) of the baseline vehicles under study (spreadsheet extractions from Matrix and WVTA). Then, IVG has processed the weight information of BoM parts by means of a rollup algorithm and aggregated them in all the functional structure levels, up to the entire vehicle. At this point, XXXXXX created the LCA model in SimaPro filling data gaps with secondary data. For the preliminary assessment of EMPOWER demonstrators, XXXXXX has created the LCA models of hydrogen, FC system, Li-ion battery, and hydrogen tanks. The main characteristics of the two EMPOWER demonstrators have been reported in Table 5. The XXX demonstrator has the same overall dimensions as the ICE-propelled version. Therefore, the functional structures of the EMPOWER demonstrators have been created considering certain parts as carry-over from traditional diesel configurations, removing those parts that are limited to diesel vehicles (e.g., ICE, diesel tank, Adblue tank, etc.) and adding new parts (e.g., FC system, Li-ion battery, hydrogen tanks, integrated e-axle). A preliminary assessment of fuel and energy consumption of the EMPOWER demonstrators has been provided by AIT to model the use phase. Figure 35 Scheme of the data collection management Table 5 Main characteristics of the EMPOWER demonstrators under study. Diesel model used as baseline VP 1 - LONG HAUL - AE6CDCD1000075 VP 2 - REGIONAL- BD3CD6D1000017 Axis configuration 6x2P 6x2P Cab type Sleeper (AS) Active day (AD) Integrated e-axle dual e-drives e-axle dual e-drives e-axle Integrated e-axle weight 1390 kg 1390 kg Motor power 240 kW 240 kW Vehicle production site/s Madrid (Spain) + Ulm (Germany) Madrid (Spain) + Ulm (Germany) Estimated vehicle (empty) weight1 10514 kg 10107 kg 1Estimated using the curb weights of the diesel baselines as starting point (Table 4), removing those parts that are related to the diesel powertrain (e.g., fuel tanks, engine, gearbox) and adding those parts that are new in the two demonstrators (e.g., integrated axle, batteries, ...
