Service Portability Sample Clauses

Service Portability an employee transferred from the sending Employer to the receiving Employer will port her/his service and service-related banks to the receiving Employer;
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Service Portability. Both parties agree that due to the dynamic nature of Dial Access Internet traffic, it is their intent to allow portability of the Ports to different locations. Reasonable re-allocation of Ports between LCAs that are serviced by a single physical Pac-West location shall be accommodated without charge. In the event of a re-allocation of Ports between LCAs that are serviced by different physical Pac-West locations, the parties agree to negotiate in good faith with regard to timeframes and the one-time non-recurring costs, which shall be limited to reasonable time and materials, for such portability.
Sample 1
Service Portability. DAPSI encourages proposals that aim to create (or enhance) viable open alternatives for widely used proprietary services that limit our freedom to move: whether it is online conferencing tools like Google Hangouts, Skype or WhatsApp, online office applications, social networks, software repositories, online calendars, platforms like Salesforce, etc. A project can be a new project, but it can also build on top of upcoming open alternatives for these consumer and business services – such as Peertube, Pixelfed, Jitsi, Etebase, the XMPP ecosystem, OpenStreetMap etc. that can be extended. Since make switching easy is crucial, adding "Import from ..." functionality from widely used proprietary services in these projects can also help to make data and portability be a more satisfying experience. Due to the limited time of participation in DAPSI, projects under this category can create a first version as catalyst for future work of the community or improve existing works in the field. data and migrating data whenever and wherever it is desirable. It is the key enabler to move from services to services, e.g., it is important that individuals have the freedom to choose which parts of data to share and transfer (instead of being forced to an all-or-nothing approach). Self-sovereignty of individuals data and capacity for selective disclosure is a practical use case that is also the key focus of EU regulatory efforts associated with proposed amendments to the eIDAS regulation and introduction of EU digital identity passports. Beyond the basic technology infrastructure of digital credentials, etc, to promote uptake by mainstream industries, it is important that more business use cases are developed that reinforce and demonstrate the value of managing data disclosure in this way. Please, note that DAPSI is not looking for only blockchain-based ideas. Data sovereignty is a much broader concept than blockchain. The proposals that only address the blockchain aspect of Data sovereignty are not the target of DAPSI.
Sample 1
Service Portability. DAPSI encourages proposals that aim to create (or enhance) viable open alternatives for widely used proprietary services that limit our freedom to move: whether it is online conferencing tools like Google Hangouts, Skype or WhatsApp, online office applications, social networks, software repositories, online calendars, platforms like Salesforce, etc. A project can be a new project, but it can also build on top of upcoming open alternatives for these consumer and business services – such as Peertube, Pixelfed, Jitsi, Etebase, the XMPP ecosystem, OpenStreetMap etc. that can be extended. Since make switching easy is crucial, adding "Import from ..." functionality from widely used proprietary services in these projects can also help to make data and portability be a more satisfying experience. Due to the limited time of participation in DAPSI, projects under this category can create a first version as catalyst for future work of the community or improve existing works in the field. enable individuals to control their personal data and use it to their benefits. This sub- domain is therefore dedicated to the development of specific methods and tools that transfer users’ data from one environment to another with as little effort as possible. The FAIR1 principles, as well as syntactic and semantic interoperability, must be taken into account here. Solutions should also make use of open technologies, common shared formats, structures, and standards, where applicable. If it becomes necessary to develop a new standard, this must be well argued. It must be ensured that the standard-setting process involves relevant stakeholders and standardization committees and is efficient at the same time. A clear high-level definition is necessary. Possible areas and aspects of work are the following (a combination is also welcome): • Implementations featuring researched and evaluated models for interoperability, allowed open formats and open specifications of domain- specific data structures (e.g. a catalogue of basic standards and tools to transform between them). • Design and develop standardized vocabularies and ontologies describing relevant domains and their exploitation to structure personal data in order to facilitate data transfer without giving away company secrets or violating legal duties and obligations (taking already available GRPR-compliant efforts in developing data privacy vocabularies into account). • Tools or methods for semi-automatically converting data from o...
Sample 1

Related to Service Portability

  • HIPAA To the extent (if any) that DXC discloses “Protected Health Information” or “PHI” as defined in the HIPAA Privacy and Security Rules (45 CFR, Part 160-164) issued pursuant to the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”) to Supplier or Supplier accesses, maintains, uses, or discloses PHI in connection with the performance of Services or functions under this Agreement, Supplier will: (a) not use or further disclose PHI other than as permitted or required by this Agreement or as required by law; (b) use appropriate safeguards to prevent use or disclosure of PHI other than as provided for by this Agreement, including implementing requirements of the HIPAA Security Rule with regard to electronic PHI; (c) report to DXC any use or disclosure of PHI not provided for under this Agreement of which Supplier becomes aware, including breaches of unsecured protected health information as required by 45 CFR §164.410, (d) in accordance with 45 CFR §164.502(e)(1)(ii), ensure that any subcontractors or agents of Supplier that create, receive, maintain, or transmit PHI created, received, maintained or transmitted by Supplier on DXC’s behalf, agree to the same restrictions and conditions that apply to Supplier with respect of such PHI; (e) make available PHI in a Designated Record Set (if any is maintained by Supplier) in accordance with 45 CFR section 164.524;

  • Service Standards We provide the Services materially in accordance with the features and functionalities set out in the Specification Documents. We will use commercially reasonable efforts to make the Services available to you subject to operational requirements including maintenance and security.

  • Anti-Corruption Compliance (a) For the past three (3) years, neither the Company nor any of its Subsidiaries, nor, to the knowledge of the Company, any director, officer, employee or agent acting on behalf of the Company or any of the Company’s Subsidiaries, has offered or given anything of value to: (i) any official or employee of a Governmental Authority, any political party or official thereof, or any candidate for political office or (ii) any other Person, in any such case while knowing that all or a portion of such money or thing of value will be offered, given or promised, directly or indirectly, to any official or employee of a Governmental Authority or candidate for political office, in each case in violation of the Anti-Bribery Laws.

  • Health Insurance The Couple agrees that: (check one) ☐ - Each Spouse is responsible for THEIR OWN health insurance. ☐ - Health insurance IS PROVIDED by ☐ Husband ☐ Wife (“Health Insurance Paying Spouse”) to ☐ Husband ☐ Wife (“Health Insurance Receiving Spouse”). Health insurance shall include: (check all that apply) ☐ - Medical ☐ - Dental ☐ - Vision Care ☐ - Other. . To facilitate the use of such coverage for the Health Insurance Receiving Spouse, the Health Insurance Paying Spouse shall cooperate fully and in a timely manner, including, but not limited to, obtaining and providing all necessary insurance cards and claim forms, completing and submitting all necessary documents, and delivering all insurance payments.

  • Additional Regulatory Requirements Notwithstanding anything contained in this Agreement to the contrary, it is understood and agreed that the Bank (or any of its successors in interest) shall not be required to make any payment or take any action under this Agreement if:

  • Customer Identification Program (A) To assist the Fund in complying with requirements regarding a customer identification program in accordance with applicable regulations promulgated by U.S. Department of Treasury under Section 326 of the USA PATRIOT Act (“CIP Regulations”), BNYM will do the following:

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