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.
View SourceView Similar (7)
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.
View SourceView Similar (2)
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.
View Source
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; ...
View Source
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.
View Source

Related to 3Scope

  • Project Management Plan 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 and

  • 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 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including 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 SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG 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. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • 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

  • Technology Research Analyst Job# 1810 General Characteristics