Work Flows Clause Samples

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
View SourceView Similar (7)
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, ▇▇▇▇ will take care of the VM allocation onto the physical servers, while, on the other hand, ▇▇▇▇▇▇▇ 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...
View Source
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: 1. Physical fault detected or predicted by the hypervisors (server failure) or SDN controller (switch failure). 2. The orchestrator is notified of the fault and determines to take action. 3. The VDC tenant is notified of impending live migration. 4. VMs instances cloned and moved to alternative servers. 5. Alternative switches that connect the new servers are programmed with flows to implement the virtual network. 6. The new VM instances are started. 7. The initial VM instances are halted. 8. The initial switches have their flows removed. 9. The VDC tenant is notified of successful migration.
View Source
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.
View Source

Related to Work Flows

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Service Levels All service level requirements will be set forth in Exhibit A (“▇▇▇▇.▇▇▇ Referral Service Level Requirements”). Recipient ▇▇▇▇▇▇ agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the ▇▇▇▇.▇▇▇ Referral Service Level Requirements in effect at the time ▇▇▇▇.▇▇▇ identifies the Referral to Recipient Broker/Agent.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇.

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

  • Developer Operating Requirements The Developer must comply with the Transmission Owner’s operating instructions and requirements including but not limited to Transmission Owner’s Operation Coordination Agreement, as it may change from time to time. The Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time. Whether or not the Large Generating Facility is eligible for the Transition Period LVRT Standard set forth in Appendix G will be determined by the Commission. The Large Generating Facility will comply with the Transition Period LVRT Standard pending issuance of an order by the Commission determining the appropriate LVRT standard. For purposes of compliance with Appendix G, the Transmission Owner has determined that the Developer shall maintain the Large Generating Facility in service during a three-phase fault for 7 cycles. Infrastructure security of New York State Transmission System equipment and operations and control hardware and software is essential to ensure day-to-day New York State Transmission System reliability and operational security. The Commission will expect the NYISO, all Transmission Owners, all Developers and all other Market Participants to comply with the recommendations offered by the President’s Critical Infrastructure Protection Board and, eventually, best practice recommendations from the electric reliability authority. All public utilities will be expected to meet basic standards for system infrastructure and operational security, including physical, operational, and cyber-security practices. All personnel working in Transmission Owner’s facilities will require security background checks prior to entering and working in such facilities. New York Independent System Operator, Inc. Attn: Vice President, Operations ▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇ Schenectady, NY 12303 Senior Vice President of Transmission New York Power Authority ▇▇▇ ▇▇▇▇ ▇▇. ▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇-▇▇▇▇ Re: Large Generating Facility Dear : On [Date] [Developer] has completed Trial Operation of Unit No. . This letter confirms that [Developer] commenced Commercial Operation of Unit No. at the Large Generating Facility, effective as of [Date plus one day]. Thank you. NYISO: