Scenario B Sample Clauses

Scenario B. Fast fluid transfer
AutoNDA by SimpleDocs
Scenario B. Scenario B was similar to the first one, but aiming at testing the availability and functionality of an alignment service, and a workflow usage within Taverna. Here, the validator got more difficulties, although the scenario is validated. Only one criterion (Req-TEC- 0106 – Format compliance) is reported as not fulfilled, contrary to the developer who had no problems. The external validator gives a few comments. More than one aligner is available through the registry and it was not clear which one to be selected. Moreover, although some documentation is available through Spinet, the documentation in Taverna was not sufficient enough to be able to use the service in a workflow. The validator had to look for information on the Internet, then chose to use the bsa aligner although it is not listed as a PANACEA tool in the catalogue, but was nevertheless integrated. Using the Spinet interface, bsa run correctly (although, from time to time, bsa failed without returning any error through the Spinet), but the final output was not PANACEA compliant.
Scenario B. Roma model
Scenario B. Within the scope of this SOW, it is the understanding of the parties that Customer’s influence over the determination of the means and purposes of processing of Dataset Personal Data qualifies it as a data controller in respect of such processing. The provisions in Appendix 2 shall apply to such processing. SCENARIO C: Within the scope of this SOW, it is the understanding of the parties that Customer’s influence over the determination of the means and purposes of processing of Dataset Personal Data qualifies it as a data controller in respect of such processing. The provisions in Appendix 2 shall apply to such processing. Additional terms (if any) (See MSA Guidance Notes) [insert details of any additional terms that apply (if any)] By signing below, each party confirms that it has read and understood the terms of this SOW and agrees to be bound by such terms from the SOW Commencement Date.
Scenario B. Within the scope of this SOW, it is the understanding of the parties that Customer’s influence over the determination of the means and purposes of processing of Dataset Personal Data qualifies it as a data controller in respect of such processing. The provisions in Appendix 2 shall apply to such processing. SCENARIO C: Within the scope of this SOW, it is the understanding of the parties that Customer’s influence over the determination of the means and purposes of processing of Dataset Personal Data qualifies it as a data controller in respect of such processing. The provisions in Appendix 2 shall apply to such processing. By selecting the appropriate Scenario, the data protection terms that apply is determined in relation to personal data that is not business contact data of the parties. See the description of the Scenarios on page 2 above for further details. Additional terms (if any) (See MSA Guidance Notes) [insert details of any additional terms that apply (if any)]
Scenario B. You have been assigned to a mentor who is of a race different from you. You find yourself uncomfortable and sense that your mentor is also feeling awkward. Your mentor does share his/her experiences and strategies on how to approach issues so that you do feel you are gaining something from this relationship. However, you frequently disagree with some of his/her suggested approaches and you find yourself increasingly frustrated. You believe the issue to be that your mentor has a problem with talking about your ethnic/racial background. • Will you address the issue or let it go? If you let it go, what will you do instead? • Is there anything you could have done early on to avoid this situation? • What concerns do you have about being mentored by someone of a different Race/culture or gender? • Are the concerns the same for each one of you? You and your mentor have been communicating frequently and enjoying the naturalness of the relationship and you both have great chemistry together. You have agreed to meet during the day but early on your mentor calls and informs you that s/he is unable to meet as scheduled but suggests meeting after work at a local restaurant. You meet and your conversation goes well, as usual and the atmosphere is relaxed. At some point in the conversation, your mentor talks about how much s/he enjoys this relationship but s/he does so in a way that leads you to think that his/her interest in you is becoming more personal than professional. • What are you going to do? • How will this affect your relationship from this point? • How will you handle this if both of you are single? • How would you react if the mentor reveals that s/he is gay/lesbian? • Are there circumstances when you feel that a mentor and mentoree can pursue a more intimate relationship without it affecting their mentoring?
Scenario B. Holiday: Friday = Observed, Saturday = Actual (non-premium) Schedule: Monday through Friday Sun Mon Tues Wed Thurs Fri Sat Straight Pay 8 8 8 8 Overtime Pay 8 (4 hrs) 1.5 x Pay* 8 (12 hrs) 8 (12 hrs) Holiday Pay 8
AutoNDA by SimpleDocs
Scenario B. Clinical data and images were previously collected in different research projects and are used in the neuGRID e-infrastructure, with two different possibilities: 1. the data are collected in neuGRID 2. the data are used, but not collected, in neuGRID In this scenario, informed consent and anonymization issues have already been handled in some way in the original research protocols.
Scenario B. 1 i) previous research protocol gives the possibility that data collected be included in other datasets/neuGRID; ii) previous research protocol rules out the possibility that data collected be included in other datasets/neuGRID; iii) previous research protocol does not take into account the possibility that data collected be included in other datasets/neuGRID In case i) the collection of the data in neuGRID is possible In case ii) the collection of data in neuGRID is not possible In case iii) the collection of data in neuGRID is possible under some conditions.

Related to Scenario B

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Interim Measures Notwithstanding any requirements for alternative dispute resolution procedures as set forth in Articles 18(B), any party to the Dispute may apply to a court for interim measures (i) prior to the constitution of the arbitral tribunal (and thereafter as necessary to enforce the arbitral tribunal’s rulings); or (ii) in the absence of the jurisdiction of the arbitral tribunal to rule on interim measures in a given jurisdiction. The Parties agree that seeking and obtaining such interim measures shall not waive the right to arbitration. The arbitrators (or in an emergency the presiding arbitrator acting alone in the event one or more of the other arbitrators is unable to be involved in a timely fashion) may grant interim measures including injunctions, attachments and conservation orders in appropriate circumstances, which measures may be immediately enforced by court order. Hearings on requests for interim measures may be held in person, by telephone, by video conference or by other means that permit the parties to the Dispute to present evidence and arguments.

  • Scaling “Scaling,” as used herein, involves:

  • Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When Southern Telecom or its authorized agent owns the splitter, Line Splitting requires the following: a non-designed analog Loop from the serving wire center to the NID at the End User’s location; a collocation cross connection connecting the Loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The Loop and port cannot be a Loop and port combination (i.e. UNE-P), but must be individual stand-alone Network Elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog Loop from the serving wire center to the NID at the End User’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port. 3.8.2 An unloaded 2-wire copper Loop must serve the End User. The meet point for the Voice CLEC and the Data LEC is the point of termination on the MDF for the Data LEC's cable and pairs. 3.8.3 The foregoing procedures are applicable to migration to Line Splitting Service from a UNE-P arrangement, BellSouth Retail Voice Service, BellSouth High Frequency Spectrum (CO Based) Line Sharing. 3.8.4 For other migration scenarios to line splitting, BellSouth will work cooperatively with CLECs to develop methods and procedures to develop a process whereby a Voice CLEC and a Data LEC may provide services over the same Loop.

  • Protective Measures We have implemented and will maintain appropriate technical and organisational measures in relation to the Services taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of Processing, as well as the likelihood and severity of risk to the rights and freedoms of data subjects. This includes measures relating to the physical security of Our facilities used to deliver them, measures to control access rights to Our assets and relevant networks, and processes for testing these measures. In accordance with Our obligations under applicable law, We may undertake digital forensic investigations in relation to the use of the Services and Subscriptions. You are responsible for using, and ensuring that your Users use, the controls and advice provided by the Services correctly and consistently.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester. 7.2.2 No later than thirty (30) Days prior to the earlier of the Scheduled Substantial Completion Date or Substantial Completion, Design-Builder shall provide to Owner for review a detailed testing plan for the Performance Tests (other than for air emissions). Owner and Design-Builder shall agree upon a testing plan that shall be consistent with the Performance Test Protocol contained in Exhibit A hereto. After such agreement has been reached, Design-Builder shall notify the Owner five (5) business days prior to the date Design-Builder intends to commence the Performance Tests and shall notify the Owner upon commencement of the Performance Tests. Owner and Independent Engineer each have the right to witness all testing, including the Performance Tests and any equipment testing, whether at the Site or at the Subcontractor’s or equipment supplier’s premises during the course of this Agreement. Notwithstanding the foregoing sentence, Owner shall bear the costs of providing a witness to any such testing and all such witnesses shall comply at all times with Design-Builder’s, Subcontractor’s or equipment supplier’s safety and security procedures and other reasonable requirements, and otherwise conduct themselves in a manner that does not interfere with Design-Builder’s, Subcontractor’s or equipment supplier’s activities or operations. 7.2.3 Design-Builder shall provide to Owner a Performance Test report (excluding results from air emissions testing), including all applicable test data, calculations and certificates indicating the results of the Performance Tests and, within five (5) business days of Owner’s receipt of such results, Owner, Independent Engineer and Design-Builder will jointly inspect such Work and review the results of the Performance Tests to verify that the Performance Guarantee Criteria have been met. If Owner or Independent Engineer reasonably determines that the Performance Guarantee Criteria have not been met, Owner shall notify Design-Builder the reasons why Owner determined that the Performance Guarantee Criteria have not been met and Design-Builder shall promptly take such action or perform such additional work as will achieve the Performance Guarantee Criteria and shall issue to the Owner another notice in accordance with Section 7.2.2; provided however that if the notice relates to a retest, the notice may be provided no less than two (2) business days prior to the Performance Tests. Such procedure shall be repeated as necessary until Owner and Independent Engineer verifies that the Performance Guarantee Criteria have been met. 7.2.4 If Owner, for whatever reason, prevents Design-Builder from demonstrating the Performance Guarantee Criteria within thirty (30) Days of Design-Builder’s notice that the Plant is ready for Performance Testing, then Design-Builder shall be excused from demonstrating compliance with the Performance Guarantee Criteria during such period of time that Design-Builder is prevented from demonstrating compliance with the Performance Guarantee Criteria; provided however that Design-Builder will be deemed to have fulfilled all of its obligations to demonstrate that the Plant meets the Performance Guarantee Criteria should such period of time during which Design-Builder is prevented from demonstrating the Performance Criteria exceed thirty (30) Days or extend beyond the Final Completion Date.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

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