Modifications, Changes and Maintenance Staffing Sample Clauses

Modifications, Changes and Maintenance Staffing. After system implementation, modifications to the software should go through the formal change control process. CHFS is requiring 25,000 hours of Vendor-categorized staff time per contract year to apply towards system enhancements to the MEMS once the system has been fully implemented for the life of the contract. The Vendor should analyze the change request, provide an estimate to CHFS, and receive approval prior to expending any of these hours. Defects cannot be corrected utilizing any of these 25,000 hours. Any hours remaining at the end of a contract year are to be rolled over to the next year. The Commonwealth will not be charged for any configurable items nor will hours go against the pool of change order hours. Examples of configurable items include but are not limited to: adding MCOs, Provider Types, Procedure Codes, TPL Carriers, Rate changes, Notification changes. The Vendor is responsible for full-time staff support comprised of professional systems engineers (programmer/analysts) for all system maintenance change categories. This staff should be in addition to Vendor staff performing routine and general system maintenance activities. The Vendor should identify staff to be assigned to system modification, change and enhancement projects. Additionally, the staff can be assigned to support routine and general maintenance activities with the approval of the CHFS. Other non-programming categorized staff should support routine and general maintenance activities that include: workflow analysis, system testing, documentation updates, and program procedure activities may consist of architects, testers, business analysts, security experts, Database Analysts (DBAs), change management personnel, and/or administrative staff. The mix should be left up to the Vendor, as long as the required level of service is met. Vendor staff responsibilities for all system maintenance activities are prioritized by the CHFS, with input from the Vendor. Within these priorities, the Systems Manager is responsible for directing the work of Vendor staff to ensure that all maintenance and modification efforts proceed in a timely manner as defined in an agreed upon service level agreement. All module and system component functions should be covered by at least one Vendor systems/programming staff with extensive knowledge and experience in the corresponding technical area. Team members should be sufficiently cross- trained to support temporary changes in priorities and/or responsi...
Sample 1
AutoNDA by SimpleDocs

Related to Modifications, Changes and Maintenance Staffing

  • SYSTEM CHANGES AND MAINTENANCE/SUPPORT The Contractor shall give a minimum of 5 business days advance Written notice to the designated Authorized User contact of any upgrades, system changes and Maintenance/support actions that may potentially impact services described in the Authorized User Agreement. Upgrades, system changes, and Maintenance/support actions which are required by system vulnerabilities or emergency situations shall be carried out by the Contractor to protect the system. Authorized Users shall be notified by the Contractor as soon as possible after the change has taken place. Contractor shall provide documentation of upgrades, system changes and Maintenance/support actions upon request from an Authorized User. EXPIRATION, TERMINATION OR SUSPENSION OF SERVICES Return of Data The Contractor shall return Data in a format agreed upon within the Authorized User Agreement or as agreed to with the Authorized User. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. The Contractor must certify all Data has been removed from its system and removed from backups within timeframes established in the Authorized User Agreement or as agreed to with the Authorized User. Suspension of Services During any period of suspension of service, the Authorized User shall have full access to all Data at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing an application programmable interface or other such efficient electronic tools. The Contractor shall not take any action to erase and/or withhold any Authorized User Data, except as directed by the Authorized User. Expiration or Termination of Services Upon expiration or termination of an Authorized User Agreement, the Authorized User shall have full access to all Data for a period of 60 calendar days. Unless noted in the original Authorized User Agreement, this period will be covered at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. During this period, the Contractor shall not take any action to erase and/or withhold any Data, except as directed by the Authorized User. An Authorized User shall have the right to specify a period in excess of 60 calendar days in its RFQ. SECURE DATA DISPOSAL When requested by the Authorized User, the Contractor shall destroy Data in all of its forms, including all back-ups. Data shall be permanently deleted and shall not be recoverable, according ITS Policy S13-003 Sanitization/Secure Disposal or successor and S14-003 Information Security Controls or successor. Certificates of destruction, in a form acceptable to the Authorized User, shall be provided by the Contractor to the Authorized User.

  • Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.

  • Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Construction and Maintenance There are on-going maintenance, renovation and construction projects taking place in and around the residences. The work typically takes place during regular business hours, but may begin earlier or extend into evenings or weekends. On-going construction or renovation projects will continue through midterm and final exam periods. The University will take measures to ensure that prudent construction practices are followed, but there may be noise, dust and temporary interruption of some services. Residents may be required to temporarily or permanently relocate to facilitate construction or renovation to their residence area. There will be no compensation or reduction to your residence fees due to disruption and/or relocation.

  • Changes and Modifications (i) DST shall have the right, at any time, to modify any systems, programs, procedures or facilities used in performing its obligations hereunder; provided that the Fund will be notified as promptly as possible prior to implementation of such modifications and that no such modification or deletion shall materially adversely change or affect the operations and procedures of the Fund in using the TA2000 System hereunder, the Services or the quality thereof, or the reports to be generated by such system and facilities hereunder, unless the Fund is given thirty (30) days’ prior notice to allow the Fund to change its procedures and DST provides the Fund with revised operating procedures and controls.

  • Planned Maintenance (a) Sellers may designate up to twenty (20) Days of Planned Maintenance on Sellers’ Facilities during each Contract Year. Sellers shall be entitled to reduce (including down to zero (0)) its Gas scheduling under Clause 8 and Exhibit 3 for each Day of Planned Maintenance.

  • Operations and Maintenance Pursuant to Section 10.5 of this Agreement, Developer shall pay the reasonable expenses (including overheads) for the operation, maintenance, repair and replacement of Transmission Owner’s Attachment Facilities and incremental operating and maintenance expenses incurred in association with System Upgrade Facilities, if and to the extent provided for under Attachment S. For Transmission Owner’s Attachment Facilities, such expenses are calculated as follows:

  • Operation and Maintenance 17.1 O&M obligations of the Concessionaire

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