- Moderate System Impact Sample Clauses

- Moderate System Impact. The Software suffers an error or issue (which is not of Severity 1) which cannot be reasonably circumvented and which substantially impairs the use of one or more portions or features of the Software required by Licensee to perform necessary business functions. MyECheck will acknowledge any such reported error or issue promptly, but in no event longer than within four (4) hours and, if Licensee is using the Software in Production, will use commercially reasonable efforts to address and remedy such error with timeliness corresponding to the severity of the impact of such error on Licensee's business operation, including but not limited to working continually to address and remedy such error during MyECheck's normal Maintenance hours.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
- Moderate System Impact. The Software suffers an error (and is not of Severity 1) which cannot be reasonably circumvented and that substantially impairs the use of one or more portions or features of the Production Software required by Customers to perform necessary business functions. MyECheck will acknowledge any such reported Production system error promptly, but in no event longer than within four (4) hours and will promptly address and remedy such error during MyECheck's normal Maintenance hours.
Sample 1Sample 2
- Moderate System Impact. The Software suffers an error or issue (which is not of Severity 1) which cannot be reasonably circumvented and which substantially impairs the use of one or more portions or features of the Software required by Customer to perform necessary business functions. GreenPay will acknowledge any such reported error or issue promptly, but in no event longer than within four (4) hours and, if Customer is using the Software in Production, will use commercially reasonable efforts to address and remedy such error with timeliness corresponding to the severity of the impact of such error on Customer's business operation, including but not limited to working continually to address and remedy such error during GreenPay's normal Maintenance hours.
Sample 1
- Moderate System Impact. Causes a loss of a product's major function, but not all of its functionality. This covers problems which must be corrected but progress is not prevented but immediate attention is not required. This includes an isolated, reproducible problem resulting in a system crash or the failure of a significant utility or problem delaying Licensee's development schedule.
Sample 1

Related to - Moderate System Impact

  • Study Population ‌ Infants who underwent creation of an enterostomy receiving postoperative care and awaiting enterostomy closure: to be assessed for eligibility: n = 201 to be assigned to the study: n = 106 to be analysed: n = 106 Duration of intervention per patient of the intervention group: 6 weeks between enterostomy creation and enterostomy closure Follow-up per patient: 3 months, 6 months and 12 months post enterostomy closure, following enterostomy closure (12-month follow-up only applicable for patients that are recruited early enough to complete this follow-up within the 48 month of overall study duration).

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Population The Population shall be defined as all Paid Claims during the 12-month period covered by the Claims Review.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Criminal History Category With regard to determining defendant’s criminal history points and criminal history category, based on the facts now known to the government, defendant’s criminal history points equal zero and defendant’s criminal history category is I.

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!