Technical support to implement GRB Sample Clauses

Technical support to implement GRB. After the revision of the GRB guidelines the MA conducted intensive GRB training for the six existing GRB implementing SAIPs. The MA also conducted a light version of the training for all of the other SAIPs at one of the bi-annual learning workshops. As a result of this training, three additional SAIPs expressed an interest to implement GRB (see table 1 – late adapters), and they received support to do so. In addition to the development of the adapted GRB manual and the training for all SAIPs, the MA also made a significant technical support package available, which saw the MA gender expert travel to all SAIPs to review progress, to take part in the training of woreda- based gender experts or to assist in the conducting of sector-focused gender analyses (for a full table of all gender expert support provided, see annex 1). The training and support that SAIPs were given after the updating of the GRB guidelines was generally practical in nature. The MA expert explains that some of the SAIPs staff initially struggled with questions such as “what is the difference between sex and gender” and many individuals revealed that they still held traditional views about the roles of men and women, especially when it comes to typical ‘women’s chores’ such as fetching water. The training led to some introspection about how people’s culture influences their views on gender roles. There was a xxxxx difference between gender role perceptions in urban and rural areas, which shows how gender is dynamic and culture is always changing; in urban areas men also fetch water, it just involves a short walk to a standpipe beside the house! However, evidence from the predominantly urban-dwelling SAIP staff suggests that gender divisions remain prominent, with the majority of urban working women devoting most of their Saturdays to household chores and family responsibilities while urban professional men spend their Saturdays engaged in leisure activities. After the training, most SAIPs expressed relief that they had now been provided with the right tools to use GRB. Most SAIPs had good reasons for choosing the GRB tool: ADA staff explained: “The 3 sectors in which we work are highly gender sensitive, and there is a huge budget investment from government, so GRB can have a great effect for women and girls empowerment. With this tool we can really integrate women into the development mainstream.” REST stated: “We selected GRB because we feel SA must be inclusive, and because budget is a ...
AutoNDA by SimpleDocs

Related to Technical support to implement GRB

  • Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • TECHNICAL SUPPORT AND MAINTENANCE If technical support and maintenance is a part of the Goods that Contractor provides under the Contract, Contractor will use commercially reasonable efforts to respond to the Department in a reasonable time when the Department makes technical support or maintenance requests regarding the Goods.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Operational Support Systems (OSS 2.13.1 BellSouth has developed and made available the following electronic interfaces by which <<customer_name>> may submit LSRs electronically. LENS Local Exchange Navigation System EDI Electronic Data Interchange TAG Telecommunications Access Gateway

  • Procurement Plan 8. The Borrower shall update the Procurement Plan as needed throughout implementation of the Project, and on each anniversary of the Effective Date, the Borrower shall in consultation with ADB determine whether the Procurement Plan needs to be updated. The Borrower shall implement the Procurement Plan in the manner in which it has been approved by ADB.

  • Software Maintenance and Support If You purchase Software Maintenance and Support for the Software, the Software Maintenance and Support will be provided as described in Kofax’s then current Software Maintenance and Support Agreement, available at xxxx://xxx.xxxxx.xxx/legal/SMSA, and which is incorporated herein by this reference. If You are active and current on Software Maintenance and Support, You may request reconfigurations of the Software subject to Your payment of Kofax’s then current standard rates for such reconfigurations. Kofax will have no liability to You arising from or related to Your cessation of Software Maintenance and Support, whether from Your failure to timely renew Software Maintenance and Support or otherwise. If You elect to reinstate Software Maintenance and Support following expiration of the Software Maintenance and Support for whatever reason, You will (a) pay a reinstatement fee equal to the sum of the current annual Software Maintenance and Support fees, any unpaid Software Maintenance and Support fees from the date of expiration to the date of reinstatement, and an amount equal to one additional year of Software Maintenance and Support fees, and (b) apply all upgrades, enhancements and new releases to the Software needed to bring Your Software current with Kofax’s most current supported version of the Software. Software Maintenance and Support pricing will increase for renewal terms by an amount not to exceed 5% of the prior year term fee, provided that increases associated with additional software license purchases, if any, will be incorporated into the base for the purpose of calculation of each annual increase.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

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