Project Approach: Task System Sample Clauses

Project Approach: Task System. The FIRM will develop and execute a planning process and final Master Plan document that meets the City’s and Department’s expectations and requirements. This plan is based on the original RFQ (RFQ – 16‐D‐000310, the FIRM’s proposal, additional suggested scope, and discussions with the City. • Task 1 – Project Management and Data Review • Task 2 – Assessment and Baseline Analysis of the Integrated System • Task 3 – Review and Analyses of the XxXxx Bay Complex • Task 4 – System Cost Review • Task 5 – Benchmarking Review • Task 6 – Identify Alternative Process Improvements • Task 7 – Public Outreach, Public Relations, and Communications • Task 8 – System Master Plan Development Presented in Table 1 is a proposed schedule for undertaking Tasks 1‐8 with Task 9 being an optional task. Table 1 ‐ Schedule Task Start Finish Task 1 – Project Management and Data Review Contract Execution; Day 0 Ongoing; Data Review – done Day 45 Task 2 – Assessment and Baseline Analysis Day 30 Day 90 Task 3 – Review and Analyse XxXxx Bay Complex Day 30 Day 90 Task 4 – System Cost Review Day 45 Day 90 Task 5 – Benchmarking Review Day 30 Day 90 Task 6 – Identify Alternative Process Improvements Day 60 Day 120 Task 7 – Public Outreach Day 120 Day 180 Task 8 – System Master Plan Day 90 Draft – Day 120 Draft #2 – Day 210 Final – Day 270 Task 1 ‐ Project Management and Data Review Objective Key objectives of this task are to provide: • Coordination of the Project • Review of pertinent information provided by the City and Department • Identification of data gaps and how such gaps will be addressed • Effective oversight • Accountability and quality management • Communication with the Department through a series of formal/informal approaches and meetings/work sessions • Maintenance of the project within the budget and schedule FIRM’s Team The FIRM’s primary contact with the City and project manager will be Xxx Xxxxxxxx, a Client Manager with TT. Xx. Xxxxxxxx has managed solid waste projects throughout Florida and has worked in this same capacity for the Lee County Integrated Waste Management Plan. His focus will be on delivering the work products discussed in this scope of work with a technical focus on waste disposal vulnerabilities and options. Xxxxxxxx Xxxx, Project Manager, will aid with the task management with a focus on budget, schedule, and quality control while concentrating on the regulatory aspects of the project. Xxxx Xxxxx, GBB Vice President will manage the work performed by GB...
Sample 1
AutoNDA by SimpleDocs

Related to Project Approach: Task System

  • Project Approach € Project schedules and budgets are reviewed by the Project Manager on a weekly basis during our company-wide Project Managers Meeting using project status reports generated by our control software (Deltek Vision). Progress is compared to the schedule and budget to ensure adequate resources are available and that necessary coordination is occurring. Costs are reported real time, with actual labor based on time sheet entry and actual expense costs based on invoices. The reporting system can be customized to track specific tasks or efforts in multiple categories, making it flexible enough to adapt to any project specific requirements. We hold regular project coordination meetings to facilitate communication and information transfer among the design team. These meetings are held weekly and are supplemented with e-mail communication, as well as telephone conversations. We hold monthly project status meetings with your project manager to update project status, discuss priorities, and receive direction from City staff. This provides an opportunity for communication and information to flow openly between the City and the design team. These meetings are supplemented by communications that will occur via e-mail and telephone. We conduct meetings with other agencies and stakeholders impacted by the work as needed. E-mail and telephone communication work well for quick questions or minor issues, but we have found that the most effective means of communication with other agencies and stakeholders is the “old-fashioned” face- to-face mexxxxx. Xxbble’s record of providing quality civil engineering services to our clients reflects our ability to manage multiple projects effectively and efficiently. Our philosophy is that each project is personally overseen by one of our principal officers, thereby providing immediate attention to all project aspects (i.e. negotiations, communications, schedule, budgets).

  • Project Approval The County may issue a Job Order Authorization for the Work, to include the firm-fixed-price of the Job Order and the project duration. Contractor agrees that all clauses of this Contract are applicable to any Job Order issued hereunder. The County reserves the right to reject a Contractor’s Quote based on unjustifiable quantities and/or methods, performance periods, inadequate documentation, or other inconsistencies or deficiencies on the Contractor’s part in the sole opinion of the County. The County reserves the right to issue a unilateral Job Order authorization for the Work if a Quote price cannot be mutually agreed upon. This is based upon unjustifiable quantities in the sole opinion of the County. The County also reserves the right to not issue a Job Order Authorization if the County’s requirement is no longer valid or the project is not funded. In these instances, the Contractor has no right of claim to recover Quote expenses. The County may pursue continuing valid requirements by other means where Contract was not reached with the Contractor.

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

  • 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 Work PURCHASER shall complete the following projects in accordance with the specifications provided in Exhibits B, C, D, E, and F and written instructions from STATE. Project locations are shown on Exhibit A unless otherwise described. PURCHASER shall furnish all material unless otherwise specified.

  • New Project Approval Consultant and District recognize that Consultant’s Services may include working on various projects for District. Consultant shall obtain the approval of District prior to the commencement of a new project.

  • Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Project acronym Use the project acronym as indicated in the submitted proposal. It cannot be changed, unless agreed during the negotiations. The same acronym should appear on each page of the grant agreement preparation documents to prevent errors during its handling.

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