Specificity of Data Clause Samples

The "Specificity of Data" clause defines the level of detail and accuracy required for any data exchanged or referenced under the agreement. It typically outlines the standards or formats that data must meet, such as requiring precise measurements, up-to-date records, or clearly defined data fields. By establishing these requirements, the clause ensures that all parties work with reliable and unambiguous information, reducing the risk of misunderstandings or disputes arising from vague or incomplete data.
Specificity of Data. Pursuant to A.R.S. § 42-6001, the Department and City/Town agree that the data fields identified in Appendix B of this Agreement and the JT-1, TPT-2, and TPT-EZ forms in Appendix C of this Agreement (also provided online at ▇▇▇.▇▇▇▇▇.▇▇▇) meet the specificity requirements of City/Town. The data fields identified in Appendix B and the forms in Appendix C may be revised or replaced only by mutual agreement of the Department and Arizona municipalities, with any unresolved issues being referred to SMART for final determination.
View SourceView Similar (4)
Specificity of Data. A.R.S. § 42-6001 provides that taxpayers shall file and pay Municipal Taxes to the Department if the Department has developed the electronic and nonelectronic tools necessary to capture data with sufficient specificity to meet the needs of all taxing jurisdictions, including specific data regarding each tax classification and any corresponding deductions at each business location of the taxpayer. Pursuant to A.R.S. § 42-5015, the electronic system utilized by the Department must be able to capture data with sufficient specificity to meet the needs of the taxing jurisdiction. The Department and City/Town agree that JT2 and TPT2 (as summarized in Appendix C) are required to meet the specificity needs of City/Town. (a) Non-Program City/Town: If City/Town performed its own Municipal Tax administration, collection, and licensing prior to July 1, 2015, then if the Department is unable to commit by September 1, 2015 that the data detail behind the JT2 and TPT2 will be provided to City/Town beginning and from January 1, 2016, the following shall take place: (1) The term of the agreement entered into by the Department and City/Town pertaining to City/Town performing municipal licensing services on behalf of the Department shall be extended for one (1) year; and (2) All provisions in this Agreement pertaining to the administration, collection, and licensing of Municipal Taxes shall not go into effect until such time as the Department is able to meet the requirements of A.R.S. § 42-6001 and A.R.S. § 42-5015, however all language in this Agreement related to audit functions shall remain in full force and effect.
View SourceView Similar (2)
Specificity of Data. Pursuant to A.R.S. § 42-6001, the Department and City/Town agree that the data fields identified in Appendix B and the JT-1, TPT-2 and TPT- EZ forms provided in Appendix C meet the specificity requirements of City/Town. The forms provided in Appendix C may be revised and replaced as needed by mutual agreement of the Department and City/Town based on approval by SMART.
View SourceView Similar (2)
Specificity of Data. A.R.S. § 42-6001 provides that taxpayers shall file and pay Municipal Taxes to the Department if the Department has developed the electronic and nonelectronic tools necessary to capture data with sufficient specificity to meet the needs of all taxing jurisdictions, including specific data regarding each tax classification and any corresponding deductions at each business location of the taxpayer. Pursuant to A.R.S. § 42-5015, the electronic system utilized by the Department must be able to capture data with sufficient specificity to meet the needs of the taxing jurisdiction. The Department and City agree that JT2 and TPT2 (as summarized in Appendix C) are required to meet the specificity needs of City.
View Source

Related to Specificity of Data

  • Protection of Data The Contractor agrees to store Data on one or more of the following media and protect the Data as described: a. Hard disk drives. For Data stored on local workstation hard disks, access to the Data will be restricted to Authorized User(s) by requiring logon to the local workstation using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. b. Network server disks. For Data stored on hard disks mounted on network servers and made available through shared folders, access to the Data will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on disks mounted to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. For DSHS Confidential Information stored on these disks, deleting unneeded Data is sufficient as long as the disks remain in a Secure Area and otherwise meet the requirements listed in the above paragraph. Destruction of the Data, as outlined below in Section 8 Data Disposition, may be deferred until the disks are retired, replaced, or otherwise taken out of the Secure Area. c. Optical discs (CDs or DVDs) in local workstation optical disc drives. Data provided by DSHS on optical discs which will be used in local workstation optical disc drives and which will not be transported out of a Secure Area. When not in use for the contracted purpose, such discs must be Stored in a Secure Area. Workstations which access DSHS Data on optical discs must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism. d. Optical discs (CDs or DVDs) in drives or jukeboxes attached to servers. Data provided by DSHS on optical discs which will be attached to network servers and which will not be transported out of a Secure Area. Access to Data on these discs will be restricted to Authorized Users through the use of access control lists which will grant access only after the Authorized User has authenticated to the network using a Unique User ID and Hardened Password or other authentication mechanisms which provide equal or greater security, such as biometrics or smart cards. Data on discs attached to such servers must be located in an area which is accessible only to authorized personnel, with access controlled through use of a key, card key, combination lock, or comparable mechanism.

  • CONFIDENTIALITY OF DATA A. All financial, statistical, personal, technical, or other data and information relative to LOCAL AGENCY’s operations, which are designated confidential by LOCAL AGENCY and made available to CONSULTANT in order to carry out this contract, shall be protected by CONSULTANT from unauthorized use and disclosure. B. Permission to disclose information on one occasion, or public hearing held by LOCAL AGENCY relating to the contract, shall not authorize CONSULTANT to further disclose such information, or disseminate the same on any other occasion. C. CONSULTANT shall not comment publicly to the press or any other media regarding the contract or LOCAL AGENCY’s actions on the same, except to LOCAL AGENCY’s staff, CONSULTANT’s own personnel involved in the performance of this contract, at public hearings or in response to questions from a Legislative committee. D. CONSULTANT shall not issue any news release or public relations item of any nature, whatsoever, regarding work performed or to be performed under this contract without prior review of the contents thereof by LOCAL AGENCY, and receipt of LOCAL AGENCY’S written permission. E. Any subcontract entered into as a result of this contract shall contain all of the provisions of this Article.

  • Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.

  • Source of Data A description of (1) the process used to identify claims in the Population, and (2) the specific documentation relied upon by the IRO when performing the Quarterly Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare contractor manual or bulletins (including issue and date), other policies, regulations, or directives).‌‌‌

  • Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.