Model for transition Clause Samples

Model for transition. 1935 Transition will be done in the form of a transition project the aim of which is to establish the 1936 FMO. The Contractor will be responsible for the transition project (including the interaction with 1937 the Incumbent(s)) and submit an initial plan as part of their offer. In such offer the Contractor 1938 shall specify requirements for exit tasks on the Incumbent(s). To this effect the Contractor is 1939 expected to carefully analyse the CMO Annexes (ref. section 3.1 Current Mode of Operations 1940 (CMO)). 1941 As soon the FWC is signed ▇▇▇▇ will engage the Contractor in the preparation of: 1942 1. Governance Contract, a refinement of the governance model specified in section 9 1943 Governance 1944 2. Transition project Contract, a refinement of the plan provided in the offer 1945 3. Exit agreement with the Incumbent, based on the requirements expressed by the 1946 Contractor and their compatibility with the contractual obligations of the Incumbent(s). 1947 Regular Service Contract(s) will follow. 1948 ECHA envisages a full transition to FMO in nine months after signature of the FWC at 1949 least the following milestones in the transition project: 1950  M1 Readiness of the cloud infrastructure provided by the Contractor for migration of 1951 services; no later than six months after the signature of the FWC; 1952  M2 Migration of services complete; no later than three months after M1 1953  M3 services ready in the FMO (and complying with the required requests table, ref. 6.3.9 1954 Required Requests); no later than three months after M1; 1955  M4 SMP ready for use; no later than three months after M1. 1956 Readiness include successful acceptance testing and successful Disaster Recovery testing when 1957 applicable. The numbering of the milestones does not mean sequencing. However, the FMO is 1958 considered “established” on achievement of M3 and M4.

Model for transition.  Elements addressing 8.