Multi-layer Coordination Sample Clauses

Multi-layer Coordination. ‌ In RINA, the situation is very different. Using a common API (the IPC API) and building immutable infrastructure used by each and every IPCP means that there are no longer an technological differences among different layers in the network. There are also no differences between vertical elements in a component, everything is an IPC process (IPCP). Next, the concept of separation of mechanism and policy, and the definition of policies for all aspects of an IPCP (and thus inter-process communication), makes all available policies ex- plicit. There is no need anymore for separate management model interface definitions, everything management requires is already defined by the architecture. Next, the concept of a DIF as a layer, and not a stack, with autonomic functions for layer management (as part of every IPCP) and with an explicit definition of the scope of the layer (the scope of the DIF, realised by its policies), provides for a very new concept with regard to multi-layer management. Last but not least, the RIB in the IPCPs (and thus in the DIF) provides for the required information base for all of the above. The RIB maintains all shared state of all IPCPs in a DIF. The defined processes also realise an automatic update of this shared state amongst all IPCPs in a DIF. This means that changes to a DIF’s configuration will propagate from one IPCP to another until the entire DIF is reconfigured.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Multi-layer Coordination

  • Project Coordination The Engineer shall coordinate all subconsultant activity to include quality and consistency of deliverables and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Order Coordination and Order Coordination-Time Specific 2.1.9.1 “Order Coordination” (OC) allows BellSouth and Choice Telephone Company to coordinate the installation of the SL2 Loops, Unbundled Digital Loops (UDL) and other Loops where OC may be purchased as an option, to Choice Telephone Company’s facilities to limit end user service outage. OC is available when the Loop is provisioned over an existing circuit that is currently providing service to the end user. OC for physical conversions will be scheduled at BellSouth’s discretion during normal working hours on the committed due date. OC shall be provided in accordance with the chart set forth below.

  • Project Management and Coordination The Engineer shall coordinate all subconsultant activity to include quality of and consistency of work and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Utility Coordination Identify all potential utility conflicts and provide preliminary office check plans showing the problem locations, posted to the City’s FTP site. Plans will clearly identify specific utility company facilities by color and by name (i.e. not just “gas” or “fiber optic”). ENGINEER shall include a conflict list for each utility, also posted to the FTP site. ENGINEER shall meet with utility company representatives to review plans and utility verification forms (Attachment No. 3 to Exhibit “A”) at each milestone date and as directed by the CITY and as determined necessary by the ENGINEER. This in- formation will be compiled into a summary report (Attachment No. 4 to Exhibit “A” also available on the City’s FTP site) maintained and updated by ENGINEER as necessary to present a cohesive and reflective status of utilities, and provided to the City as necessary. ENGINEER shall maintain involvement with utility companies until all conflicts have been resolved (not just identified). When appropriate, the City Engineer will approve the identification on plans of conflicts to be resolved during construction. ENGINEER shall meet with involved utility company/ies and project contractor to resolve any conflicts with utilities that occur during construction.

  • Project Coordinator 3. Within 14 days of the effective date of this Consent Agreement, DTSC and Respondent shall each designate a Project Coordinator and shall notify each other in writing of the Project Coordinator selected. Each Project Coordinator shall be responsible for overseeing the implementation of this Consent Agreement and for designating a person to act in his/her absence. All communications between Respondent and DTSC, and all documents, report approvals, and other correspondence concerning the activities performed pursuant to this Consent Agreement shall be directed through the Project Coordinators. Each party may change its Project Coordinator with at least seven days prior written notice. WORK TO BE PERFORMED

  • Cooperation and Coordination The Parties acknowledge and agree that it is their mutual objective and intent to minimize, to the extent feasible and legal, taxes payable with respect to their collaborative efforts under this Agreement and that they shall use all commercially reasonable efforts to cooperate and coordinate with each other to achieve such objective.

  • Care Coordination MCOs must ensure care coordination is provided to Members with a substance use disorder. MCOs must work with providers, facilities, and Members to coordinate care for Members with a substance use disorder and to ensure Members have access to the full continuum of Covered Services (including without limitation assessment, detoxification, residential treatment, outpatient services, and medication therapy) as Medically Necessary and appropriate. MCOs must also coordinate services with the DSHS, DFPS, and their designees for Members requiring Non-Capitated Services. Non-Capitated Services includes, without limitation, services that are not available for coverage under the Contract, State Plan or Waiver that are available under the Federal Substance Abuse and Prevention and Treatment block grant when provided by a DSHS-funded provider or covered by the DFPS under direct contract with a treatment provider. MCOs must work with DSHS, DFPS, and providers to ensure payment for Covered Services is available to Out-of-Network Providers who also provide related Non-capitated Services when the Covered Services are not available through Network Providers.

  • Coordination The Parties shall confer regularly to coordinate the planning, scheduling and performance of preventive and corrective maintenance on the Large Generating Facility and the Interconnection Facilities.

  • Scheduling Coordinator Buyer shall act as the Scheduling Coordinator for the Project. In that regard, Buyer and Seller shall agree to the following:

  • Coordination of Work Licensee shall be responsible for coordination of its Equipment installation work to avoid any interference with existing utilities, substructures, facilities and/or SFMTA transit operations. Licensee shall be the City's point of contact for all Equipment installation and except in case of emergency, all communications concerning Equipment installation shall be through Licensee's field representatives.

Time is Money Join Law Insider Premium to draft better contracts faster.