Prospect Development and Prospect Costs Sample Clauses

Prospect Development and Prospect Costs 
AutoNDA by SimpleDocs

Related to Prospect Development and Prospect Costs

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • Development Within twenty (20) Working Days after the Commencement Date and in accordance with paragraphs 3.10 to 3.12 (Amendment and Revision), the Contractor will prepare and deliver to the Authority for approval the full and final Security Plan which will be based on the draft Security Plan set out in Appendix B.

  • Product Development (a) Supplier may develop enhancements it intends to incorporate into the BioGlue Surgical Adhesive during the term of this Agreement that have potential application to the Company Product (“Enhancements”). Unless otherwise agreed by the parties, at least once every six months during the Term, representatives of each of BioForm and Supplier shall hold a meeting in accordance with Sections 4.4 and 8.4 (the “Product Development Meeting”) at which Supplier will present Enhancements for BioForm to consider for application to the Company Product. At such Product Development Meeting, BioForm will also present its marketing plans (pursuant to Section 4.4) for the period and any information or feedback that BioForm reasonably believes may lead to Improvements. Within 30 calendar days following each Product Development Meeting, Supplier shall deliver a notice to BioForm (the “Enhancements Notice”) that shall describe the Enhancements that were presented by Supplier at such Product Development Meeting. Within 30 calendar days following receipt of the Enhancements Notice, BioForm may notify Supplier in writing if BioForm elects that any Enhancement described in the Enhancements Notice shall become an Improvement. If BioForm does provide such notice to Supplier during such 30-calendar day period, then BioForm and Supplier shall agree on a timeline for implementation of the Improvement in new Product Specifications for Company Product. If BioForm does not provide such a notice, said Enhancement shall not be implemented into the Company Product. The Enhancements Notice may also describe any potential Enhancements presented by Supplier at the Product Development Meeting, but BioForm shall not be required to take any action under this Section 8.4 with respect to such potential Enhancements until such time as they are presented by Supplier as Enhancements at a future Product Development Meeting. All Enhancements and potential Enhancement information provided by Supplier shall be considered Supplier Confidential Information. (b) From time to time, each party may request the other party to participate in joint projects to develop Improvements. Neither party is obligated to participate in such projects, and in each **** Certain information on this page has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. instance, each party’s decision whether to participate will be made in such party’s sole discretion. If both parties mutually agree to participate in such a project (a “Program”), the parties will promptly prepare a mutually agreeable written development agreement specifying the development activities to be performed by and the research and development tasks assigned to each party (the “Development Agreement”). All allocation of Intellectual Property rights with respect to any Program will be set forth in writing in the Development Agreement. (c) In the absence of a Development Agreement, (i) BioForm and Supplier shall retain joint ownership of Intellectual Property rights in which there is joint inventorship by BioForm (or its Affiliates) and Supplier, as determined in accordance with United States patent law, with Supplier’s rights in such joint ownership being subject to the license rights of BioForm under this Agreement, (ii) any Intellectual Property rights related to the Company Products, Enhancements, and Improvements that are created solely by employees or consultants of Supplier during the Term shall be considered to be Intellectual Property rights of Supplier, subject to the license rights of BioForm under this Agreement, and (iii) any Intellectual Property rights related to the Company Products and Improvements that are created solely by employees or consultants of BioForm or any of its Affiliates during the Term shall be considered to be Intellectual Property rights of BioForm. BioForm hereby grants to Supplier a perpetual, royalty free, world-wide, nonexclusive license to Supplier under such Blocking Intellectual Property to make, use, and sell such Intellectual Property outside the Field. “Blocking Intellectual Property” for the purposes of Section 8.4(c)(iii) shall mean Intellectual Property necessary for Supplier to make, use, or sell SA Product.

  • Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Research Project The findings of any research project, which would change the provisions of this Agreement will not be implemented until such changes are negotiated and agreed to by the parties.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Development Rights The Employee agrees and declares that all proprietary information including but not limited to trade secrets, know-how, patents and other rights in connection therewith developed by or with the contribution of Employee's efforts during his employment with the Company shall be the sole property of the Company. Upon the Company's request (whenever made), Employee shall execute and assign to the Company all the rights in the proprietary information.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

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