Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.
Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:
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 Month, Assuming Institution shall provide Receiver:
Excess Finance Charge Collections Series 2018-6 shall be an Excess Allocation Series. Subject to Section 4.05 of the Agreement, Excess Finance Charge Collections with respect to the Excess Allocation Series for any Distribution Date will be allocated to Series 2018-6 in an amount equal to the product of (x) the aggregate amount of Excess Finance Charge Collections with respect to all the Excess Allocation Series for such Distribution Date and (y) a fraction, the numerator of which is the Finance Charge Shortfall for Series 2018-6 for such Distribution Date and the denominator of which is the aggregate amount of Finance Charge Shortfalls for all the Excess Allocation Series for such Distribution Date. The “Finance Charge Shortfall” for Series 2018-6 for any Distribution Date will be equal to the excess, if any, of (a) the full amount required to be paid, without duplication, pursuant to subsections 4.05(a), 4.05(b) and 4.05(c) and subsections 4.07(a) through (j) on such Distribution Date and the full amount required to be paid, without duplication, pursuant to subsections 3.02(a)(iii) and 3.02(a)(iv) of the Transfer Agreement on the related Payment Date (as such term is defined in the Transfer Agreement) over (b) the sum of (i) the Reallocated Investor Finance Charge Collections, (ii) if such Monthly Period relates to a Distribution Date with respect to the Controlled Accumulation Period or Early Amortization Period, the amount of Principal Funding Account Investment Proceeds, if any, with respect to such Distribution Date and (iii) the amount of funds, if any, to be withdrawn from the Reserve Account which, pursuant to subsection 4.12(d), are required to be included in Class A Available Funds with respect to such Distribution Date. The amount of Excess Finance Charge Collections for Series 2018-6 for any Distribution Date shall be specified in subsection 3.02(a)(v) of the Transfer Agreement. On each Distribution Date, the Trustee shall deposit into the Collection Account for application in accordance with Section 4.05 of the Agreement the aggregate amount of Excess Finance Charge Collections received by the Trustee pursuant to the Transfer Agreement on such date.
Information Collection Information collection activities performed under this award are the responsibility of the awardee, and NSF support of the project does not constitute NSF approval of the survey design, questionnaire content or information collection procedures. The awardee shall not represent to respondents that such information is being collected for or in association with the National Science Foundation or any other Government agency without the specific written approval of such information collection plan or device by the Foundation. This requirement, however, is not intended to preclude mention of NSF support of the project in response to an inquiry or acknowledgment of such support in any publication of this information.
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Local Line’s data from BellSouth’s data, the following shall apply:
Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.
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).
Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.
