Project Specifics Sample Clauses

Project Specifics. Project milestones and timelines as well as associated payments are outlined in Appendix A.
AutoNDA by SimpleDocs
Project Specifics. The table below provides additional detail regarding the Requesting Party’s access to HMIS data. Project Description Purpose of the data match What questions will you answer with the data? Are you requesting de- identified/aggregate data or identifiable data? Specify data elements requested or provide a data file layout. Who will access the data? Are there other individuals outside of your organization with whom you will share the data? Describe your organization’s data security. How will you keep the data safe?
Project Specifics. The current project is expected to include at minimum:  Licensed inspection of the water xxxxx.  Preliminary report assessing the existing facilities and presenting recommended repairs or replacement needed to address maintenance and safety concerns.  Emergency pump and well repairs.  Well plugging.  Electric logging.  Camera services.  Disinfection and water testing.  Well cleaning.  Flow and proficiency testing. The City seeks the following minimum qualifications for Well Inspection companies:  Conducted at least sixty (60) inspections of potable municipal water xxxxx.  Field inspector must have at least ten (10) years of water well inspection experience.  Proposal shall include project references for at least five recent projects and the resume of the field inspector and report preparer.  All equipment entering the water must be disinfected in accordance with AWWA standards for potable water xxxxx.
Project Specifics. This section describes the Agreement Term and Fees for the services provided in this Agreement. ComplianceLine Hotline Toll-Free Number To be provided by Client Line Access Base Population 11,000 Annual Utilization Level (AUL) Unlimited
Project Specifics 

Related to Project Specifics

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

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