Data Transfer Process. Client may order Mass Data Migration Services (the “Services”) through the IBM Cloud Control Portal (the “Portal) at the price set forth in the Portal subject to the following terms: (a) After Client places the Order, SoftLayer will send a portable storage device (“Device”) to the address specified by Client (“Client’s Address”). (b) Client will copy Client’s content (data) onto the Device, and the Device will automatically encrypt the data. Client will then ship the Device to the datacenter designated by IBM in the region selected by Client via one of the common carriers approved by IBM for this purpose. (c) SoftLayer will connect the Device to Client’s specified SoftLayer hardware (“Hardware”), transfer Client’s data from the Device to the Hardware, and delete all data from the Device after the transfer is complete. (d) Client is responsible for all charges associated with shipping, delivery, insurance, taxes and any other charges related to delivery of the Device to Client and to the agreed SoftLayer datacenter. (e) Client is not authorized to transfer the Device to any address other than the selected SoftLayer datacenter unless approved in advance by the IBM Cloud Global Trade Compliance team. Client’s removal of the Device from the country in which Client’s Address is located will automatically terminate this Agreement, and IBM will deem this a loss of the Device by Client for purposes of Section 5 liability. (f) The Device is for the exclusive use of Client for the purpose of the Services, and the Device may not be used for any other purpose. Client may not transfer the Device into the possession of a third party unless approved in advance by the IBM Cloud Global Trade Compliance team. (g) Only authorized account users may request the Services. (h) Client is solely responsible for and assumes the risk of harm caused by the actions of any third parties authorized by client to assist with transfer of the data, and indemnifies SoftLayer for all damages caused thereby.

Data Transfer Process o The Contractor shall create a secure automated data transfer process that meets the functional and operational needs of the OCEMS system. o The automated data transfer process will be initiated immediately based on the following conditions, triggers, and filters:  When the initiator (e.g. Paramedic filling out ePCR) marks his / her PCR as “Complete” and posts his/her chart to Service Bridge; and  The initiator marks the data Field “Transporting Agency” (IT5.50) with the desired transporting EMS provider. o The NEMSIS XML file that is transferred for each EMS event will be made available on a secure/HIPAA Compliant web-service that will be hosted by the Contractor. o The NEMSIS XML file will include a Portable Document File (PDF) for each patient care record exported. o EMS provider agencies and/or their agents will be provided the tools that they need to access the Contractor hosted web-service so that they may establish their own data retrieval methods. o The web-service must be capable of partitioning provider data so that only those agencies that should have access to specific EMS events are the only one’s permitted to do so. o The following provides an example of the workflow:  Fire Department A initiates a ePCR, marks the run as “Complete”, selects Ambulance Company B as the “Transporting Agency”, and then posts their run to Service Bridge.  Based on the triggers and filters defined above, a NEMSIS XML file for the event is automatically generated and made available on the Contractor’s secure web-service specific to Ambulance Company B.  Representatives for Ambulance Company B access the web-service using Contractor supplied credentials at an interval that meets their operational needs (every thirty (30) seconds, every minute, every five (5) minutes, etc.).

Data Transfer Process o The Contractor shall create a secure automated data transfer process that meets the functional and operational needs of the OCEMS system. o The automated data transfer process will be initiated immediately based on the following conditions, triggers, and filters:  When the initiator (e.g. Paramedic filling out ePCR) marks his / her PCR as “Complete” and posts his/her chart to Service Bridge; and  The initiator Service/Agency ID is one of twelve (12) fire departments.  Anaheim Fire Department (30005)  Brea Fire Department (30010)  Costa Mesa Fire Department (30020)  Fountain Valley Fire Department (30025) County of Orange Health Care Agency 27 MA-042-14010212 Orange County – Medical Emergency Data System HCA ASR 14-000839 Page 27 of 56  Fullerton Fire Department (30030)  Garden Grove Fire Department (30035)  Huntington Beach Fire Department (30040)  Laguna Beach Fire Department (30045)  Los Angeles County Fire Department (19110)  Newport Beach Fire Department (30055)  Orange City Fire Department (30060)  Orange County Fire Authority (30065) o The NFIRS XML file that is transferred for each EMS event will be made available on a secure/HIPAA Compliant web-service that will be hosted by the Contractor. o EMS provider agencies/fire departments and/or their agents will be provided the tools that they need to access the Contractor hosted web-service so that they may establish their own data retrieval methods. o The web-service must be capable of partitioning provider data so that only those agencies that should have access to specific EMS events are the only one’s permitted to do so. o The following provides an example of the workflow:  Fire Department A initiates a ePCR, marks the run as “Complete”, and then posts their run to Service Bridge.  Based on the triggers and filters defined above, a NFIRS XML file for the event is automatically generated and made available on the Contractor’s secure web-service specific to the initiators Service/Agency ID.  Representatives for Fire Department A access the web-service using Contractor supplied credentials at an interval that meets their operational needs (every thirty (30) seconds, every minute, every five (5) minutes, etc.)

Data Transfer Process. You may order Cloud Migration Services (the “Services”) through our Cloud Control Portal (the “Portal) at the price set forth in the Portal subject to the following terms: After You places the Order, We will: a. Analyze and categorize Your applications; b. Prepare the migration plan; c. Consider possibility of latency and scalability improvement; d. Define a comprehensive migration plan; e. Optimize geo location of servers; f. Transfer all Your data and applications to the new cloud.

Related to Data Transfer Process

Transfer Procedure After receipt by Silicon Valley Bank of the executed Warrant, Silicon Valley Bank will transfer all of this Warrant to its parent company, SVB Financial Group. By its acceptance of this Warrant, SVB Financial Group hereby makes to the Company each of the representations and warranties set forth in Section 4 hereof and agrees to be bound by all of the terms and conditions of this Warrant as if the original Holder hereof. Subject to the provisions of Section 5.3 and upon providing the Company with written notice, SVB Financial Group and any subsequent Holder may transfer all or part of this Warrant or the Shares issuable upon exercise of this Warrant (or the securities issuable directly or indirectly, upon conversion of the Shares, if any) to any transferee, provided, however, in connection with any such transfer, SVB Financial Group or any subsequent Holder will give the Company notice of the portion of the Warrant being transferred with the name, address and taxpayer identification number of the transferee and Holder will surrender this Warrant to the Company for reissuance to the transferee(s) (and Holder if applicable); and provided further, that any subsequent transferee other than SVB Financial Group shall agree in writing with the Company to be bound by all of the terms and conditions of this Warrant. Notwithstanding any contrary provision herein, at all times prior to the IPO, Holder may not, without the Company’s prior written consent, transfer this Warrant or any portion hereof, or any Shares issued upon any exercise hereof, or any shares or other securities issued upon any conversion of any Shares issued upon any exercise hereof, to any person or entity who directly competes with the Company, except in connection with an Acquisition of the Company by such a direct competitor.
Transfer Procedures 1. The transfers referred to in Article 4, 5, 6 and 7 shall be effected without undue delay and, at all events, within six months after all fiscal obligations have been met and shall be made in a convertible currency. All the transfers shall be made at the prevailing exchange rate applicable on the date on which the investor applies for the related transfer, with the exception of the provisions under point 3 of Article 5 concerning the exchange rate applicable in case of nationalization or expropriation. 2. The fiscal obligations under the previous paragraph are deemed to be complied with when the investor has fulfilled the proceedings provided for by the law of the Contracting Party on the territory of which the investment has been carried out.
Order Process When the start of production of your reservation nears, we will ask you to confirm your option selections and to provide full details of the legal purchaser of the Model X. Tesla will create an order for your Model X containing the information provided by you, and a Purchase Agreement indicating the estimated purchase price of your Model X, taking into account the base price of the model and any options included or that you select, plus estimates of any applicable taxes, duties, transport and delivery charges, and any other applicable fees. Tesla will then submit to you the order and the Purchase Agreement for your review. If you wish to proceed and purchase the Model X, you must sign and return the Purchase Agreement together with any amounts that are then required to be paid. Production of your Model X will then be commenced and your deposit payable under the Purchase Agreement will be held by Tesla as a non-refundable deposit (to the extent permitted by applicable law). At the time you enter into the Purchase Agreement, you may, at your sole option, notify us that you would like to take your Reservation Payment and apply it to your deposit. These procedures may be subject to change.
Order Processing Any order by you for the purchase of shares of the respective Funds through us shall be accepted at the time when it is received by us (or any clearing house agency that we may designate from time to time), and at the offering and sale price next determined, unless rejected by us or the respective Funds. In addition to the right to reject any order, the Funds have reserved the right to withhold shares from sale temporarily or permanently. We will not accept any order from you that is placed on a conditional basis or subject to any delay or contingency prior to execution. The procedures relating to the handling of orders shall be subject to instructions that we shall forward from time to time to all members of the Selling Group. The shares purchased will be issued by the respective Funds only against receipt of the purchase price, in collected New York or Los Angeles Clearing House funds subject to deduction of all concessions on such sale (reallowance of any concessions to which you are entitled on purchases at net asset value will be paid through our direct purchase concession system). If payment for the shares purchased is not received within three days after the date of confirmation the sale may be cancelled forthwith, by us or by the respective Funds, without any responsibility or liability on our part or on the part of the Funds, and we and/or the respective Funds may hold you responsible for any loss, expense, liability or damage, including loss of profit suffered by us and/or the respective Funds, resulting from your delay or failure to make payment as aforesaid.
Order Procedure 7.1 Subject to the Supplier's fulfillment of all of its obligations pursuant to this Agreement, ISR intends to purchase Machine/s from the Supplier by issuing a written Purchase Order dully signed by ISR all on a non-exclusive basis ("Purchase Order"). 7.2 The time of issuance of Purchase Orders and the quantity of the Machines in each Purchase Order shall be subject to ISR's discretion and Supplier herby waives any claim and/or demand against ISR including for loss of income and/or profits. 7.3 During the Agreement Period, ISR in its sole discretion, shall have the option to purchase from the Supplier up to four (4) more additional Machines and ancillaries (the “Optional Machines”). The terms and conditions of this Agreement will apply, mutatis mutandis, to the Optional Machines subject to Section 8.6. For the prevention of any doubt, it is hereby expressly emphasized that ISR is under no obligation whatsoever to order certain or any amount of Optional Machines from Supplier. 7.4 Upon receipt of a Purchase Order by email, Supplier shall confirm via email receipt of the Purchase Order to ISR's contact person. An original document of such confirmation shall be sent to ISR via air mail. 7.5 The Parties’ contact persons are as follows, or any replacement contact persons as notified in writing by one Party to the other: For ISR: Mr. Israel Railways Ltd. Address: Telephone: E-mail: ("IPM") For the Supplier: ("SPM") Each Party shall, in writing without undue delay, notify the other Party of changes in contact persons, addresses or facsimile numbers, if any. 7.6 Supplier will endeavor to furnish a secured electronic mail service or other equivalent means, in accordance with ISR safety requirements, which will be used by both Parties for the purpose of ordering procedure, requests, queries, reports etc. 7.7 The following original documents will be supplied by Supplier to ISR:
Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.
Additional Wet Weather Procedure 14.15.1 Remaining On Site a) for more than an accumulated total of four hours of ordinary time in any one day; or b) after the meal break, as provided for in clause 17.1 of the Award, for more than an accumulated total of 50% of the normal afternoon work time; or c) during the final two hours of the normal work day for more than an accumulated total of one hour, the Enterprise will not be entitled to require the employees to remain on site beyond the expiration of any of the above circumstances.
Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.
Purpose of Processing Personal Data will be Processed for the purpose of performing obligations under the Agreement.
Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

Data Transfer Process Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Sub-Clauses

Related to Data Transfer Process