Operating Model. 3.15 In respect of each DivestCo Transferred Entity that is subject to a Reverse Carve-Out and that is identified in accordance with the same process as set out in Clause 3.9 as transacting directly with distributors, customers, suppliers or the principal of the DivestCo Group, in connection with the RemainCo Business (if any), the parties agree:
Operating Model. 65.1 The parties agree that a new Operating Model will be developed using genuine consultation by 29 February 2020 for the Darwin and Xxxxx Springs Correctional Centres, and the Barkly and Datjala Work Camps.
Operating Model. This Exhibit contains specific functional requirements that all Service Component Providers (SCPs) (including the Service Provider) must meet in order to perform the requested Services and responsibilities defined in Exhibits 2.8.1, 2.8.2, and 2.8.3. Service Providers must integrate with DIR’s Multi-sourcing Services Integrator (MSI). DIR contracts with multiple SCPs to deliver shared technology services to DIR Customers. Those services are integrated into a common service delivery model by DIR’s MSI. The MSI provides the systems, processes and service delivery oversight necessary to ensure consistent, quality service delivery. Figure 1 below depicts the relationships between SCPs and the MSI. Figure 1
Operating Model. All services are delivered to the Customer in adherence with the governance defined in Schedule 12 (Governance and Service Management). The day-to-day operations for each service are defined within each Schedule 2 Annex. The Service Provider will provide a Programme Management Office (PMO) function to deliver reporting and to manage cross-service responsibilities. The Service Provider will further use the Change Management capability within the Change Management function, as defined in Schedule 2 Annex 5 (Change Management Services) to assist with capacity, project and change management across the services. The services will be delivered from the Service Provider’s delivery location in India and from the Customer’s location in London, UK. The Service Provider will establish an ITIL-based tiered support model, including L1.5, L2 and L3 services. For L1.5 support, please refer to Schedule 2 Annex 3 (Operations and Service Delivery Services) that sets forth the roles and responsibilities of the Service Desk. The Service Provider will establish an integrated L1.5 Service Desk for all IT Incidents and Service Requests, including the Network, Infrastructure, Security and Application related Incidents and Service Requests. This team will attempt resolution based on documented procedures / Standard Operating Procedures being agreed upon with the Customer on an ongoing basis. If the L1.5 team is unable to resolve the Incident, the Incident will be escalated to the Xxxxx 0 support team. Level 2 Support, will be responsible for providing resolution to escalated issues in addition to providing routine system administration activities. Level 3 Support, will be responsible for providing Problem Management and root cause analysis activities and interfacing with the Customer retained team. The Level 3 support team will also support the resolution team for any escalated issues. The L1.5, Level 2 and Level 3 support teams will coordinate with any 3rd party vendors for issue resolution as appropriate.
Operating Model. The Service Provider shall establish an ITIL based tiered support model including L1.5, L2 and L3 services aligned to the operating model as set out in Schedule 2 Annex 1 (Common Services. The Service provider shall establish an integrated L1.5 Service Desk for the Network, Infrastructure and Application related Incidents and Service Requests. This team will attempt resolution based on documented procedures / Standard Operating Procedures being agreed upon with the Customer on an ongoing basis. If the L1.5 team is unable to resolve the incident, the incident will be escalated to the Xxxxx 0 support team. The L1.5, Level 2 and Level 3 support teams will coordinate with any 3rd party vendors for issue resolution as appropriate.
Operating Model. Schedule 2 Annex 1 (Common Services) sets out the definition of the Common Operating Model. • The Services shall be delivered from the Service Provider’s delivery location in India with Information Security Officer based in the Customer’s London office. • The Service provider shall establish an ITIL based Tiered Support Model including L1.5, L2 and L3 services. • Level 1.5 support, shall be responsible for providing resolution based on documented procedures / Standard Operating Procedures being agreed upon with the Customer on an ongoing basis. If the L1.5 team is unable to resolve the incident, the incident will be assigned to the corresponding security assignment group. Tickets re-routed to the security assignment group will be forwarded to the Service Provider ticketing tool for ticket resolution. • Level 2 Security support, shall be responsible for providing resolution to escalated issues in addition to providing routine system administration activities. • Level 3 Security support, shall be responsible for providing engineering activities and interfacing with the Customer retained Architecture team. The Level 3 support team will also support the resolution team for any escalated issues.
Operating Model. In case of any discrepancies between the above documents, the text of this Agreement document shall always prevail over any of the Appendices (with the exception of Appendix 4) or the Schedules thereto. The terms and conditions of Appendix 4 hereto shall alter the contents of this Agreement only to the extent expressly stated in Appendix 4. All other conditions of this Agreement shall remain unchanged. The Appendices shall apply in the order set forth above.
Operating Model. The Operating Model is the overarching document that describes what the Collaborative is, its purpose and how it works. Along with the Collaborative's Ambitions document the Operating Model has two core functions/purposes to provide:
Operating Model. Both INFOCUS and Flextronics will appoint one or more program managers for its respective project activities to act as commercial and technical liaison with the other party. Each party will assign appropriate personnel, as it shall deem necessary in its sole discretion; provided, however, that each party shall use its reasonable commercial efforts to perform the activities for which, by the terms of this Agreement, is responsible. Both parties shall provide manufacturing, test and quality engineering support, if needed, at each others facilities as mutually agreed upon. Flextronics agrees to work with INFOCUS to further develop the shared operating model in Exhibit E that includes cross-company processes in the following functional areas: project management, supply chain planning, procurement, order management, manufacturing operations, logistics, quality control, documentation and ECO control, service operations and information technology (IT).
Operating Model. 3.2.1.3.1. FT will provide usage forecasts based on the number of installed and disconnected connections, with the first forecast being provided before the Effective Date, to enable Equant to dimension the MLN Equipment and assess the workload. FT undertakes to provide forecasts on a regular basis to be defined in the Agreement for Switched Voice Services.
