consistency and compatibility Sample Clauses

consistency and compatibility. To promote a cohesive plan of development, buildings shall have architectural features that offer common themes and styles while recognizing local character. Acceptable examples include Italianate Revival, Mediterranean, Neoclassical, and Art Deco Mission. Generally, the perimeter zone is envisioned as having more design flexibility than the core zone and can accommodate corporate headquarters that develop as a campus vs. a street front development due to image or security reasons.
Sample 1
AutoNDA by SimpleDocs
consistency and compatibility. In order to get a better understanding of when the properties consistency [6,7,20] and compatibility [6, 7, 20] are relevant, a scenario is examined where a contract is used to out source the development of an element E with an interface X. Specifically, the scenario can be described in three phases: 1) a contract (A, G) and an interface specification X are handed from the client to a supplier; 2) an element E = (X, B) is delivered to the client that meets the condition (i) of Corollary 1; and 3) the client integrates the element E with a set of elements to form an archi- tecture where the environment of E meets the condition (ii) of Corollary 1. As expressed in phases (1-2), the client would expect the supplier to deliver an element that meets the condition (i) of Corollary 1 with respect to the contract C . However, in order for the supplier to be able to meet the demands from the client, the supplier would expect that the contract is such that there actually exists an element that meets the condition (i) of Corollary 1. If such an element exists, then the contract will be referred to as a consistent contract. Furthermore, in order for the client to be able to complete phase (3), at least one architecture containing an element E = (X, B) where the environment of E meets the condition (ii) of Corollary 1, needs to exist. If such an architecture exists, then the contract will be referred to as a compatible contract. Now that the concepts of consistency and compatibility have been introduced in the context of a scenario, formal definitions follow. ^ ^ ^^ Definition 7 (Consistent Contract). A contract (A, G) is consistent with respect to a set of variables X if there exists an element E = (X, B) such that AA ∩ B ⊆ G and AA ∩ G ⊆ B. 1. Definition 7 is also closely related to definitions in [6, 7], but where Definition 7, in contrast to the definitions in [6,7], allows contracts that are not limited to the interface and are further not limited to elements with defined inputs and outputs.
Sample 1

Related to consistency and compatibility

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Consistency The Corporate Taxpayer and the Members agree to report and cause to be reported for all purposes, including federal, state and local Tax purposes and financial reporting purposes, all Tax-related items (including the Basis Adjustments and each Tax Benefit Payment) in a manner consistent with that specified by the Corporate Taxpayer in any Schedule required to be provided by or on behalf of the Corporate Taxpayer under this Agreement unless otherwise required by law. Any dispute as to required Tax or financial reporting shall be subject to Section 7.09.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Quality Management Grantee will: 1. comply with quality management requirements as directed by the System Agency. 2. develop and implement a Quality Management Plan (QMP) that conforms with 25 TAC § 448.504 and make the QMP available to System Agency upon request. The QMP must be developed no later than the end of the first quarter of the Contract term. 3. update and revise the QMP each biennium or sooner, if necessary. Xxxxxxx’s governing body will review and approve the initial QMP, within the first quarter of the Contract term, and each updated and revised QMP thereafter. The QMP must describe Xxxxxxx’s methods to measure, assess, and improve - i. Implementation of evidence-based practices, programs and research-based approaches to service delivery; ii. Client/participant satisfaction with the services provided by Xxxxxxx; iii. Service capacity and access to services; iv. Client/participant continuum of care; and v. Accuracy of data reported to the state. 4. participate in continuous quality improvement (CQI) activities as defined and scheduled by the state including, but not limited to data verification, performing self-reviews; submitting self-review results and supporting documentation for the state’s desk reviews; and participating in the state’s onsite or desk reviews. 5. submit plan of improvement or corrective action plan and supporting documentation as requested by System Agency. 6. participate in and actively pursue CQI activities that support performance and outcomes improvement. 7. respond to consultation recommendations by System Agency, which may include, but are not limited to the following: i. Staff training; ii. Self-monitoring activities guided by System Agency, including use of quality management tools to self-identify compliance issues; and iii. Monitoring of performance reports in the System Agency electronic clinical management system.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, Xxxxx XxXxxxxxxx, Xxxx Xxxxxx, Xxxxx Xxxxxxxx, or a substitute agreed to by the parties, shall at the request of either party:

  • Customer Services Customer Relationship Management (CRM): All aspects of the CRM process, including planning, scheduling, and control activities involved with service delivery. The service components facilitate agencies’ requirements for managing and coordinating customer interactions across multiple communication channels and business lines. Customer Preferences: Customizing customer preferences relative to interface requirements and information delivery mechanisms (e.g., personalization, subscriptions, alerts and notifications).

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