Work Flows Sample Clauses

Work Flows. Any and all responses or required responses to an open Action Item or to an initiated Work Flow process shall be input and managed through e-Builder. Work Flow processes that will be executed through e- Builder include but are not limited to those processes identified in Article
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Work Flows. The starting point for the demonstration will be the dashboard service of the orchestrator. There, a new VDC instance will be specified utilizing the graphical editor of the dashboard (e.g. OpenStack Horizon). For the new VDC instance, it will be possible to specify the quantity of the virtual nodes as well as the number of virtual machines per virtual node. For each virtual machine, it will be possible to state the desired resources in terms of CPU cores, storage capacity and memory (e.g. utilizing the OpenStack flavour templates) as well as the desired image for the operating system. Once the virtual nodes have been specified, the connectivity between the virtual nodes will be specified as well in terms of virtual links. In this regard, it will be possible to state both the source/destination and bit-rate for each virtual link. When the VDC request has been fully specified, the dashboard service will contact the orchestrator core, asking for the provisioning of a virtual slice that satisfies the requirements of the VDC request. In this regard, the orchestrator core (Heat) will contact the provisioning algorithms, which are the responsible for deciding on the optimal mapping of virtual resources to physical ones. The algorithms module will utilize the topological and resource utilization that can fetch from the physical infrastructure controllers (Nova for the compute and Neutron for the network) and will run the algorithm using this information as input. The output will be passed to the services responsible for provisioning the resources. On one hand, Xxxx will take care of the VM allocation onto the physical servers, while, on the other hand, Xxxxxxx will collaborate with the OpenDaylight controller to configure and establish the optical slice that corresponds to the realization of the virtual links. Once the whole VDC instance has been successfully deployed, the dashboard service will be informed, providing the details about the provisioned virtual infrastructure as well as the corresponding mapping. After this process, new VDC instance can be configured onto the same physical infrastructure. For this, the dashboard service allows for independent request of VDC instances in order to keep separated the requests that belong to different tenants. The process for provisioning a new VDC request is the same, with the difference that the physical infrastructure utilization has been changed. In this regard, the algorithms module will have to be updated with th...
Sample 1
Work Flows. Initially the network must allocate server nodes for virtual machines as well switches to support the virtual network. In this test case we do not wish to measure the performance of allocation as this is tested in case 2, see Section 3.2. Hence, in this case we will assume that a VDC instance and all relevant resources have already been successfully allocated. The workflows will involve the introduction or simulation of an error condition in the VDC instance. The result of the condition is that the VDC instance must coordinate the network hypervisors and SDN controller to redeploy the virtual components. In summary the actions of the COSIGN orchestrator and SDN controller in this scenario are as follows:
Sample 1
Work Flows. Each party will retain all rights to the clinical and medical workflows that it owned prior to the date hereof, or acquired or developed after the date hereof outside of performance under this Agreement. The parties expressly agree that each may freely use any workflows that the parties jointly develop under this Agreement, and that any such workflows that may rise to the level of Intellectual Property shall be memorialized in a separate SOW as provided for in Section 4.4.
Sample 1

Related to Work Flows

  • Work Schedule A 4/10 work schedule is four (4) ten hour days in a seven (7) day period, for a total of forty (40) hours per week.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Maintenance Services Subject to Client’s timely payment of the applicable maintenance fees, Accenture will make available the following maintenance services (“Maintenance Services”):

  • Customer Responsibilities Customer shall:

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

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

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