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.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").
Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.
Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:
Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles:
(a) Such schedules shall be established by mutual agreement of the Home and the Union;
(b) These schedules may pertain to full-time and/or part-time employees;
(c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations;
(d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules;
(e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis.
(f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).
System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.
Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.
Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.
Network Interface Device 4.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s on-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.
4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.
