Software Change Management Sample Clauses

Software Change Management. 5.2.2. Server Management 5.2.3. Security Device Management 5.2.4. Level 2 SupportService support through the SITA Remote Management Centre. 5.2.5. Level 3 Support – Service support through the SITA Development and Certification team.
AutoNDA by SimpleDocs
Software Change Management. SITA will provide a Software Change management service, to advise Customer of Changes proposed by XXXX and to ensure appropriate action to support Change Requests submitted by Customer.
Software Change Management. All software application change requests can be submitted by Customer to DocXellent via phone or email. This will invoke the DocXellent Software Change Management Procedure, SOP-SDLC- CHANGE-MGNT in the Customer Audit Portal. As noted, in 1.4.3, Customer change requests are classified as (PCR’s). All PCRs are reviewed by the Change Control Board (CCB) for approval and release version assignment. The PCR prioritization and approval process are based on a set of four criteria, 1) value to the customer as defined by the source subject matter expert, 2) value to sales objectives as defined by the Sales department, 3) alignment with system purpose/valid use scenarios as defined by Customer Relations and 4) complexity to implement as defined by Development. If the PCR is approved, the CCB shall slot the item for release in an upcoming Theme Pack, if the PCR is not approved, then the item shall be closed. In either instance, the Customer will be notified of the CCB decision.
Software Change Management. Software changes that are made to the Spotify systems pass through a set of tests before being deployed to the production environment. These tests ensures the stability and functionality of the software. Commonly, only a small part of the servers in the production environment **** to allow for quick rollback in the case of an emergency. If the update requires **** all connected users are migrated to a different server to ensure that no users are negatively affected by the upgrade. The client application is protected from tampering ****. The desktop and mobile versions of the client application will automatically download, verify and install updates when deployed by Spotify. Access to the **** within the company. 7 Content ingestion, storage and packaging
Software Change Management 

Related to Software Change Management

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Programme Management The Government will establish a programme management office and the Council will be able to access funding support to participate in the reform process. The Government will provide further guidance on the approach to programme support, central and regional support functions and activities and criteria for determining eligibility for funding support. This guidance will also include the specifics of any information required to progress the reform that may be related to asset quality, asset value, costs, and funding arrangements.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopts or introduces for the Employer, management and municipal staff of the Employer.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Traffic Management The Customer will not utilize the Services in a manner which, in the view of the Centre Operator, significantly distorts traffic balance on the Centre Operator’s circuits which are shared with other users. If, in the reasonable view of the Centre Operator, the Customer’s traffic patterns cause or may cause such distortion, the Customer should have a dedicated circuit capability. If the Customer declines to do so then the Centre Operator may suspend the Services while the matter is being resolved. If there is no resolution within 5 business days then either party may terminate the Agreement.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

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