Recorded Usage Data Format Sample Clauses

Recorded Usage Data Format. 1BA will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the AT&T Customer Usage Data Transfer Requirements, March 1996 ("Data Requirements"), which is attached hereto and incorporated herein as Appendix I.
Sample 1Sample 2
Recorded Usage Data Format. 4.1 PACIFIC will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the CLEC Customer Usage Data Transfer Requirements, November 1996 ("Data Requirements"), which is attached hereto and incorporated herein as Appendix I. 4.2 PACIFIC shall include the Working Telephone Number (WTN) of the call originator on each EMR call record. 4.3 End user customer usage records and station level detail records shall be in packs in accordance with EMR standards. 4.4 PACIFIC shall append the recording point identification to each EMR call record the recording point identification or other mutually agreed upon code that specifically designates the recording switch.
Sample 1Sample 2
Recorded Usage Data Format. 4.1 PACIFIC will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the CLC Usage Requirements document, dated December 1996 ("Data Requirements"), which is attached hereto and incorporated herein as Appendix I. 4.2 PACIFIC shall include the Working Telephone Number (WTN) of the call originator on each EMR call record. 4.3 End user customer usage records and station level detail records shall be in packs in accordance with EMR standards. 4.4 PACIFIC shall append the recording point identification or some other code that specifically identifies the central office switch that is mutually agreeable to both Parties to each EMR call record.
Sample 1
Recorded Usage Data Format. BA will provide Recorded Usage Data in the EMI format and by category, group and record type, as specified in Appendix I, Subappendix G, “Sprint Call/Service Type and Associated EMI Matrix”.
Sample 1
Recorded Usage Data Format. GTE will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the AT&T Customer Usage Data Transfer Requirements, March 1996 ("Data Requirements") which is attached hereto and incorporated herein as Appendix 11.
Sample 1
Recorded Usage Data Format. 4.1 NEVADA will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the CLEC Usage Requirements document, dated November 1996 (“Data Requirements”), which is attached hereto and incorporated herein as Appendix I. 4.2 NEVADA shall include the Working Telephone Number (WTN) of the call originator on each EMR call record. 4.3 End user customer usage records and station level detail records shall be in packs in accordance with EMR standards. 4.4 NEVADA shall append the recording point identification or some other code that specifically identifies the central office switch that is mutually agreeable to both Parties to each EMR call record.
Sample 1
Recorded Usage Data Format. 4.1 GTE will provide Recorded Usage Data in the EMR format and by category, group and record type, as specified in the AT&T Customer Usage Data Transfer Requirements, March 1996 ("Data Requirements"), which is attached hereto and incorporated herein as Appendix II. 4.2 GTE shall include the Working Telephone Number (WTN) of the call originator on each EMR call record. 4.3 End user customer usage records and station level detail records shall be in packs in accordance with EMR standards.
Sample 1

Related to Recorded Usage Data Format

  • Usage Data 7.1. The parties shall supply data on usage of the Licensed Work that is available to them during the term of this Licence. Notwithstanding the foregoing, the parties shall neither assemble nor provide data from which an individual user could be identified.

  • 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).

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Contract Database Metadata Elements Title: Xxxxxxx-Xxx Xxxxx Central School District and Xxxxxxx-Xxx Xxxxx Teachers Association (2007)

  • Production Report and Lease Operating Statements Within 60 days after the end of each fiscal quarter, a report setting forth, for each calendar month during the then current fiscal year to date, the volume of production and sales attributable to production (and the prices at which such sales were made and the revenues derived from such sales) for each such calendar month from the Oil and Gas Properties, and setting forth the related ad valorem, severance and production taxes and lease operating expenses attributable thereto and incurred for each such calendar month.

  • Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts.

  • Financial Records 26.1.1 CONTRACTOR shall prepare and maintain accurate and complete financial records. Financial records shall be retained by CONTRACTOR for a minimum of five (5) years from the date of final payment under this Contract, or until all pending COUNTY, State, and federal audits are completed, whichever is later. 26.1.2 CONTRACTOR shall establish and maintain reasonable accounting, internal control, and financial reporting standards in conformity with generally accepted accounting principles established by the American Institute of Certified Public Accountants and to the satisfaction of ADMINISTRATOR.