Dissemination of Project Information/Publication Requirements Sample Clauses

Dissemination of Project Information/Publication Requirements. (a) Prior to any dissemination, display, publication, presentation, or release of papers, articles, reports, summaries, or abstracts developed under the NRC/servicing agency agreement, the servicing agency shall submit them to the NRC for review and comment. NRC shall have a review and comment period of at least [60] days, after which both an NRC and servicing agency representative at the lowest management level, shall attempt to resolve any differing viewpoints or statements which are the subject of NRC objection. If the matter cannot be resolved at that level, the issue shall be brought up to the next management level in both organizations until an agreement can be reached or it reaches the Office Director level. In the event resolution cannot be achieved , the NRC may direct the servicing agency to not publish the work as a NUREG/CR, but publish as a servicing agency report without the NRC office name or Contracting Officer’s Representative (COR)’s name listed on the report, and with a Disclaimer conspicuously noted on the report, article, summary, abstract or related document that the servicing agency intends to release, display, disseminate or publish to other persons, the public or any other entities: “The views expressed in this [paper, journal article, report, summary, or abstract] do not represent those of the U.S. Nuclear Regulatory Commission.”
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Dissemination of Project Information/Publication Requirements. (a) Prior to any dissemination, display, publication, presentation, or release of papers, articles, reports, summaries, or abstracts developed under the NRC/DOE Agreement, the DOE Laboratory shall submit them to the NRC for review and comment. NRC shall have a review and comment period of at least [60] days, after which both an NRC and DOE Laboratory representative at the lowest management level, shall attempt to resolve any differing viewpoints or statements which are the subject of NRC objection. If the matter cannot be resolved at that level, the issue shall be brought up to the next management level in both organizations until an agreement can be reached or it reaches the Office Director level. Matters which cannot be resolved at this level shall be submitted for resolution to the Laboratory’s Technology Partnership Ombudsman (as set forth in the Laboratory’s Management and Operating contract with DOE or NNSA pursuant to § (p) of Department of Energy Acquisition Regulation (DEAR) 970.5227-3 “Technology Transfer Mission” (Aug 2002)). In the event resolution cannot be achieved by the Ombudsman, the NRC may direct the Laboratory/DOE to not publish the work as a NUREG/CR, but publish as a Laboratory report without the NRC office name or Project Manager’s name listed on the report, and with a Disclaimer conspicuously noted on the report, article, summary, abstract or related document that the Laboratory/DOE intends to release, display, disseminate or publish to other persons, the public or any other entities: “The views expressed in this [paper, journal article, report, summary, or abstract] do not represent those of the U.S. Nuclear Regulatory Commission.”
Sample 1Sample 2Sample 3

Related to Dissemination of Project Information/Publication Requirements

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Information Required Such records must contain the name; Social Security number; last known address, telephone number, and email address of each such worker; each worker's correct classification(s) of work actually performed; hourly rates of wages paid (including rates of contributions or costs anticipated for bona fide fringe benefits or cash equivalents thereof of the types described in 40 U.S.C. 3141(2)(B) of the Xxxxx-Xxxxx Act); daily and weekly number of hours actually worked in total and on each covered contract; deductions made; and actual wages paid.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Access to Financial Information Buyer’s representatives shall have access to, and Seller and its Affiliates shall cooperate with Buyer and furnish upon request, all financial and other information relating to the Hotel’s operations to the extent necessary to enable Buyer’s representatives to prepare audited financial statements in conformity with Regulation S-X of the Securities and Exchange Commission (the “SEC”) and other applicable rules and regulations of the SEC and to enable them to prepare a registration statement, report or disclosure statement for filing with the SEC on behalf of Buyer or its Affiliates, whether before or after Closing and regardless of whether such information is included in the Records to be transferred to Buyer hereunder. Seller shall also provide to Buyer’s representative a signed representation letter in form and substance reasonably acceptable to Seller sufficient to enable an independent public accountant to render an opinion on the financial statements related to the Hotel. Buyer will reimburse Seller for costs reasonably incurred by Seller to comply with the requirements of the preceding sentence to the extent that Seller is required to incur costs not in the ordinary course of business for third parties to provide such representation letters. The provisions of this Section shall survive Closing or termination of this Contract.

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