Licensee Position Sample Clauses

Licensee Position. The doses due to (1) tritium evaporation from the SDSP and (2) tritium seepage from the SDSP to the unrestricted area (in the location called Nancy’s Creek) do not need to be included in the annual dose assessment in Attachment 7 of the ARERR. The total curies released do not need to be included in the release summations in Attachment 2 of the ARERR. The curies, volume released, and dose were not included because those releases are “…not part of the pathway for designed releases from the plant.”
AutoNDA by SimpleDocs
Licensee Position. The licensee’s position, as described in “Licensing Bases for Prairie Island Nuclear Generating Plant Turbine Building Internal Flooding,” dated July 16, 2010 (XXXXX Accession No. ML102100198) is that water sources from the pipe that suffered the HELB should be included as a source of flooding, but water sources from piping adjacent to the HELB pipe that may be subjected to damage from pipe whips do not need to be considered. The licensee’s assessment is focused on PINGP’s response to the Giambusso letter (XXXXX Accession No. ML102100067) concerning the potential for flooding safety-related equipment resulting from a HELB. In responding to paragraph 9.29.15 of the Giambusso letter, concerning flooding potential from HELBs, PINGP discussed flooding from the HELB-ruptured pipe itself in a specific system in the Auxiliary Building. In its March 17, 1973, response contained in Final Safety Analysis Report (FSAR) Amendment 31 (XXXXX Accession No. ML102100175), PINGP did not CONTACT: Xxxxx X. Xxxxxx, NRR/DPR 000-000-0000 provide a discussion or consideration of other sources of water from a secondary rupture due to pipe whip. In fact, there is no discussion of any adjacent or target pipe, or pipe whip in the flooding paragraph. The licensee subsequently concluded that the Atomic Energy Commission (AEC) approved the PINGP response through the staff’s safety evaluation report (SER) and, therefore, accepted the premise that consequential flooding from the secondary pipe rupture is not required to be analyzed.
Licensee Position. The licensee’s position is that water sources from the pipe that suffered the HELB should be included as a source of flooding; however, water sources from piping adjacent to the HELB pipe that may be subjected to damage from pipe whips do not need to be considered. The licensee’s assessment is focused on PINGP’s response to the Giambusso letter concerning the potential for flooding safety-related equipment resulting from the HELB. In answering paragraph 9.29.15 of the Giambusso letter, concerning flooding potential from HELBs, PINGP discussed flooding from the HELB-ruptured pipe itself in a specific system in the Auxiliary Building. In its response, PINGP did not provide a discussion or consideration of other sources of water from a secondary rupture due to pipe whip. In fact, there is no discussion of any adjacent or target pipe, or pipe whip in the flooding paragraph. The licensee subsequently concluded that AEC approved the PINGP response through the staff’s safety evaluation report (SER); and therefore, accepted the premise that consequential flooding from the secondary pipe rupture is not required to be analyzed. Based on the thought process above, the licensee does not consider the fire projection sprinklers a water source since there was no specific discussion in the Giambusso discussion. The USAR established the licensing basis in Sections 6 and 12 for flooding (Section 12- “The Class I items are protected against damage from rupture of a pipe or tank resulting in serious flooding or excessive steam release to the extent that Class I function is impaired.”) Section 6 notes that internal flooding, which could be postulated to adversely affect the performance of Engineered Safety Features, was a part of the original plant design criteria. It further suggests that the turbine building was a building for which protection is designed to mitigate the consequences of flooding. The PINGP licensing basis for HELB impacts on adjacent piping resides in Section 12 (“Class I items are protected against damage from: Pipe whip and steam/water jets following a pipe rupture of an adjacent pipe”). The type of damage is discussed in USAR Appendix I. If the pipe is not restrained and is capable of striking a smaller diameter pipe with a smaller wall thickness than the target or adjacent pipe, one should conclude that the target or adjacent pipe is ruptured (unless an analysis shows this not to be the case). Since the pipe ruptures, water will flow out of the pipe just...
Licensee Position. The NSCW is OPERABLE when the tower return header control switch is in the OPEN BYPASS position. This position is explained in detail in the licensee letter to the NRC dated February 2, 2009, Agencywide Document Access and Management System (XXXXX) Accession No.
Licensee Position. In response to a request from regional staff, the licensee provided their position on these issues in writing. A detailed description of the licensee’s position is provided in the licensee’s White Paper (Reference 1).
Licensee Position. Pacific Gas and Electric evaluated the new seismic information against the LTSP 84th percentile deterministic spectrum (a margin analysis to the Hosgri design basis). Pacific Gas and Electric stated that further review against the seismic qualification basis was not needed because the new predicted vibratory ground motions were bounded by the LTSP spectrum, which was based on the seismic source that could produce the maximum vibratory ground motion at the Diablo Canyon site (Hosgri Event). The licensee concluded that the new seismic information was therefore neither a nonconforming nor an unanalyzed condition. The licensee based these conclusions on three factors documented in Notification 50086062, Task 30:
Licensee Position. Since first being presented with this issue in July 2008, the licensee’s engineering evaluations have led them to several positions. These positions have included that it is not preconditioning and that it is acceptable preconditioning. The licensee has benchmarked several other licensees’ pressure switch testing methodologies and has not reached a consensus on the preconditioning question. The licensee’s current position is that the issue is potentially a generic industry issue and should be addressed as such in regulatory space. The limited regulatory guidance on the topic of preconditioning resides primarily in Information Notice 97-16, “Preconditioning of Plant Structures, Systems, and Components Before ASME Code Inservice Testing of Technical Specification Surveillance Testing” and Inspection Manual Chapter 9900, “Maintenance – Preconditioning of Structures, Systems and Components Before Determining Operability.” The current pressure switch testing methodology affects approximately 30 pressure switches, which are relied upon to initiate technical specification required safety functions. These technical specification required functions include:
AutoNDA by SimpleDocs
Licensee Position. The licensee established a position that accessible interior surfaces of the RRVCH stud holes did not require a surface examination. The licensee position was based on Code Interpretation III-1-77-162 (Reference 1), which states in part, that drilled holes are not considered to be material form surfaces and the requirement for examination of holes (if any) resides in NX-4000 and NX-5000. The licensee concluded that the re-examination of machined surfaces as discussed in NB-4121.3 did not apply to the accessible interior surfaces of the flange stud holes because they were not material form surfaces. Reference 2 provides the NRC guidance on interpretations to Section III of the ASME Code. Specifically, if inspectors identify Code issues that result in a disagreement with the licensee, or if an official Code Interpretation is identified by an inspector that appears to conflict or is inconsistent with NRC requirements, the item should be sent via TIA to NRR for guidance and interpretation. Further, Reference 2 states that the ASME Code Interpretations are not incorporated into the Code of Federal Regulations; and therefore, the NRC is not bound by these interpretations. In this case, the licensee has applied wording “material form surfaces” from Reference 1 to exclude re-examination of machined surfaces formed during boring of the RRVCH flange holes. The licensee’s application of this interpretation appears to conflict with the 1989 edition of the ASME Code Section III NB-4121.3 requirement to re-examine machined surfaces of pressure boundary materials.

Related to Licensee Position

  • Licensee “Licensee” means the individual or company that has entered into an Agreement with the Embassy. “Offer” means a response to a solicitation that, if accepted, would bind the offeror to perform the resultant Agreement.

  • Licensor any Person from whom a Grantor obtains the right to use any Intellectual Property. Lien: any Person’s interest in Property securing an obligation owed to, or a claim by, such Person, whether such interest is based on common law, statute or contract, including liens, security interests, pledges, hypothecations, statutory trusts, reservations, exceptions, encroachments, easements, rights-of-way, covenants, conditions, restrictions, leases, and other title exceptions and encumbrances affecting Property. Lien Waiver: an agreement, in form and substance satisfactory to Agent, by which (a) for any material Collateral located on leased premises, the lessor waives or subordinates any Lien it may have on the Collateral, and agrees to permit Agent to enter upon the premises and remove the Collateral or to use the premises to store or dispose of the Collateral; (b) for any Collateral held by a warehouseman, processor, shipper, customs broker or freight forwarder, such Person waives or subordinates any Lien it may have on the Collateral, agrees to hold any Documents in its possession relating to the Collateral as agent for Agent, and agrees to deliver the Collateral to Agent upon request; (c) for any Collateral held by a repairman, mechanic or bailee, such Person acknowledges Agent’s Lien, waives or subordinates any Lien it may have on the Collateral, and agrees to deliver the Collateral to Agent upon request; and (d) for any Collateral subject to a Licensor’s Intellectual Property rights, the Licensor grants to Agent the right, vis-à-vis such Licensor, to enforce Agent’s Liens with respect to the Collateral, including the right to dispose of it with the benefit of the Intellectual Property, whether or not a default exists under any applicable License.

  • Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.

  • License Scope Licensee is granted a non-exclusive, perpetual license to use, execute, reproduce, display, perform, or merge the Product within its business enterprise in the United States up to the maximum licensed capacity stated on the Purchase Order. Product may be accessed, used, executed, reproduced, displayed or performed up to the capacity measured by the applicable licensing unit stated on the Purchase Order (i.e., payroll size, number of employees, CPU, MIPS, MSU, concurrent user, workstation). Licensee shall have the right to use and distribute modifications or customizations of the Product to and for use by any Authorized Users otherwise licensed to use the Product, provided that any modifications, however extensive, shall not diminish Licensor’s proprietary title or interest. No license, right or interest in any trademark, trade name, or service xxxx is granted hereunder.

  • License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not xxx, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.

  • Sublicensees Licensee shall have the right (but not the obligation) to sublicense those rights granted to it under Section 2.1 only as set forth in, and subject to the terms and conditions of, Section 2.5 and this Section 2.3.2, to (a) any Person (other than a Specified Person) with the prior written consent of Lxxxx, which consent will not be unreasonably withheld, conditioned or delayed; provided that Licensee may contract in the ordinary course of business with any Third Party contract research organization (“CRO”) or contract development and manufacturing organization (“CMO”) to handle certain clinical Development or Manufacturing activities, in Licensee’s reasonable discretion, without requiring Lilly’s consent; provided further that such CRO or CMO are working on Licensee’s behalf, (b) any of its Affiliates (only for so long as they remain Affiliates), provided that Licensee provides prior written notice (at least 20 Business Days in advance) to Lilly of any sublicenses to be granted to any Affiliate or its request for approval of any sublicense to be granted to any other Person, which shall include in each case a description of the rights to be granted and the purpose therefor, the identity of the proposed Sublicensee and the countries involved, or (c) a Specified Person. Each Affiliate or other Person to which any such sublicense is granted is referred to herein as a “Sublicensee.” Licensee shall remain responsible for the performance by each of its Sublicensees and shall cause each of its Sublicensees to comply with the applicable provisions of this Agreement, and Licensee shall be liable for the acts or omissions of its Sublicensees under or in connection with this Agreement (as if such acts or omission were those of Licensee). Without limiting the foregoing, Licensee shall: (x) ensure that each of its Sublicensees accepts in writing all applicable terms and conditions of this Agreement, including the non-compete, reporting, audit, inspection and confidentiality provisions hereunder; (y) under the agreements between Licensee and each of its Sublicensees, include a provision pursuant to which either (a) Lilly is named as a third-party beneficiary or (b) a mechanism (for example, a power of attorney) is implemented for Lxxxx to enforce all applicable terms and conditions of this Agreement against the Sublicensee in a manner reasonably satisfactory to Lilly, provided that, in each case, Lxxxx shall not proceed against any Sublicensee unless Lxxxx has first provided Licensee with written notice of the Sublicensee’s breach and Licensee has not, within 90 days after receipt of such notice, caused the Sublicensee to cease the breaching activity or otherwise cure the breach, in each case, to the reasonable satisfaction of Lxxxx; and (z) terminate all relevant agreements with any such Sublicensee in the case of any breach of such terms and conditions by such Sublicensee. A Sublicensee shall have the right to grant further sublicenses, subject to complying with the terms of this Section 2.3.2 with respect to further Sublicensees. For the avoidance of doubt, (i) Licensee will remain directly responsible for all amounts owed to Lilly under this Agreement, and (ii) each Sublicensee is subject to the negative and restrictive covenants set forth in Sections 2.2.1 and 2.4, respectively. Licensee hereby expressly waives any requirement that Lxxxx exhaust any right, power or remedy, or proceed against a subcontractor, for any obligation or performance hereunder prior to proceeding directly against Licensee. Notwithstanding anything to the contrary, (A) all sublicenses granted hereunder shall automatically terminate upon expiration or termination of this Agreement for any reason and (B) if the Parties enter into an agreement pursuant to Section 2.5 with respect to the Product, then as of the effective date of such agreement all sublicenses granted with respect to the Product shall automatically terminate, except as otherwise mutually agreed by the Parties in writing (and in no event shall any negotiations for any such agreement pursuant to Section 2.5 be conditioned on or otherwise affected by whether Lxxxx agrees to allow any such sublicenses to continue).

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.

  • Joint Work Product This Agreement is the joint work product of H-GAC and the Contractor. This Agreement has been negotiated by H-GAC and the Contractor and their respective counsel and shall be fairly interpreted in accordance with its terms and, in the event of any ambiguities, no inferences shall be drawn against any party.

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!