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;

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.

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.

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

Related to Service Portability

Data Portability Operator shall, at the request of the LEA, make Data available including Pupil Generated Content in a readily accessible format.
Portability (a) Employees are able to maintain their participation in the scheme should they transfer their employment between Catholic schools or to the Catholic Education Office. (b) The employee is obliged to notify the principal prior to appointment of their participation in the Deferred Salary Scheme and the date that leave is due to be taken. (c) Participation in the Deferred Salary Scheme shall not impede an application for employment in a Catholic school.
Number Portability Each Party shall adopt or maintain measures to ensure that suppliers of public telecommunications networks or services in its territory provide number portability on a timely basis, and on reasonable terms and conditions for mobile services and any other services as designated by that Party.
Health Insurance Portability and Accountability Act of 1996 This paragraph was intentionally left blank.
Health Insurance Portability and Accountability Act Grantee certifies that it is in compliance with the Health Insurance Portability and Accountability Act of 1996 (HIPAA), Public Law Xx. 000-000, 00 XXX Parts 160, 162 and 164, and the Social Security Act, 42 USC 1320d-2 through 1320d-7, in that it may not use or disclose protected health information other than as permitted or required by law and agrees to use appropriate safeguards to prevent use or disclosure of the protected health information. Grantee shall maintain, for a minimum of six (6) years, all protected health information.
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;
Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.
Substance Abuse Treatment Information Substance abuse treatment information shall be maintained in compliance with 42 C.F.R. Part 2 if the Party or subcontractor(s) are Part 2 covered programs, or if substance abuse treatment information is received from a Part 2 covered program by the Party or subcontractor(s).
Group Health Insurance The Employer shall provide a comprehensive health care insurance program for all permanent full-time and part-time employees. Health Plan characteristics and benefits shall be as provided in the Employer’s Agreement with the Ohio Civil Service Employees Association (hereinafter OCSEA). Regardless of the plan, employees will pay fifteen percent (15%) of the premium and the Employer will pay eighty-five percent (85%) of the premium; however for any alternative plans offered pursuant to the Agreement with OCSEA, the employees’ premium share will be determined by the Director of DAS, but will not exceed fifteen percent (15%) of the premium. The Employer’s premium share shall be paid on behalf of eligible employees as provided in the Employer’s Agreement with OCSEA. Employees who include a spouse as a dependent for healthcare coverage shall pay a surcharge as provided in the Employer’s Agreement with OCSEA. Eligibility provisions for employees enrolling in State provided health care plans shall remain the same as those in effect in the Employer’s Agreement with OCSEA. The Employer reserves the right to perform dependent eligibility audits upon recommendation of the Joint Health Care Committee. Health care costs paid on behalf of ineligible dependents will be subject to recovery. Deductibles, co-payments, and other plan design provisions for all benefit programs shall be the same as those prescribed in the Employer’s Agreement with OCSEA. Every year the Employer shall conduct an open enrollment period, at which time employees shall be able to enroll in a health plan, continue enrollment in their current plan, switch to another plan, subject to plan availability in their area, or waive coverage. The timing of the open enrollment period shall be established by the Director of the Department of Administrative Services (DAS), in consultation with the Joint Health Care Committee. Changes outside of open enrollment may only occur as prescribed in the Employer’s Agreement with OCSEA. Open Enrollment Fairs shall be held in accordance with Employer’s Agreement with OCSEA. There shall be established a Joint Health Care Committee composed of representatives of management, and of the various labor Unions representing State employees. The Committee shall meet regularly to monitor the operation of the State’s health care plans, and to make recommendations for the improvement of the plans and cost containment procedures. The Employer shall provide funding for dental, vision and the life benefits as described in Article 21 of the Employer’s Agreement with OCSEA and the Union’s Benefits Trust. Employee health insurance payments will be deducted from every paycheck. In the event an employee is receiving disability leave or Workers’ Compensation benefits, the Employer- policyholder shall continue, at no cost to the employee, the coverage of group health insurance for such employee for the period of such leave, but not beyond twelve (12) months. If the employee’s leave extends beyond twelve
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

Service Portability Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Related to Service Portability