System Testing and Change Management Requirements Sample Clauses

System Testing and Change Management Requirements. 17.6.1 The Contractor shall absorb the cost of routine maintenance, inclusive of defect correction, System changes required to effect changes in Puerto Rico and federal statute and regulations, and production control activities, of all Systems within its Span of control. 17.6.2 The Contractor shall respond to ASES reports of System problems not resulting in System Unavailability according to the following timeframes: 17.6.2.1 Within five (5) Calendar Days of receipt the Contractor shall respond in writing to notices of system problems. 17.6.2.2 Within fifteen (15) Calendar Days, the correction will be made or a Requirements Analysis and Specifications document will be due. 17.6.3 The Contractor shall correct the deficiency by an effective date to be determined by ASES. 17.6.4 Contractor systems will have a system-inherent mechanism for recording any change to a software module or subsystem. 17.6.5 The Contractor shall put in place procedures and measures for safeguarding ASES from unauthorized modifications to Contractor Systems. 17.6.6 Unless otherwise agreed to in advance by ASES, scheduled System Unavailability to perform System maintenance, repair and/or upgrade activities to Contractor’s CCE systems shall take place between 11 p.m. on a Saturday and 6 a.m. on the following Sunday. 17.6.7 The Contractor shall work with ASES pertaining to any testing initiative as required by ASES. 17.6.8 The Contractor shall provide sufficient system access to allow verification of system functionality, availability and performance by ASES during the times required by ASES prior to the Implementation Date and as subsequently required during the term of the Contract.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
System Testing and Change Management Requirements. 1. Notification and Discussion of Potential System Changes
Sample 1Sample 2Sample 3
System Testing and Change Management Requirements. 1. Notification and Discussion of Potential System Changes. The Health Plan shall notify the applicable Agency staff person of the following changes to Systems within its Span of Control within at least ninety (90) Calendar Days of the projected date of the change; if so directed by the Agency, the Health Plan shall discuss the proposed change with the applicable Agency staff: (1) software release updates of core transaction Systems: claims processing, eligibility and Enrollment processing, service authorization management, Provider enrollment and data management; (2) conversions of core transaction management Systems.
Sample 1Sample 2
System Testing and Change Management Requirements. 17.6.1 The Contractor shall absorb the cost of routine maintenance, inclusive of defect correction, System changes required to effect changes in Puerto Rico and Federal statute and regulations, and production control activities, of all Systems within its Span of Control. 17.6.2 The Contractor shall respond to ASES reports of System problems not resulting in System Unavailability according to the following timeframes:
Sample 1
System Testing and Change Management Requirements. 2.23.9.1 The CONTRACTOR shall notify the applicable TENNCARE staff person of the following changes to Systems within its span of control within at least ninety (90) calendar days of the projected date of the change. 2.23.9.1.1 Major changes, upgrades, modifications or updates to application or operating software associated with the following core production Systems: claims processing, eligibility and enrollment processing, service authorization management, provider enrollment and data management, and encounter data management; and
Sample 1

Related to System Testing and Change Management Requirements

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Quality Service Standards Price Services and the Fund may from time to time agree to certain quality service standards, as well as incentives and penalties with respect to Price Services’ Services hereunder.

  • Listing and Maintenance Requirements The Common Stock is registered pursuant to Section 12(b) or 12(g) of the Exchange Act, and the Company has taken no action designed to, or which to its knowledge is likely to have the effect of, terminating the registration of the Common Stock under the Exchange Act nor has the Company received any notification that the Commission is contemplating terminating such registration. The Company has not, in the 12 months preceding the date hereof, received notice from any Trading Market on which the Common Stock is or has been listed or quoted to the effect that the Company is not in compliance with the listing or maintenance requirements of such Trading Market. The Company is, and has no reason to believe that it will not in the foreseeable future continue to be, in compliance with all such listing and maintenance requirements.

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

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

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