Identify Variance Sample Clauses

Identify Variance 
AutoNDA by SimpleDocs

Related to Identify Variance

  • T1 IDENTIFICATION PROCEDURES During the restoration of service after a disaster, BellSouth may be forced to aggregate traffic for delivery to a CLEC. During this process, T1 traffic may be consolidated onto DS3s and may become unidentifiable to the Carrier. Because resources will be limited, BellSouth may be forced to "package" this traffic entirely differently then normally received by the CLECs. Therefore, a method for identifying the T1 traffic on the DS3s and providing the information to the Carriers is required.

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • Identifying Information Issuer and Broker acknowledge that a portion of the identifying information set forth on Exhibit A is being requested by NCPS in connection with the USA Patriot Act, Pub.L.107-56 (the “Act”). To help the government fight the funding of terrorism and money laundering activities, Federal law requires all financial institutions to obtain, verify, and record information that identifies each person who opens an account. For a non-individual person such as a business entity, a charity, a Trust, or other legal entity, we ask for documentation to verify its formation and existence as a legal entity. We may also ask to see financial statements, licenses, identification and authorization documents from individuals claiming authority to represent the entity or other relevant documentation.

  • Contractor’s Staff Identification Contractor shall provide, at Contractor’s expense, all staff providing services under this Contract with a photo identification badge.

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • Identifying Number The Participant’s Social Security number will serve as the identification number of his or her Custodial Account. An employer identification number is required only for a Custodial Account for which a return is filed to report unrelated business taxable income. An employer identification number is required for a common fund created for IRAs.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Accounts Not Required to Be Reviewed, Identified, or Reported Unless the Reporting Financial Institution elects otherwise, either with respect to all Preexisting Individual Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in the jurisdiction provide for such an election, the following accounts are not required to be reviewed, identified, or reported as Reportable Accounts:

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

  • Updating At the end of each calendar quarter in which there occurs any event that materially affects the accuracy of the information contained in the Certification or, if applicable, Standard Form-LLL, Qualified Producer shall file with TVA an initial or new Standard Form-LLL with such new information or modifications as are necessary to correct any inaccuracies in the information originally declared and certified.

Time is Money Join Law Insider Premium to draft better contracts faster.