Relationship Management Structure Sample Clauses

Relationship Management Structure. Within thirty (30) days after the Effective Date, Health Net and Supplier will identify the titles of the initial members of the committees set forth below and will agree upon a process for replacement of the committee members during the Term.
Sample 1Sample 2
AutoNDA by SimpleDocs
Relationship Management Structure. Within thirty (30) days after the Effective Date, Health Net and Supplier will identify the titles of the initial members of the committees set forth below and will agree upon a process for replacement of the committee members during the Term. (a) Joint Steering Committee (i) Health Net and Supplier will jointly create a committee consisting of three management employees from Health Net and its Affiliates and three management employees from Supplier and its Affiliates who will focus on Health Net’s and Supplier’s long-term strategic plans as they relate to the Services (“Joint Steering Committee”). (ii) The Joint Steering Committee will: (A) meet at least semi-annually to discuss the evolving business agenda of Health Net and Supplier as it relates to the Services; (B) facilitate the goals of the Agreement; (C) review performance against goals and revise such goals, as appropriate; (D) approve and/or propose Changes to the Agreement, as appropriate; (E) identify major Health Net organization changes (i.e., people, processes, functions) or proposed changes affecting the Agreement; (F) review industry / business trends and the impact of technology on the Services; (G) evaluate Supplier industry initiatives for potential applicability to the Services; (H) review operating and strategic plans prepared by the Project Executives; (I) upon Health Net’s or Supplier’s request, assist in resolving issues arising under this Agreement; and (J) participate in the dispute resolution process set forth in Section 26 of the General Terms and Conditions, as necessary.
Sample 1
Relationship Management Structure. (a) On the Effective Date, the Parties will each identify an Executive Sponsor (who will focus on Triple-S’ and Supplier’s long-term strategic relationship and the mission, vision and innovation as they relate to the Services) and Delivery Executives (the Triple-S Program Manager a described in Section 7.1 of the General Terms and Conditions and the Supplier Account Executive as described in Section 6.3(e) of the General Terms and Conditions). (who will have responsibility for the execution of Contract Governance and who will be responsible for the day-to-day operations and delivery of the Services). These positions will function as the initial Relationship Management Structure until the long term Relationship Management Structure is implemented as described below. During such period, each Party will cause its representatives to participate in contract governance related discussions and work together to establish agendas and agreed upon tasks. These roles will continue within the Relationship Management Structure. (b) Within thirty (30) days after the Effective Date, the Parties will identify the titles of (i) the initial members of the committees set forth below in this Section 2.3 (Relationship Management Structure) and (ii) the initial representatives who will attend the meetings identified in Section 2.4 (Meetings) below, and will agree upon a process for replacement of committee members and meeting attendees, as applicable, during the Term.
Sample 1

Related to Relationship Management Structure

  • Relationship Management LAUSD expects Contractors and their Representatives to ensure that their business dealings with and/or on behalf of LAUSD are conducted in a manner that is above reproach.

  • Relationship Managers The Participant Relationship Manager and the Reclaim Fund Relationship Manager at the date of this agreement for the purposes of clause 27 of Part B of this agreement are as follows: (a) the Participant Relationship Manager: Xxxxxx Xxxxxx; and (b) the Reclaim Fund Relationship Manager: Xxxxxx Xxxxx.

  • Management Structure Describe the overall management approach toward planning and implementing the contract. Include an organization chart for the management of the contract, if awarded.

  • Account Management 15.1 The Contractor is required to provide a dedicated Strategic Account Manager who will be the main point of contact for the Authority. The Strategic Account Manager will:  Attend quarterly, or as otherwise agreed, review meetings with the Authority, in person at the Authority’s premises or other locations as determined by the Authority  Attend regular catch-up meetings with the Authority, in person or by telephone/videoconference  Resolve any on-going operational issues which have not been resolved by the Contractor or Account Manager(s) and therefore require escalation  Ensure that the costs involved in delivering the Framework are as low as possible, whilst always meeting the required standards of service and quality. 15.2 The Contractor is also required to provide a dedicated Account Manager for every Framework Public Body using the Framework, if required by the Framework Public Body. The service to be provided will be agreed with each Framework Public Body and may include:  regular review meetings, which may be in person at the Framework Public Bodies’ premises, by video-conference, webinar or telephone  Regular catch-up meetings/telephone calls to discuss current and on-going issues  Work with the Framework Public Bodies Contract Manager to resolve any on-going operational issues  Work with the Framework Public Body ’s Contract Manager to pro-actively introduce initiatives to:  Create efficiencies in processes  Improve the environmental performance of the contract. 15.3 It is expected that end users will contact the Contractor in the first instance to resolve any operational issues. The Account Manager will act as a point of escalation to be contacted either by end users or by the Framework Public Body’s Contract Manager should there be issues that the Contractor needs to resolve. 15.4 Further details of the roles and responsibilities of the Contractor, Authority and Framework Public Bodies are provided in Schedule 4 – Management Arrangements

  • Agreement Structure This Agreement includes Part 1 - General Terms, Part 2 - Country-unique Terms (if any), the LI, and the XxX and is the complete agreement between Licensee and Lenovo regarding the use of the Program. It replaces any prior oral or written communications between Licensee and Lenovo concerning Licensee’s use of the Program. The terms of Part 2 may replace or modify those of Part 1. To the extent of any conflict, the LI prevails over both Parts.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • 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:

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!