Operating Model. 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. 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. 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.
65.2 The parties agree to genuinely consult with the Union on the new final Operating Model.
65.3 The parties agree to work collaboratively with the Union on the best positions for the new staffing model(s) to ensure successful implementation by no later than 29 February 2020.
65.4 The parties will work cooperatively to implement the new Operating Model within 6 months of it being funded by Cabinet.
65.5 The parties acknowledge the need for regular and ongoing monitoring, assessment and review of the Operating Model.
65.6 Once implemented, variations to the Operating Model will be through agreement with the union, except in the circumstances set out in clauses 65.7 and 65.8.
65.7 Where variations to the Operating Model are required in response to a Government direction or changes in Government policy priorities, the variations will be managed in accordance with consultation provisions set out in clause 65.9.
65.8 Where an incident or event threatens the security and good order of a correctional precinct/work camp and/or staff or offenders, the CEO may implement a temporary variation to the Operating Model with consultation that is practicable in the circumstances, and that variation may be maintained for the life of the incident or event.
Operating Model. Each body prepares their control strategy, identifying their tactical priorities and intelligence gathering requirements. Such strategies develop from the strategic assessments. They are independently prepared, likely to be complimentary and will be shared to promote interoperability. Both the FSA and FSS will work to jointly lead on Operation OPSON (a Europol and Interpol joint operation targeting fake and substandard food and beverages) and this offers a model for cross border collaboration between the two units within the UK.
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. 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. The Shareholders agree that the Company will have its own employees and management reporting to the Board and/or various non-executive committees that will provide interface between the Board, the management team and the Shareholders and will provide advice to the Board, as needed. Daily operations will be carried out by the management of the Company. Day to day operations will be carried out by management of the Company. The Board may establish certain standing committees; however no such committee will have independent decision-making authority, but each will provide guidance to the Board.
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.
3.2.1.3.2. Equant shall identify a single point of contact, who will act as the carrier business support coordinator for the implementation of FT orders.
