Application Maintenance and Support Sample Clauses

Application Maintenance and Support. Definition: Application Maintenance and Support includes the skills and requirements for supporting application systems, including troubleshooting, modifying, maintaining and enhancing legacy systems. Application Maintenance and Support also applies to applications running in a production environment.
Sample 1Sample 2Sample 3See All (28)
AutoNDA by SimpleDocs
Application Maintenance and Support. Application Maintenance and Support includes troubleshooting, modifying, maintaining, improving security, and enhancing legacy systems and applications which may be running in a production environment. Examples may include: • Providing ongoing maintenance and support services for our existing applications. • Conducting regular monitoring and enhancements to ensure optimal performance. • Offering timely response and resolution to reported issues and incidents. • Performing routine updates, bug fixes, and troubleshooting. • Ensuring the availability, responsiveness, performance, and security of applications. • Applying industry best practices and proactive measures to minimize downtime.
Sample 1Sample 2Sample 3See All (27)
Application Maintenance and Support. CGS will use a firm-fixed-price fee structure for all projects under the Application Maintenance and Support category. The firm-fixed price will be based on an agreed-upon scope of work and the fully burdened hourly rates found in the table below. The firm-fixed price will be broken down by task and deliverables for each task. The Texas Share member will be invoiced monthly based on the percentage completed for each task.
Sample 1
Application Maintenance and Support. The purpose for Application Maintenance processes is to support and maintain information systems and preserve their quality, integrity, and availability following implementation. To meet organization performance criteria and strategic goals, maintenance operations are managed through a tracking and approval process. The Application Maintenance processes can be viewed as a recurring cycle, characterized by specific activities that produce the output required to deliver maintenance Services. When problems are detected, maintenance requests are submitted, reviewed and approved or cancelled. ODOT IS uses an automated Request for Work (“RFW”) document and process to control maintenance and other user Help Desk type requests. The RFW document and process contains details of the need, specifications, requirements, and desired outcomes. Actual project work tasks may include but are not limited to some or all of the following areas: • Evaluate a user submitted RFW and provide feedback to ODOT. (Appropriate RFW's are provided electronically to the Contractor based on triggers and other automated processes.) • Adjustments to non-compliant system components to meet the current specifications of an information system in production, without applying changes to data definitions or enhancements to functionality. • Ensure tight controls are maintained to minimize corruption for continued and efficient operation. • Performing backup and recovery. Move selected data. • Review coding specifications for tables. Setup new database tables. • A change to an information system that is independent of system functionality and has minimal or no user-level impact. • Providing, limited, additional capability to an information system. This capability may encompass new or modified functionality, and address work process improvements or regulation aspects. • Designing, guiding and conducting data profiling or data cleansing activities. • Perform application/system maintenance based on an ODOT approved user Request for Work and based on the ODOT-Approved Methodology. • Update existing application/system documentation as a result of the maintenance performed. • Providing technical support for users internal and external to ODOT. • Troubleshooting of user access, file issues and system functionality errors that occur in the production environment, including root cause analysis, communicating with user base about incident status and recommending solutions to fix the issues. • Support testing ...
Sample 1

Related to Application Maintenance and Support

  • Maintenance and Support NCR Voyix is solely responsible for providing any maintenance and support services with respect to the Software as specified in the Agreement, or as required under applicable law. The parties acknowledge that Apple has no obligation whatsoever to furnish any maintenance and support services with respect to the Software.

  • Maintenance and Support Services 3.1 Subject to Client’s timely payment of applicable Maintenance and Support fees, MRI will provide to Client the Maintenance and Support services for the Maintenance and Support plan indicated in the Order Document during the specified period. All licenses in Client’s possession must be supported under the same Maintenance and Support plan. 3.2 Updates are provided if and when available and MRI shall notify Client of the availability of such Updates solely by posting such Updates at MRI’s client support portal. MRI is under no obligation to develop any future programs or functionality. MRI is under no obligation to provide Maintenance and Support with respect to: (i) Software that has been altered or modified by anyone other than MRI or its licensors; (ii) a release for which Maintenance and Support has been discontinued; (iii) Software used other than in accordance with the Documentation or other than on a XXX; (iv) discrepancies that do not significantly impair or affect the operation of the Software; (v) any systems or programs not supplied by MRI; or (vi) Configurations. 3.3 Subject to timely payment of the applicable fees, Maintenance and Support is provided for all Software, unless otherwise noted in the Order Document, provided however that with respect to Third Party Software, MRI’s obligation is limited to using commercially reasonable endeavours to obtain Maintenance and Support from the third party owner of such Software. 3.4 Maintenance and Support starts on the Effective Date and continues through the expiration of the initial term set forth in the Order Document (“Initial Term”). Following the end of the Initial Term, Maintenance and Support and the license grant under Section 2.1 shall automatically renew for the same length as the Initial Term (each renewal a “Renewal Term”), unless either Party gives written notice at least sixty (60) calendar days prior to the end of the Initial Term or any Renewal Term, as applicable, of its intention to not renew Maintenance and Support and the license grant. The pricing for the first twelve (12) months of any Renewal Term shall be provided in writing by MRI no less than ninety (90) days prior to the end of the Initial Term or any Renewal Term. Notice to not renew the Initial Term or any Renewal Term shall be given in accordance with section 10.8 of the Master Agreement and shall be deemed given upon delivery to the non-cancelling Party. For purposes of the pricing notice in this Section only, email or first-class mail will suffice. The Initial Term and Renewal Terms are collectively referred to as the “Term”. 3.5 In the event that Client’s Maintenance and Support is not renewed and is later reinstated, a reinstatement fee shall be assessed equal to 120% of the aggregate Maintenance and Support fee that would have been payable during the period of lapse. In order to reinstate Maintenance and Support, Client must Upgrade its Software to the most current release and pay for any applicable Upgrade fees. 3.6 If ordered by Client, Maintenance and Support must be ordered for all Software and all associated License Metrics licensed by Client and its Affiliates. Client may not purchase or renew Maintenance and Support for less than all of the Software licensed by Client. 3.7 Fees for Maintenance and Support do not include implementation, training and other Professional Services, such as project management, conversion, report writing, and external systems interface development. 3.8 It is Client’s responsibility to ensure that all appropriate users receive initial training services sufficient to enable Client to effectively use the Software. Failure to do so could result in additional Maintenance and Support fees if service requests are deemed excessive as a result of insufficient training, at MRI’s discretion. 3.9 The System will need to be installed on Client’s servers and technology infrastructure. If utilizing Professional Services or Maintenance and Support in the installation of the System, Client shall ensure that MRI’s assigned technical personnel are able to access the System remotely. Client shall be responsible for providing access through any security measures it deems necessary. MRI alone shall decide whether access to the System is sufficient for Maintenance and Support purposes. Certain functionality of the System may require connections to or interaction with MRI after such System is running on Client’s infrastructure, and Client agrees to permit and facilitate such connections

  • System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

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

  • Software Maintenance Subrecipient shall apply security patches and upgrades in a timely manner and keep virus software up-to-date on all systems on which State data may be stored or accessed.

  • Maintenance Support State Street shall use commercially reasonable efforts to correct system functions that do not work according to the System Product Description as set forth on Attachment A in priority order in the next scheduled delivery release or otherwise as soon as is practicable.

  • Project Maintenance The Local Government shall be responsible for maintenance of locally owned roads and locally owned facilities after completion of the work. The State shall be responsible for maintenance of the state highway system after completion of the work if the work was on the state highway system, unless otherwise provided for in existing maintenance agreements with the Local Government.

  • Account Maintenance Trade Allocations Trade Reporting; (Futures) Daily Trade Checkout Daily Statement Reconciliation

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