Network Architecture Sample Clauses

Network Architecture. Schedule 3.18 of the Seller Disclosure Schedule sets forth a true and complete statement (detailed by Cable System) as of December 31, 2004 (or, in the case of clauses (c) and (f), as of the date hereof), of (a) the approximate number of plant miles (aerial and underground) for each headend located in each Specified Business, (b) the approximate bandwidth capability expressed in MHz of each such headend, (c) the stations and signals carried by each such headend and the channel position of each such signal and station, (d) the approximate number of multiple dwelling units served by such Specified Business, (e) the approximate number of homes passed in such Specified Business as reflected in the system records of Seller or any of its Affiliates, (f) a description of basic and optional or tier services available and the rates charged for each such Specified Business, (g) the bandwidth capacity of each Cable System in such Specified Business for each headend, and (h) the municipalities served by each of the Cable Systems in such Specified Business and the public service numbers of such municipalities.
AutoNDA by SimpleDocs
Network Architecture. Schedule 4.20 of the Buyer Disclosure Schedule sets forth in all material respects a true and complete statement as of December 31, 2004, of (a) the approximate number of plant miles (aerial and underground) for each division of the Parent Business, (b) the approximate bandwidth capability expressed in MHz of each such division of the Parent Business, (c) the stations and signals carried by each such division and the channel position of each such signal and station of the Parent Business, (d) the approximate number of bulk accounts served by the Parent Cable Systems, (e) the approximate number of homes passed in the Parent Business as reflected in the system records of Parent or any of its Affiliates, (f) a description of basic and optional or tier services available from each such division of the Parent Business and the rates charged for each, (g) the channel capacity of each such division of the Parent Business, and (h) the municipalities served by each such division of the Parent Business and the community unit numbers of such municipalities.
Network Architecture. 2.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the Government, escalation processes, etc.) to achieve this desired result.
Network Architecture. 1502136 - 2640 Schematic overview of the network architecture within the data centres: internet Lochristi LCL Private WAN (MPLS) Mechelen
Network Architecture. 6.1.1. The Contractor Platform shall be protected behind a layer of firewalls.
Network Architecture. (i) Hubs and Lit Buildings communicate via multiple DS3/DS1 radio links in the 38-40 Ghz portion of the spectrum. The Hubs function as concentrators for these milliwave links, providing DS3 or DS1 service for Lit Buildings within the Hub service area. The traffic from the Lit Buildings will be bundled into multiple DS3 links over a fiber SONET ring backbone, or connected by lower frequency radio shots (i.e., 18 and 23 Ghz currently and 6 and 11 Ghz in the future).
Network Architecture. On-Net sites are customer access points for microwave links that transmit traffic to and from Hubs. Hub and On-Net sites communicate via multiple DS3/DS1 radio links in the 38 Ghz portion of the spectrum. The Hubs function as concentrators for these microwave links, providing DS3 or DS1 service for buildings within the Hub service area. In some instances , the traffic from these buildings will be bundled into multiple DS3 links over a fiber SONET Ring backbone, or connected by low frequency radio shots. This fiber backbone will initially be provided by a competitive access provider (CAP). In simple terms, the network architecture features On-Net sites as customer access points for traffic, with Hubs transmitting and receiving traffic from On-Net sites via microwave links. Hubs concentrate that traffic from On-Nets and transmit (or receive) traffic over fiber links to any one of the following:
AutoNDA by SimpleDocs
Network Architecture. You understand and agree that the Services and fees described in a SOW are based upon the architecture of your network and the System as described in an applicable SOW. In the event that your network or the System is subsequently modified in any manner, FWC reserves the right to change the scope of services and/or the fees charged to you under an applicable SOW. You agree to notify FWC prior to (i) installing any software to, or modifying any hardware of, the System, or (ii) moving the System, in part or in whole, to any location other than the locations at which FWC installed the components comprising the System. Your failure to notify FWC as described in this paragraph may result in you incurring additional costs, on a time and materials basis, to restore the System or to bring the System back to a functioning condition.
Network Architecture. (a) TWC shall have the right to determine, in its sole discretion, all aspects of network architecture with respect to the System Facilities that deliver the EarthLink High-Speed Service. To the extent TWC elects to make available any modifications or enhancements to network quality of service, or network operations or architecture for any Online Provider with or without an additional charge, then the Parties will reasonably discuss in good faith the possibility of amending this Agreement to include such modifications or enhancements. TWC shall support Service Subscribers in a reasonable manner (including time to repair, installations and responding to customer service calls) determined in TWC’s reasonable business judgment. TWC’s customer support shall not be determined based upon whether a particular high-speed service customer is a Service Subscriber or a customer of another Online Provider or Road Runner.
Network Architecture. 10 4.2 SERVICE LEVEL OBJECTIVES (OPS METRICS ARE UNDER DEVELOPMENT)....... 10 4.3 SECURITY (UNDER DEVELOPMENT, CLARIFICATION AND ROLES TBD).......... 11 5.0 END USER EXPERIENCE................................................... 13 5.1 PRIMARY PHONE NUMBERS.............................................. 13 5.2 SECONDARY PHONE NUMBERS............................................ 13 5.3 NUMBER TRANSFERABILITY (NTA) (TO BE CONFIRMED ONCE TELCO PARTNER RELATIONSHIPS ARE ESTABLISHED):.................................... 14 6.0 STATIC E911........................................................... 16
Time is Money Join Law Insider Premium to draft better contracts faster.