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.
Scope of Processing The subject-matter of Processing of Personal Data by Okta is the performance of the Service pursuant to the Agreement. The duration of the Processing, the nature and purpose of the Processing, the types of Personal Data and categories of Data Subjects Processed under this DPA are further specified in Appendix 1 to this DPA.
Instructions for Operators This agreement is intended to be provided to an Operator from a LEA. The Operator should fully read the agreement and is requested to complete the below areas of the agreement. Once the Operator accepts the terms of the agreement, the Operator should wet sign the agreement and return it to the LEA. Once the LEA signs the agreement, the LEA should provide a signed copy of the agreement to the Operator. Cover Page Box # 3 Official Name of Operator Cover Page Box # 4 Date Signed by Operator Recitals Box #5 Contract Title for Service Agreement Recitals Box #6 Date of Service Agreement Article 7 Boxes #7-10 Operator’s designated representative Signature Page Boxes #15-19 Authorized Operator’s representative signature Exhibit A Box #25 Description of services provided Exhibit B All Applicable Boxes Operator notates if data is collected to provide the described services. Defines the schedule of data required for the Operator to provide the services outlined in Exhibit A Exhibit D All Applicable Boxes (Optional Exhibit): Defines deletion or return of data expectations by LEA Exhibit E All Applicable Boxes (Optional Exhibit): Operator may, by signing the Form of General Offer of Privacy Terms (General Offer, attached as Exhibit E), be bound by the terms of this DPA to any other Subscribing LEA who signs the acceptance in said Exhibit. Exhibit F Boxes # 25-29 A list of all Subprocessors used by the Operator to perform functions pursuant to the Service Agreement, list security programs and measures, list Operator’s security measures
Sub-processing 11.1 The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub- processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.
11.2 The prior written contract between the data importer and the sub-processor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the sub-processor shall be limited to its own processing operations under the Clauses.
11.3 The provisions relating to data protection aspects for sub-processing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established, namely ........................................
11.4 The data exporter shall keep a list of sub-processing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5(j), which shall be updated at least once a year. The list shall be available to the data exporter’s data protection supervisory authority.
Office of Supplier Diversity The State of Florida supports its diverse business community by creating opportunities for woman-, veteran-, and minority-owned small business enterprises to participate in procurements and contracts. The Department encourages supplier diversity through certification of woman-, veteran-, and minority-owned small business enterprises and provides advocacy, outreach, and networking through regional business events. For additional information, please contact the Office of Supplier Diversity (OSD) at xxxxxxx@xxx.xxxxxxxxx.xxx.
Supplier’s Staff 3.3.1 Access to the Premises shall be limited to such Staff and the Supplier’s suppliers as are necessary for the Supplier to fulfil its obligations under the Contract. The Supplier shall co-operate with others working on the Premises to such extent as the Authority may reasonably require.
3.3.2 The Authority reserves the right to refuse to admit to, or to withdraw permission to remain on, the Premises:-
(a) for any member of the Staff; or
(b) for any person employed or engaged by any member of the Staff, whose admission or continued presence would be, in the reasonable opinion of the Authority, undesirable.
3.3.3 At the Authority’s written request, the Supplier shall provide a list of the names and business addresses of all persons who may require admission in connection with the Contract to the Premises, specifying the capacities in which they are concerned with the Contract and giving such other particulars as the Authority may reasonably request.
3.3.4 The Supplier’s Staff, engaged within the boundaries of the Premises, shall comply with such rules, regulations and requirements (including those relating to security arrangements) as may be in force from time to time for the conduct of personnel when at or outside those premises.
3.3.5 If the Supplier fails to comply with Clause 3.3.3 within one (1) Month of the date of the request and in the reasonable opinion of the Authority, such failure may be prejudicial to the interests of the Crown, then the Authority may terminate the Contract, provided always that such termination shall not prejudice or affect any right of action or remedy which shall have accrued or shall thereafter accrue to the Authority.
3.3.6 The decision of the Authority as to whether any person is to be refused access to the Premises and as to whether the Supplier has failed to comply with Clause 3.3.3 shall be final and conclusive.
Description of Processing Include a description of how the disclosed information will be processed by each receiving party.
GENERAL SERVICE DESCRIPTION Service Provider currently provides active medical, pharmacy(Rx) and dental administration for coverages provided through Empire and Anthem (medical), Medco(Rx), MetLife(dental) and SHPS (FSA) (Empire, Anthem, Medco, MetLife and SHPS collectively, the “Vendors”) for its U.S. Active, Salaried, Eligible Employees (“Covered Employees”). Service Provider shall keep the current contracts with the Vendors and the ITT CORPORATION SALARIED MEDICAL AND DENTAL PLAN (PLAN NUMBER 502 EIN 00-0000000) and the ITT Salaried Medical Plan and Salaried Dental Plan General Plan Terms (collectively, the “Plans”) and all coverage thereunder in full force through December 31, 2011 for Service Recipient’s Covered Employees. All claims of Service Recipient’s Covered Employees made under the Plans and incurred on or prior to December 31, 2011 the (“2011 Plan Year”) will be adjudicated in accordance with the current contract and Service Provider will continue to take such actions on behalf of Service Recipient’s Covered Employees as if such employees are employees of Service Provider. All medical, dental, pharmacy and FSA claims of Service Recipient’s Covered Employees made under the Plans (the “Claims”) will be paid by the Vendors on behalf of the Service Provider. Service Recipient will pay Service Provider for coverage based on 2011 budget premium rates previously set for the calendar year 2011 and described in the “Pricing” section below. Service Recipient will pay Service Provider monthly premium payments for this service, for any full or partial months, based on actual enrollment for the months covered post-spin using enrollments as of the first (1st) calendar day of the month, commencing on the day after the Distribution Date. Service Recipient will prepare and deliver to Service Provider a monthly self xxxx containing cost breakdown by business unit and plan tier as set forth on Attachment A, within five (5) Business Days after the beginning of each calendar month. The Service Recipient will be required to pay the Service Provider the monthly premium payments within ten (10) Business Days after the beginning of each calendar month. A detailed listing of Service Recipient’s employees covered, including the Plans and enrollment tier in which they are enrolled, will be made available to Service Provider upon its reasonable request. Service Provider will retain responsibility for executing funding of Claim payments and eligibility management with Vendors through December 31, 2013. Service Provider will conduct a Headcount True-Up (as defined below) of the monthly premiums and establish an Incurred But Not Reported (“IBNR”) claims reserve for Claims incurred prior to December 31, 2011 date, but paid after that date, and conduct a reconciliation of such reserve. See “Headcount True-Up” and “IBNR Reconciliation” sections under Additional Pricing for details.
Out of Scope Services Axon is only responsible to perform the professional services described in the Quote and this Appendix. Any additional professional services are out of scope. The Parties must document scope changes in a written and signed change order. Changes may require an equitable adjustment in the charges or schedule.
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
