Ordering Guidelines and Processes 1.14.1 For information regarding Ordering Guidelines and Processes for various Network Elements, Combinations and Other Services, TWTC should refer to the “Guides” section of the AT&T Interconnection Web site. TWTC will be notified of any material changes to such “Guides”.
PROCEDURES AND/OR CRITERIA FOR COURSE ARTICULATION a. Complete the ROP Careers with Children course at Freedom High School with a grade of “B” or better.
Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.
CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.
Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.
The Contractor must 16.1.1. treat all Authority Protected Information as confidential and safeguard it accordingly, implementing appropriate technical and organisational measures to protect Authority Protected Information against disclosure;
Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Bulk Migration 2.1.9.1 If Telepak Networks requests to migrate twenty-five (25) or more UNE- Port/Loop Combination (UNE-P) customers to UNE-Loop (UNE-L) in the same Central Office on the same due date, Telepak Networks must use the Bulk Migration process, which is described in the BellSouth CLEC Information Package, “UNE-Port/Loop Combination (UNE-P) to UNE-Loop (UNE-L) Bulk Migration.” This CLEC Information package, incorporated herein by reference as it may be amended from time to time, is located at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/xxxxxx/xxxx/xxxx.xxxx. The rates for the Bulk Migration process shall be the nonrecurring rates associated with the Loop type being requested on the Bulk Migration, as set forth in Exhibit A of this Attachment. Additionally, OSS charges will also apply per LSR generated per customer account as provided for in the Bulk Migration Request. The migration of loops from Integrated Digital Loop Carrier (IDLC) will be done pursuant to Section 2.6 of this Attachment.
