Summary of achievements Sample Clauses

Summary of achievements. Summarize major results and achievements and evaluate them compared with the objectives.
Sample 1Sample 2
AutoNDA by SimpleDocs
Summary of achievements. The CITYkeys set of indicators consists of a mixture of quantitative and semi-quantitative indicators. The semi-quantitative indicators for example provide an assessment of the way smart city projects are executed, the way the city government stimulates smart city development and of the potential of smart city projects to be taken up by other cities. For the semi-quantitative indicators data needs to be collected using interviews or an analysis of project or policy documents. There is a difference in the data collection process between the project and the city indicators. The project indicators are meant for assessing the success and potential for replication of smart city projects. In individual project assessments data needs to be collected from the project office, the project leader and/or others closely involved in the project. Cities might want to streamline the data collection for all their smart city projects, creating a reporting system and specific databases, but even then a number of the project indicators will require (qualitative) information that can only be gathered by involving persons involved in the project (e.g. through interviews, questionnaires). Data for the majority of the city indicators can be retrieved from statistical sources within the city administration or national or European level. The problem of such data is that it typically presents average (annual) figures for the whole city. For a city it may however be more interesting to analyse the differences between districts. Spatial data makes it possible to calculate indicators also for geographically restricted areas such as city districts. It is expected that CITYkeys testing phase will allow, to some extent, the evaluation of a project’s impact on city level as CITYkeys KPIs contain project-to-city link for many indicators. Additional sources of open data and public data can be found in national or European institutions (e.g. statistics bureaus). In any case, national data sources provide excellent support for data availability in all the five partner cities. EUROSTAT is potentially also of support for many data, but the problem is that information is given for regions and not for cities or municipalities as defined nationally. It is important to note that data for all indicators will obviously not be available immediately. A city that engages in smart city indicators starts a process. The CITYkeys indicator framework is a methodology for such a process. The city will need to ...
Sample 1
Summary of achievements. For the 55 outputs contracted for delivery SACTCG delivered a total of 128. Key Outputs • 19 events • 17 grant applications • 59 individual communication pieces Partners and stakeholders • 11 small community groups, members of SACTCG, were supported under this program, including 3 new member groups. • 18 partners were engaged in the delivery of the 3 workplans. Below is a sample list: o University of Canberra o SEE-Change Tuggeranong o Tuggeranong Community Council o Woden Community Council x Xxxxxx resident’s association o Wanniassa Shops Association o Australian Association of Environmental Education (AAEE) ACT Chapter o Holy Family Primary School Gowrie o Lake Tuggeranong College o Bunnings - multiple locations Future work These programs have built significant momentum in community stewardship of public lands in Southern ACT. They have established strong foundation partnerships for both the delivery of community engagement and education activities that will grow these programs in 2020-2021.
Sample 1
Summary of achievements. We briefly summarise what has been achieved with this model. The model is intended as an illustration. When the informal safety requirements have been finalised, this model may require revision to make it more realistic. For example the model does not consider the possibility of track being bi-directional. Other formalisations of the safety requirements may also be required in other formal notations. The model illustrates how some example hazards can be used to derive safety requirements. To derive safety requirements it was first necessary to introduce some concepts that are present in the domain. We also made explicit which hazards are not covered by an interlocking system. The four invariants given in Figure 5.8 are a formalisation of the relevant safety requirements in terms of these domain concepts. In addition, we introduced some very abstract behaviour and proved that this behaviour satisfies the formalised safety requirements. By modelling the safety requirements and a behaviour that is safe, and proving this to be true, we gain confidence that the safety requirements are consistent. By keeping the model simple and abstract we gain confidence that the safety requirements are correct. We should also validate the model by animation. Using refinement (according to the Rodin tools upon which UML-B is based) it would be possible to make this abstract model more detailed until it describes an interlocking system. The Rodin tools force us to prove that the more detailed model is a proper refinement of this abstract one and hence that the interlocking system also satisfies these safety requirements.
Sample 1

Related to Summary of achievements

  • Targets a) Seller’s supplier diversity spending target for Work supporting the construction of the Project prior to the Commercial Operation Date is ____ percent (___%) as measured relative to Seller’s total expenditures on construction of the Project prior to the Commercial Operation Date, and;

  • Table 7b - Other milestones and targets Reference Number Select stage of the lifecycle Please select target type from the drop-down menu Description (500 characters maximum) Is this a collaborative target? Baseline year Baseline data Yearly milestones (numeric where possible, however you may use text) Commentary on your milestones/targets or textual description where numerical description is not appropriate (500 characters maximum)

  • PERFORMANCE ISSUES The County will hold the Contractor responsible for meeting all of the Contractor’s contractual obligations. If performance issues arise that cannot be resolved between the Contractor and the County's Representative, the matter will be referred to the Procurement Division for appropriate action.

  • Performance indicators and targets The purpose of the innovation performance indicators and targets is to assist the University and the Commonwealth in monitoring the University's progress against the Commonwealth's objectives and the University's strategies for innovation. The University will report principal performance information and aim to meet the innovation performance indicators and targets set out in the following tables.

  • Performance Goals A. The Trust and State Street have developed mutually acceptable performance goals dated March 1, 2011 , and as may be amended from time to time, regarding the manner in which they expect to deliver and receive the services under this Agreement (hereinafter referred to as “Service Level Agreement”). The parties agree that such Service Level Agreement reflects performance goals and any failure to perform in accordance with the provisions thereof shall not be considered a breach of contract that gives rise to contractual or other remedies. It is the intention of the parties that the sole remedy for failure to perform in accordance with the provisions of the Service Level Agreement, or any dispute relating to performance goals set forth in the Service Level Agreement, will be a meeting of the parties to resolve the failure pursuant to the consultation procedure described in Sections V. B. and V.C. below. Notwithstanding the foregoing, the parties hereby acknowledge that any party’s failure (or lack thereof) to meet the provisions of the Service Level Agreement, while not in and of itself a breach of contract giving rise to contractual or other remedies, may factor into the Trust’s reasonably determined belief regarding the standard of care exercised by State Street hereunder.

  • Specific Objectives In accordance with Articles 34 and 35 of the Cotonou Agreement, the specific objectives of this Agreement are to:

  • Metrics The DISTRICT and PARTNER will partake in monthly coordination meetings at mutually agreed upon times and dates to discuss the progress of the program Scope of Work. DISTRICT and PARTNER will also mutually establish criteria and process for ongoing program assessment/evaluation such as, but not limited to the DISTRICT’s assessment metrics and other state metrics [(Measures of Academic Progress – English, SBAC – 11th grade, Redesignation Rates, mutually developed rubric score/s, student attendance, and Social Emotional Learning (SEL) data)]. The DISTRICT and PARTNER will also engage in annual review of program content to ensure standards alignment that comply with DISTRICT approved coursework. The PARTNER will provide their impact data based upon these metrics.

  • PERFORMANCE OBJECTIVES 4.1 The Performance Plan (Annexure A) sets out-

  • Goals Goals define availability, performance and other objectives of Service provisioning and delivery. Goals do not include remedies and failure to meet any Service Goal does not entitle Customer to a Service credit.

  • Project Objectives The Program consists of the projects described in Annex I (each a “Project” and collectively, the “Projects”). The objective of each of the Projects (each a “Project Objective” and collectively, the “Project Objectives”) is to:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!