Publishing ANOP-related Data Sample Clauses

Publishing ANOP-related Data. In the light of representations made to us, we requested that Transco explore the extent to which it could increase the transparency of its ANOPs calculations, whether through proposals to modify its network code or in other ways. We suggested, for instance, that Transco could make available the historical average operating pressure at specific parts of its pipeline system (whether at the connection point itself or on the feeder main). We also suggested that Transco should explain how any variances between that average and the calculated ANOP reconcile with its Ten-Year Statement. In addition, we suggested that Transco could make available information about the ANOPs quoted to it by other users at or near that point of its pipeline system. Xxxxxxx has suggested that the publication of detailed pressure information on the system can indicate the level of certain connected parties’ demands. Transco did, however, agree to consider how best it might present ANOP-related information.
Sample 1
AutoNDA by SimpleDocs

Related to Publishing ANOP-related Data

  • Statistical Information Any third-party statistical and market-related data included in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate in all material respects.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

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

  • Alert Information As Alerts delivered via SMS, email and push notifications are not encrypted, we will never include your passcode or full account number. You acknowledge and agree that Alerts may not be encrypted and may include your name and some information about your accounts, and anyone with access to your Alerts will be able to view the contents of these messages.

  • CENTURYLINK OSS INFORMATION 57.1 Subject to the provisions of this Agreement and Applicable Law, CLEC shall have a limited, revocable, non-transferable, non-exclusive right to use CenturyLink OSS Information during the term of this Agreement, for CLEC’s internal use for the provision of Telecommunications Services to CLEC End Users in the State.

  • Medical Information Throughout the Pupil's time as a member of the School, the School Medical Officer shall have the right to disclose confidential information about the Pupil if it is considered to be in the Pupil's own interests or necessary for the protection of other members of the School community. Such information will be given and received on a confidential, need-to-know basis.

  • Patient Information Each Party agrees to abide by all laws, rules, regulations, and orders of all applicable supranational, national, federal, state, provincial, and local governmental entities concerning the confidentiality or protection of patient identifiable information and/or patients’ protected health information, as defined by any other applicable legislation in the course of their performance under this Agreement.

  • Trade Secrets, Commercial and Financial Information It is expressly understood that Mississippi law requires that the provisions of this contract which contain the commodities purchased or the personal or professional services provided, the price to be paid, and the term of the contract shall not be deemed to be a trade secret or confidential commercial or financial information and shall be available for examination, copying, or reproduction.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

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