In-Scope Application definition

In-Scope Application means the web-accessible Applications identified in subsection (a) above, provided that Subscriber has purchased a subscription for the Applications and signed a valid agreement with Mark43. Under no circumstance shall any reference to an Application that Subscriber has not purchased a subscription and signed an agreement for be construed to entitle Subscriber to use such Application. For the avoidance of doubt, In-Scope Applications do not include mobile versions or Applications that are in beta testing.
View Source
In-Scope Application means a Triple-S application for which Supplier provides IT Services requested by Triple-S. The In-Scope Applications existing as of the Effective Date are listed in Schedule X (Source of Truth) and each designated to be part of the Health Plan Portfolio, PC & Life Portfolio or TSM Portfolio.
View Source

Examples of In-Scope Application in a sentence

  • If the Production Support Charge is revised pursuant to Section 4.2 in connection with the addition of a new In-Scope Application, the revised Production Support Charge shall, at a minimum, reflect the Productivity Commitments stated in the table below for each remaining year of the Term.

  • If an In-Scope Application is not fully transitioned to Steady-State by the Scheduled Steady-State Date set forth in Exhibit E-3, then the Production Support Charge shall be reduced by an amount equal to the applicable Individual Application Production Support Charge until such In-Scope Application is fully transitioned to Steady-State (i.e., there are no charges payable for an In-Scope Application until it reaches Steady-State, except as provided in Section 4.7 with respect to Transitioned Employees).

  • Health Net’s right to remove In-Scope Applications (and the corresponding adjustment to charges and minimums) shall include the right to remove In-Scope Applications that relate to an In-Scope Application for which a Required Consent is not obtained if in Health Net’s reasonable determination such other In-Scope Applications should be grouped together for operational, maintenance or other reasons.

  • The Production Support Charge in Exhibit C-1 assumes each In-Scope Application will be transitioned to Supplier (and reach Steady-State) by the corresponding transition completion date set forth in Exhibit E-3 (“Scheduled Steady-State Date”).

  • Supplier shall notify Health Net not less than 180 days in advance prior to the date that an In-Scope Application would need to be upgraded in order to meet the foregoing requirement.

  • The rules governing expedited arbitration of the State Board of Mediation and Arbitration will apply except that briefs may be filed and the arbitrator will issue an explanatory decision.

  • Schedule X (Source of Truth) identifies the date by which each In-Scope Application is expected to transition from the Triple-S data center to a Supplier Facility (“Assumed Migration Date”).

  • Charge Due to Transition Delays The Production Support Charge in Exhibit C-1 assumes each In-Scope Application will be transitioned to Supplier (and reach Steady-State) by the corresponding transition completion date set forth in Exhibit E-3 (“Scheduled Steady-State Date”).

  • Accenture shall not knowingly insert into any System Deliverable or In-Scope Application or any other Hawaiian Telcom software any code which would have the effect of disabling or otherwise shutting down all or any portion of the Services.