Technical Change Management Clause Samples

Technical Change Management. NETCARE performs a state of the art Technical Change management with the aim to ensure the adherence to internal and external guidelines regarding the operation of Systems and applications. Thereby the Technical Change Management enables NETCARE to maintain a validated status of the Systems and applications and ensures the consistence of FME requirements and available functionalities. NETCARE’s Technical Change Management has additionally the objectives to reduce the number of Incidents and to increase the stability of the IT environment. In general the Technical Change management process is triggered by Incidents, Problems, requests, ideas or during Projects. The initiation of the Technical Change management process is always a Request for Change (RfC) which runs through a two-tier procedure based on permission and approval, involving customers’ test contribution and explicit customer approvals. The permission of RFCs requires a description of the change, its organizational and technical classification and the agreement of actions and documentation requirements necessary for an RfC-approval and following go-live. The RfC-approval, which is the second step in the two-tier procedure, ensures the adherence to the agreed actions and documentation requirements before a go-live can take place. Thereby NETCARE’s Technical Change management process ensures that legal requirements are fulfilled and that changes affecting configuration items within the productive environment are traceable, documented, coordinated and planned.

Technical Change Management. In performing its duties for the Project, Contractor shall comply with County's requirements with respect to technical and operational change management. It is understood by Contractor that changing County's computers, in particular its mainframes, requires advance notice and compliance with established County procedures.