Public Input Regarding Proposed Sample Clauses

Public Input Regarding Proposed. Revisions to 10 CFR Part 26 To Include Aspects of the 2008 Health and Human Services Guidelines After HHS issued the 2008 HHS Guidelines, the NRC performed a comprehensive review of 10 CFR part 26 and the 2008 HHS Guidelines to identify provisions in the NRC’s regulations that may need to be revised. Two public meetings were held in 2009, on February 24 and June 24, with regulated entities, interest groups, and members of the general public to discuss the changes in the 2008 HHS Guidelines. In 2010, the NRC analyzed the DOT’s final rule changes to 49 CFR part 40, ‘‘Procedures for Transportation Workplace Drug and Alcohol Testing Programs’’ (75 FR 49850; August 16, 2010) to understand how another Federal agency that tests civilians implemented the 2008 HHS Guidelines. The NRC also analyzed lessons learned from implementation of the 2008 FFD final rule. Collectively, these efforts resulted in a list of potential changes to 10 CFR part 26 that the NRC presented, for feedback, at a third public meeting held on October 11, 2011. The NRC summarized public comments received at the October 11 meeting, as well as emailed comments received subsequent to the meeting, in a document titled ‘‘Comments for the October 11, 2011, Public Meeting’’ (included as Enclosure 3 in package available via XXXXX Accession No. ML112930153). A fourth meeting was held on September 11, 2013, to inform the public of the status of the rulemaking. Public meetings were attended by representatives of nuclear power plant licensees, the Nuclear Energy Institute, the Institute of Nuclear Power Operations, the International Brotherhood of Electrical Workers, and HHS. Based upon feedback received during the four public meetings, some of the NRC-proposed revisions were removed from consideration because the NRC decided that it was not appropriate to pursue those particular issues in this rulemaking, while others were revised. The NRC-proposed revisions, along with associated issues raised by the public, are discussed in Section III.C of this document.
Sample 1
AutoNDA by SimpleDocs

Related to Public Input Regarding Proposed

  • Solicitation Exceptions/Deviations Explanation If the bidder intends to deviate from the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation, all such deviations must be listed on this attribute, with complete and detailed conditions and information included or attached. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any bid based upon any deviations indicated below or in any attachments or inclusions. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Standard Terms and Conditions, Item Specifications, and all other information contained in this Solicitation.

  • Non-Public Information Except with respect to the material terms and conditions of the transactions contemplated by the Transaction Documents, the Company covenants and agrees that neither it, nor any other Person acting on its behalf, will provide any Purchaser or its agents or counsel with any information that the Company believes constitutes material non-public information, unless prior thereto such Purchaser shall have entered into a written agreement with the Company regarding the confidentiality and use of such information. The Company understands and confirms that each Purchaser shall be relying on the foregoing covenant in effecting transactions in securities of the Company.

  • Public Involvement The NRCS State Conservationist will ensure the public is involved in the development of this State-based Prototype Agreement and participates in Section 106 review as set forth above in Section V (reference to other parties).

  • Public Information The State will comply with Government Code, Chapter 552, the Public Information Act, and 43 Texas Administrative Code §3.10 et seq. in the release of information produced under this contract.

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

  • Public Information and Confidentiality Information related to the performance of this Contract may be subject to the Public Information Act and will be withheld from public disclosure or released to the public only in accordance therewith. Performing Agency shall make any information required under the Public Information Act available to the System Agency in portable document file (“.pdf”) format or any other format agreed between the Parties. To the extent permitted by law, Performing Agency and the System Agency agree to keep all information confidential, in whatever form produced, prepared, observed, or received by Performing Agency or the System Agency. The provisions of this section remain in full force and effect following termination or cessation of the services performed under this Contract.

  • Solicitation Deviation/Compliance Does the vendor agree with the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation? Yes

  • Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion - Lower Tier Covered Transactions (a) The prospective lower tier participant certifies, by submission of this proposal, that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation in this transaction by any federal department or agency.

  • Listing Information Confidentiality BellSouth will accord <<customer_name>>’s directory listing information the same level of confidentiality that BellSouth accords its own directory listing information, and BellSouth shall limit access to <<customer_name>>’s customer proprietary confidential directory information to those BellSouth employees or agents who are involved in the preparation of listings or directories.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

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