Shared Roadway. Seller will construct a paved roadway on the Common Element Road as shown on the Condominium Map for access within the Project. The roadway will be maintained as a common expense of the Association.
Shared Roadway Sample Clauses
Related to Shared Roadway
Shared roles The Parties will meet the requirements of Schedule E, Clause 26 of the IGA FFR, by ensuring that prior agreement is reached on the nature and content of any events, announcements, promotional material or publicity relating to activities under this Agreement, and that the roles of both Parties will be acknowledged and recognised appropriately.
Shared Services CUPE agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis recognizing the value of benefits to the members.
Union Access The Union shall have reasonable access to all work locations to verify that the terms and conditions of this Agreement are being carried out and for the purpose of conferring with employees, provided that access shall be subject to such rules and regulations immediately below, as well as to such rules and regulations as may be agreed to by the department and the union. Union access to work locations will not disrupt or interfere with a department’s mission and services or involve any political activities.
Data Services In lieu of any other rates or discounts, the Customer will receive a discount equal to 20% for the following Data Services: Access: Standard VBS3Guide local loop charges for DS-0, DS-1 and DS-3 Access Service.
Allocation of Resources Whenever a disaster causes Vendor to allocate limited resources between or among Vendor's customers, vendor will not provide priority over Prudential to any other customers of Vendor. In addition, in no event will Vendor re-deploy or reassign any vendor Key Employee (as identified and defined in an applicable Engagement Schedule) or any Affected Employee (as identified and defined in an applicable Engagement Schdule) to any other Vendor account in the event of a disaster.
Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:
Separate Central and Local Terms The collective agreement shall consist of two parts. Part “A” shall comprise those terms which are central terms. Part “B” shall comprise those terms which are local terms.
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
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.
