Core Platform Maintenance Sample Clauses

Core Platform Maintenance. 2.1.1. Overview The Rodin platform versions concerned by this deliverable are: • 2.1(08.02.2011), • 2.2(01.06.2011), • 2.2.2(01.08.2011), • 2.3(04.10.2011), • 2.4(31.01.2012), • 2.5(30.04.2012). This year, the maintenance carried on fixing identified bugs, although an emphasis was put on rectifying usability issues. Indeed, during the annual meeting in Nice, the WP9 members agreed to refocus on addressing some specific bugs and issues reported by DEPLOY partners, and wished resolved by the end of DEPLOY. Thus, no new features were implemented but those mentioned in the description of work. The tasks to be performed by the WP9 members were then scheduled, prioritized and regularly updated during the WP9 bi-weekly teleconferences. The updates allowed to capture and integrate rapidly some minor changes to enhance the usability of the platform which were required by the DEPLOY partners. The following paragraphs will give an overview of the the work that has been performed concerning maintenance on the existing platform components (i.e. core platform and plug-ins). See the Release Notes[1] and the SourceForge[1] databases (bugs and feature requests) for details about the previous and upcoming releases of the Rodin platform. Some other which were later added and prioritized are worth to mention: • Possibility to highlight patterns in the Proving UI, • A better output providing warnings and errors in case of wrong or missing building configurations, • The switch to Eclipse 3.7, • A Handbook to complete and enhance the existing documentation.
Sample 1
AutoNDA by SimpleDocs

Related to Core Platform Maintenance

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

  • Project Maintenance The Local Government shall be responsible for maintenance of locally owned roads and locally owned facilities after completion of the work. The State shall be responsible for maintenance of the state highway system after completion of the work if the work was on the state highway system, unless otherwise provided for in existing maintenance agreements with the Local Government.

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement.

  • Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.

  • Road Maintenance Purchaser shall maintain roads, commensurate with Purchaser’s use, in accor- dance with Road Maintenance Requirements in C5.31 and the Road Maintenance Specifications. Performance of road maintenance work by Purchaser may be required prior to, during, or after each period of use. The timing of work accomplishment shall be based on Purchaser’s Op- erating Schedule under B6.31. When two or more commercial users are simultane- ously using the same road where Forest Service is not requiring maintenance deposits, the commercial users will develop maintenance responsibilities and arrangements for accomplishing the work. Forest Service must agree to this plan. If the commercial users cannot agree on main- tenance responsibilities, Forest Service shall resolve the differences. If Purchaser elects to use different roads than those listed in C5.31, Forest Service shall determine Pur- chaser’s commensurate share of road maintenance and revise road maintenance deposits in C5.32. If Forest Service cannot perform its full commensu- rate share of road maintenance, Forest Service shall make a cash payment to Purchaser for performance of such work. Unless agreed in writing, prehaul maintenance shall be completed on any portion of road prior to hauling on that portion. Maintenance, as used in this contract, does not include road reconstruction or repairs of an extraordi- nary nature.

  • Site Maintenance The authorized area shall be maintained in a neat, clean, and safe condition, free of any solid waste, debris, or litter, except as specifically authorized herein.

  • Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Equipment Maintenance If this Contract involves computer or telecommunications hardware or other mechanical or electrical Equipment (use of the word "Equipment" means all the foregoing) as a Deliverable, then, during the warranty period and during any period covered by annual maintenance, the Contractor will provide Equipment maintenance to keep the Equipment in or restore the Equipment to good working order. This maintenance will include preventative and remedial maintenance, installation of safety changes, and installation of engineering changes based upon the specific needs of the individual item of Equipment. This maintenance will also include the repair, replacement, or exchange deemed necessary to keep the Equipment in good working order. For purposes of this Contract, Equipment restored to good working condition means Equipment that performs in accordance with the manufacturer's published specifications. The Contractor will exert its best efforts to perform all fault isolation and problem determination attributed to the Equipment covered under this Contract. The following services are outside the scope of this Contract:

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