Implementation of ARIA Data Management Sample Clauses

Implementation of ARIA Data Management. System (DMS)‌ Use of the DMS in 2019-2020 Trial Implementation The custom-developed ARIA DMS is intended to drastically improve ARIA’s capacity to carry out consistent trial implementation and data collection practices while equipping lead scientists in Kabul to remotely monitor and manage research across the country. With the initial design of the ARIA DMS completed in PY1, and further refined and tested in PY2, PY3 marks the first year of full system field testing with ARIA researchers in six provinces (Balkh, Baghlan, Herat, Kandahar, Kabul, and Nangarhar). As ARIA and GRAIN researchers rolled out the 2019-2020 winter wheat agronomic trials, GRAIN’s XXX team supported ARIA researchers to upload each trial design into the DMS and “push” the designs to ARIA field researchers in each province (reference Activity 1.A.4 for more details on the trial locations and objectives). In addition to uploading new trial designs, the GRAIN XXX and Research Teams also provide almost daily support to the provincial ARIA researchers, helping to troubleshoot issues, providing on-the-job support, and monitoring real- time data collection using the tablets. The Xxxxxx Xxxx International (RSI) database team continued to fine-tune new DMS features as per the feedback by the ARIA researchers and program team during previous DMS lessons learned workshop. Throughout Q1, and previous reporting periods, ongoing and frequent discussions were held with ARIA and GRAIN researchers through training and real practices in order to improve the DMS functionality to meet ARIA’s needs and expectations. So far, ARIA researchers shared positive feedback on the integration of new features as more user-friendly and practical. This quarter, three new DMS users have been registered, bringing a total of up to 66 active users to date. GRAIN has so far provided 18 digital tablets to ARIA researchers in support of the formal training program and DMS data collection. Support, training, and regular follow up will continue to build capacity for ARIA researchers to continue using the DMS for their experiments. DMS Training Program Continues During Q1 of PY3, the XXX team provided extensive DMS training—classroom and practical sessions—to 32 ARIA researchers (3 women). The training participants were trained on the recent DMS changes and the new DMS features. The training was conducted in Kabul, Nangahar, Balkh, and Herat. Participants first received assignments to simulate experiment data collection; then, ...
Sample 1
AutoNDA by SimpleDocs

Related to Implementation of ARIA Data Management

  • Implementation and Management 1.1 Properly constituted Occupational Health and Safety (OH&S) Committees or, where there is no OH&S Committee, Site Safety Supervisors/Safety Officers in conjunction with worker representatives, are the appropriate bodies to implement and administer alcohol and drug policy/programs (* see below).

  • Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Project Implementation 2. The Borrower shall:

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Implementation i) Where the job/time sharing arrangement arises out of the filling of a vacant full-time position, the full-time position will be posted first and in the event that there are no successful applicants, then both job/time sharing positions will be posted and selection will be based on the criteria set out in the Collective Agreement.

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

  • Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

Time is Money Join Law Insider Premium to draft better contracts faster.