Integration of other WP’s into the showcase Sample Clauses

Integration of other WP’s into the showcase. In the following, the integration of other WPs into the showcases is outlined. WP 1 - KUKA Integration of the KUKA LBR4 into the Care-O-bot 3 experimental platform is planned for the evaluation workshop 0. This includes some adaption of the mechanical and electrical subsystems of Care-O-bot 3 as well as software modifications to account for the specific drivers and interfaces of the KUKA controllers.
AutoNDA by SimpleDocs

Related to Integration of other WP’s into the showcase

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Maintenance – Line Splitting 3.6.1 BellSouth will be responsible for repairing voice troubles and the troubles with the physical loop between the NID at the End User’s premises and the termination point.

  • Maintenance and Support For so long as you timely pay your SaaS Fees according to the Invoicing and Payment Policy, then in addition to the terms set forth in the SLA and the Support Call Process, we will:

  • Maintenance Scheduling The NTO shall schedule maintenance of its facilities designated as NTO Transmission Facilities Under ISO Operational Control and schedule any outages (other than forced transmission outages) of said transmission system facilities in accordance with outage schedules approved by the ISO. The NTO shall comply with maintenance schedules coordinated by the ISO, pursuant to this Agreement, for NTO Transmission Facilities Under ISO Operational Control. The NTO shall be responsible for providing notification of maintenance schedules to the ISO for NTO Transmission Facilities Requiring ISO Notification. The NTO shall provide notification of maintenance schedules to affected Transmission Owners for NTO Transmission Facilities Requiring ISO Notification and Local Area Transmission Facilities pursuant to Section 3.5.3 of the ISO Services Tariff.

  • Maintenance and Support Services As long as you are not using the Help Desk as a substitute for our training services on the Tyler Software, and you timely pay your maintenance and support fees, we will, consistent with our then-current Support Call Process:

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

  • Maintenance and Inspection Consultant shall maintain complete and accurate records with respect to all costs and expenses incurred under this Agreement. All such records shall be clearly identifiable. Consultant shall allow a representative of City during normal business hours to examine, audit, and make transcripts or copies of such records and any other documents created pursuant to this Agreement. Consultant shall allow inspection of all work, data, documents, proceedings, and activities related to the Agreement for a period of three (3) years from the date of final payment under 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.

  • Maintenance and Repair – Line Sharing 3.6.1 C.M. shall have access for repair and maintenance purposes to any Loop for which it has access to the High Frequency Spectrum. If C.M. is using a BellSouth owned splitter, C.M. may access the Loop at the point where the combined voice and data signal exits the central office splitter via a bantam test jack. If C.M. provides its own splitter, it may test from the collocation space or the Termination Point.

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

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