Methodology to Sample Clauses

Methodology to achieve the objectives of the project, in particular the provision of integrated services Overall Project Methodologies and Structure The EMI project is strongly oriented to the provision of software and services in support to the operational activities of EGI, PRACE and other DCIs and to the scientific user communities who rely on the distributed computing infrastructures for their research. EMI needs to be able to carry out software development activities to consolidate, standardize and evolve its middleware components and at the same time provide timely and efficient maintenance and support services and release management services to its users. The EMI project methodologies and structure are modelled on standard software engineering concepts used by small and large distributed development activities, both commercial and open source, and on the processes described by the ITIL guidelines, the world most widely accepted approach to IT service management. In particular EMI adopts two concepts from ITIL, those of Functions and Services. The Functions provide project-wide support within the project to the Services; they allow to make economies of scale and to provide a coherent coordination framework to all Services enforcing common guidelines and rules, tools, processes and collaborative environments. The Functions are implemented by the project Work Packages. The Services, conversely, are specific activities provided by the project to the users (both infrastructure providers and research communities) in well defined technical areas. Essentially the Services correspond to the various middleware services and components (or tightly integrated groups of them) that must result in production-quality releases of software to the infrastructures and any related support activities. The Services are implemented by the project Product Teams. In addition, they implement the concept of „self-organizing‟ development teams, which is at the core of modern Agile development methodologies like Scrum. While the Functions (Work Packages) are static and form the structure of the EMI project, the Services (Product Teams) are dynamic and can change during the project execution, as middleware services are phased out or introduced in response to the requirements agreed with the infrastructures and the users. They constitute the project Service Catalogue and are the object of Service Level Agreements in order to better formalize the relationship between EMI and the major infrastructu...
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs

Related to Methodology to

  • Methodology 1. The price at which the Assuming Institution sells or disposes of Qualified Financial Contracts will be deemed to be the fair market value of such contracts, if such sale or disposition occurs at prevailing market rates within a predefined timetable as agreed upon by the Assuming Institution and the Receiver.

  • Benchmarking Report For the purposes of this Framework Schedule 12 “

  • TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order.

  • Timetable In order to set a timetable and procedural framework within which the subcommittees will accomplish their tasks, the parties have further agreed to the following: The subcommittees referenced in Section 1 above will be appointed and have their first organizational meeting within six (6) weeks of the date of the MOU ratification. Each subcommittee shall provide to the Head of the affected Department a final report no later than thirty (30) weeks after the date of the MOU ratification. The Department Head who receives a final report will meet with the LMC to provide feedback on the report, indicating areas of acceptance and explaining the reasons for rejecting any of the recommendations in the report.

  • Benchmarking 19.1 The Parties shall comply with the provisions of Framework Schedule 12 (Continuous Improvement and Benchmarking) in relation to the benchmarking of any or all of the Goods and/or Services.

  • Claims Review Methodology a. C laims Review Population. A description of the Population subject to the Quarterly Claims Review.‌

  • Evaluation Procedure The procedural requirements set forth in this agreement to provide specificity to the statutory obligations established under sections 3319.111 and 3319.112 of the Ohio Revised Code and to conform to the framework for the evaluation of teachers developed under section 3319.112 of the Ohio Revised Code.

  • Testing Procedure A. For alcohol testing, the member shall be first given a breath test, at the collection site, followed by a confirmatory urine test only where the breath test reveals an initial positive alcohol level of .04 grams per 210 l. of breath. If the initial breath test results are below this level, testing shall be discontinued; if confirmatory urine tests results are below a level equivalent to .04 grams per 210 l. of breath, the confirmatory test shall be considered negative.

  • Calculation methodology No adjustment in the Conversion Price need be made unless the adjustment would require an increase or decrease of at least 1% in the Conversion Price then in effect, provided that any adjustment that would otherwise be required to be made shall be carried forward and taken into account in any subsequent adjustment. Except as stated in this Article VI, the Conversion Rate will not be adjusted for the issuance of Common Stock or any securities convertible into or exchangeable for Common Stock or carrying the right to purchase any of the foregoing. Any adjustments that are made shall be carried forward and taken into account in any subsequent adjustment. All calculations under Article V and Section 6.06 hereof and this Section 6.07 shall be made to the nearest cent or to the nearest 1/10,000th of a share, as the case may be.

  • Program Evaluation The School District and the College will develop a plan for the evaluation of the Dual Credit program to be completed each year. The evaluation will include, but is not limited to, disaggregated attendance and retention rates, GPA of high-school-credit-only courses and college courses, satisfactory progress in college courses, state assessment results, SAT/ACT, as applicable, TSIA readiness by grade level, and adequate progress toward the college-readiness of the students in the program. The School District commits to collecting longitudinal data as specified by the College, and making data and performance outcomes available to the College upon request. HB 1638 and SACSCOC require the collection of data points to be longitudinally captured by the School District, in collaboration with the College, will include, at minimum: student enrollment, GPA, retention, persistence, completion, transfer and scholarships. School District will provide parent contact and demographic information to the College upon request for targeted marketing of degree completion or workforce development information to parents of Students. School District agrees to obtain valid FERPA releases drafted to support the supply of such data if deemed required by counsel to either School District or the College. The College conducts and reports regular and ongoing evaluations of the Dual Credit program effectiveness and uses the results for continuous improvement.

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