Deliverables and concrete timelines Sample Clauses

Deliverables and concrete timelines. The table below shows an indicative timeline of anticipated individual assignments. Translations of these assignments should be delivered within a reasonable time. For news articles and media releases, translation should be completed within one working day, ideally within a few hours of assignment. Deliverables and expected quality/quantity Expected time investment (days) News articles, feature stories, media releases (approx. 20,000 words) Year-round Video scripts, photo essays’ text and posters’ text (approx. 6,000 words) Year-round Presentation materials (PPT slides) (approx. 5,000 words) Year-round Development project overviews (approx. 3,000 – 6,000 words) Oct 19 – June 20 Frequently asked questions about development projects (approx. 8,000 words) Oct 19 – June 20 Synthesis of State of Basin Report 2018 (approx. 15,000 words) Nov 19 MRC Indicator Framework (approx. 13,000 words) Nov 19 Max. 15 leaflets and brochures of MRC knowledge (approx. 1,800 words each) Year-round The number of words indicated above are mostly estimates, and the actual number of words might differ from those indicated figures.
Sample 1Sample 2
AutoNDA by SimpleDocs
Deliverables and concrete timelines. Deliverables and Expected Quality Number of Days Deadline Conduct a needs-assessment, analyse the assessment and discuss the training options with HR/IT. Then develop a training methodology, along with a training programme, for discussion with HR/IT. 0.5 6 July 2023 Develop training materials and submit to HR/IT 1 Provide two training sessions using the same lesson plan for 2 groups of staff 2 11-12 July 2023 Submit a brief report, following a pre- and post- training assessments. 0.5 21 July 2023 Total Number of Days 4 days
Sample 1
Deliverables and concrete timelines. The following shows an indicative timeframe of anticipated tasks. Final products should be delivered in a reasonable time following discussion. Deliverables and expected quality/quantity Expected time investment (days) Deadline Review MRC Style Guide, Branding Guideline and MRC Admin Manual on Communication part and produce a work plan for the update 2 Nov 19 Provide suggested update and produce the first draft of the updated MRC Style Guide 8 Nov 19 Final draft of the updated MRC Style Guide following revisions 5 Dec 19 Various public information materials and/or reports drafted, edited or re-written 30 Dec 20 The possibility of other publications, or any modification of the above publications, can be discussed after the initial information gathering for the target publications. The final publication formats can be also revisited and determined at the design stage, following the MRC design standard and predecessor publications. Images will be principally provided by the MRCS. The consultant is expected to modify the texts prepared for these publications to be re-used on the MRC website or other communication channels during the consultancy, if required.
Sample 1

Related to Deliverables and concrete timelines

  • 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.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Construction Documents Phase Services 3.4.1 Based on the Owner’s approval of the Design Development Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Construction Documents for the Owner’s approval. The Construction Documents shall illustrate and describe the further development of the approved Design Development Documents and shall consist of Drawings and Specifications setting forth in detail the quality levels and performance criteria of materials and systems and other requirements for the construction of the Work. The Owner and Architect acknowledge that, in order to perform the Work, the Contractor will provide additional information, including Shop Drawings, Product Data, Samples and other similar submittals, which the Architect shall review in accordance with Section 3.6.4.

  • Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products

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