3Scope Sample Clauses

3Scope. Confidential Information shall not include information that the receiving Party can demonstrate: (1) is generally available to the public other than as a result of a disclosure by the receiving Party; (2) was in the lawful possession of the receiving Party on a non-confidential basis before receiving it from the disclosing Party; (3) was supplied to the receiving Party without restriction by a third party, who, to the knowledge of the receiving Party after due inquiry, was under no obligation to the disclosing Party to keep such information confidential; (4) was independently developed by the receiving Party without reference to Confidential Information of the disclosing Party; (5) is, or becomes, publicly known, through no wrongful act or omission of the receiving Party or Breach of this Agreement; or (6) is required, in accordance with Article 22.1.8 of this Agreement, Order of Disclosure, to be disclosed by any Governmental Authority or is otherwise required to be disclosed by law or subpoena, or is necessary in any legal proceeding establishing rights and obligations under this Agreement. Information designated as Confidential Information will no longer be deemed confidential if the Party that designated the information as confidential notifies the other Party that it no longer is confidential.
AutoNDA by SimpleDocs
3Scope. Confidential Information shall not include information that the receiving Party can demonstrate: (1) is generally available to the public other than as a result of a disclosure by the receiving Party; (2) was in the lawful possession of the receiving Party on a non‐confidential basis before receiving it from the disclosing Party; (3) was supplied to the receiving Party without restriction by a third party, who, to the knowledge of the receiving Party after due inquiry, was under no obligation to the disclosing Party to keep such information confidential; (4) was independently developed by the receiving Party without reference to Confidential Information of the disclosing Party; (5) is, or becomes, publicly known, through no wrongful act or omission of the receiving Party or Breach of this Agreement; or (6) is required in accordance with Article 22.1.8 of this Agreement, Order of Disclosure, to be disclosed. Information designated as Confidential Information will no longer be deemed confidential if the Party that designated the information as confidential notifies the other Party that it no longer is confidential.
3Scope. This Agreement applies to all clinical studies post-marketing activities (e.g., post marketing studies and spontaneous or literature reports, surveillance, Marketing Research and other activities) in relation to the Product between AstraZeneca and the Alliance Management Contracting PartyDistributor in China.
3Scope. The purpose of this procurement is to obtain commercial cloud services (IaaS, PaaS, or SaaS cloud environments) in order to host information Impact levels 2 through 5 data as defined in the DoD Cloud Security Requirements Guide. The contractor shall provide the CHS team Cloud Service Management services (where not inherently governmental) to centrally manage, track and report cost and performance data for applications hosted or IT services provided within one or more Federal Risk and Authorization Management Program (FEDRAMP) and or DoD Provisional Authorization (PA) CSP cloud environments or cloud service offerings through a single point-of-entry. The CHS team is responsible for Impact Levels 2 – 5 Cloud Service Offerings (CSO). The consumer does not manage or control the underlying cloud infrastructure but has the control over areas of the OSI stack above the underlying infrastructure as defined by the CSO SLA. CSPs shall be FEDRAMP approved and have a signed DoD PA for the appropriate Information Impact Level at award. References to “the contractor” in this document shall mean or include: The Contractor and/or the services provided by the contractor themselves, a 3rd party vendor, the source Cloud Service Provider (CSP), or source Cloud Service Offering (CSO) unless specified otherwise. References to “Navy (or Government) Data” shall include or mean: all Navy data, applications, IT systems, IT capabilities, or IT systems/services built in, built (on behalf) by, transmitted/transitioned to or hosted by the Contractor; irrespective of where the data lies. (Meaning it could be on the desk in the contractor’s offices or in their relevant business operations tool), unless specified otherwise. References to “CSP”, “CSO”, and “contractor (cloud) hosting environment, IT infrastructure, IT system(s) or IT service offering” shall be used interchangeably and mean the same thing unless specified otherwise. All work shall be accomplished using the best commercial practices and current acceptable industry standards. The applicable references and standards invoked will vary within individual tasks and will be specifically called-out in each task order. In accordance with Defense Acquisition Policy changes, maximum utilization of non-government standards will be made wherever practical. Where backward compatibility with existing systems is required, selected interoperability standards will be invoked. For purposes of bidding, the following documents are not exclusive; ...
3Scope. 1This Quality Agreement is based on the Manufacturing and Supply Agreement. This Quality Agreement is supplemental to the Manufacturing and Supply Agreement and does not amend, supply or otherwise modify the Manufacturing and Supply Agreement.

Related to 3Scope

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Review Scope The parties confirm that the Asset Representations Review is not responsible for (a) reviewing the Receivables for compliance with the representations and warranties under the Transaction Documents, except as described in this Agreement or (b) determining whether noncompliance with the representations and warranties constitutes a breach of the Eligibility Representations. For the avoidance of doubt, the parties confirm that the review is not designed to determine why an Obligor is delinquent or the creditworthiness of the Obligor, either at the time of any Asset Review or at the time of origination of the related Receivable. Further, the Asset Review is not designed to establish cause, materiality or recourse for any Test Fail (as defined in Section 3.05).

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • CONTRACT SCOPE Pursuant to this Contract, Contractor is authorized to sell and provide only those Goods and/or Services set forth in Exhibit A – Included Goods/Services for the prices set forth in Exhibit B – Prices for Goods/Services. Contractor shall not represent to any Purchaser under this Contract that Contractor has contractual authority to sell or provide any Goods and/or Services beyond those set forth in Exhibit A – Included Goods/Services.

  • FIPPA The HSP acknowledges that the LHIN is bound by FIPPA and that any information provided to the LHIN in connection with this Agreement may be subject to disclosure in accordance with FIPPA.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Geotechnical Engineer « »« » « » « » « » « »

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.

  • COUNTY’S QUALITY ASSURANCE PLAN The County or its agent will evaluate the Contractor’s performance under this Contract on not less than an annual basis. Such evaluation will include assessing the Contractor’s compliance with all Contract terms and conditions and performance standards. Contractor deficiencies which the County determines are severe or continuing and that may place performance of the Contract in jeopardy if not corrected will be reported to the Board of Supervisors. The report will include improvement/corrective action measures taken by the County and the Contractor. If improvement does not occur consistent with the corrective action measures, the County may terminate this Contract or impose other penalties as specified in this Contract.

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