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. A. Program Participant Data Collection
Data Collection and Management. Once you have identified which indicators to track (specific to distribution models implemented, outcome, output and the impact to be achieved), you will need to integrate data collection into your implementation plan. General guidelines for data collection include: • Collect data as close to the source as possible to ensure accuracy • Ensure data is entered correctly • Review Standard Operating Procedures (SOPs) for data collection with all staff assigned to enter data • Implement systems checks such as data format checking, edit validations, and mandatory checks to prevent invalid data from being entered • Enter only the minimum amount of personally identifiable information necessary for program activities • Maintain data in a secure environment and only transmit through secure methods • Limit the number of persons and entities granted access to identifiable data
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 ), Local Coordinators reporting to PO Reporting (This information will be reported to USAID team in bi-yearly basis) Collection and Storage (Program Officer & Program Associate) Analysis by project team (Data will be presented in quarterly report (Quarterly situation update reports) Project implementation team will review the validity and reliability of data and data source
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. 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. 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.
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.
Data Collection and Management. 3.1 System must 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)
Data Collection and Management. 12.1. In connection with providing the Service, Phygrid, 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 Phygrid 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 Phygrid without prior notice.
