Program Schedule Sample Clauses
The Program Schedule clause defines the timeline and sequence of activities, deliverables, or milestones for a project or agreement. It typically outlines key dates, deadlines, and the order in which tasks must be completed, often referencing an attached schedule or timeline document. This clause ensures that all parties have a clear understanding of their obligations and the expected timing, helping to coordinate efforts and avoid misunderstandings about project progress or completion.
Program Schedule. The Developer must attach as Exhibit C to this Agreement a Program Schedule, which is a timetable that the Developer must follow in developing the property to meet an NSP eligible end use. The Developer must submit performance reports as required by the Authority to demonstrate compliance with the Program Schedule. Changes to the schedule may be approved by the Authority only because of delays resulting from Acts of God or other delays that are not caused in any way by the Developer. It is the responsibility of the Developer to notify the Authority promptly in writing whenever a delay is anticipated or experienced.
Program Schedule. The Contractor shall develop and maintain a Master Phasing Schedule and Detailed Program Schedules. The Master Phasing Schedule shall clearly identify all key milestones including all hardware, software, and data deliveries, all customer furnished items and the date required, major technical and programmatic reviews, and all TerreStar milestones that are dependent on S-BSS deliveries. The Detailed Program Schedules shall be used by the contractor to plan all tasks, task dependencies, and critical path. The Detailed Program Schedules shall be updated monthly to reflect program progress and provided to the TerreStar PMO with the monthly status report.
Program Schedule. The Grantee must inform HUD immediately, in writing, of any problems, delays or adverse conditions that will impair materially the Grantee’s ability to comply with the Program Schedule, and include a statement of action taken, or proposed to be taken, and any assistance needed to resolve the situation. HUD must approve any proposed changes to the Program Schedule that would modify any date or time period.
Program Schedule. A. Contractor shall conduct one (1) annual inspection within the first month after award of the Contract and within the first month of each renewal year thereafter. Contractor shall conduct one (1) semi-annual inspection within six (6) months after award of the Contract.
B. Contractor must notify OC Public Works/Facilities Operation’s HVAC Shop Planner or Craft Supervisor a minimum of 72 hours in advance to schedule the P.M. inspection.
Program Schedule. Only Work Package 1a-1/3 and Work Package 1a-2 are scheduled to be completed and issued for proposals/bidding before the end of 2011 with construction proceeding in early 2012. As these facilities are constructed and made operational, and as future funding becomes available, IID will determine which elements of the remaining phases (Phases 1b and 2) will be required and/or if other elements such as additional system automation will be employed.
Program Schedule. The Contractor shall update the Master Schedule with Chipset tasks/milestones and shall develop and maintain Detailed Chipset Program Schedules. The Master Schedule shall clearly identify all key milestones including all hardware, software, and data deliveries, all TerreStar-furnished items and the date required, all deliveries to the terminal vendor and the date required, and major technical and programmatic reviews. The Detailed Program Schedules shall be used by the contractor to plan all tasks, TerreStar Satellite Chipset SOW task dependencies, and critical path. The Detailed Program Schedules shall be updated monthly to reflect program progress and provided to the TerreStar PMO with the monthly status report. The Contractor may maintain a separate Master Schedule for the Chipset development, however, the program interdependencies between the S-BSS development and the Chipset development shall be contained in each schedule.
Program Schedule. The GEC shall update and maintain the existing program schedule using Primavera P6 or more current version as specified by the STATE. The GEC shall maintain the schedule for key milestones and critical path for the duration of the program from information provided by others. The GEC shall include each individual project under development on the corridor by the STATE or other entities. The GEC shall depict the order and interdependence of various tasks, subtasks, milestones and deliverables. The GEC shall indicate the primary functional area, such as design, environmental, public involvement, right-of-way/utility, general administration, etc. for each activity. The GEC shall indicate when another party is responsible for completion of an activity such as review by the State. The GEC shall maintain the program schedule from execution through GEC contract completion. The GEC shall review progress during program- and project-level coordination meetings and update the schedule as necessary. The GEC shall identify issues that need resolution or action items in the Progress Report and in program- and project-level coordination meetings. The GEC shall produce a table of deliverables from the information provided in the schedules upon the request of the STATE. The GEC shall review, assess, monitor, and update monthly detailed schedules and other scheduling documents produced by others including utility companies and third party agencies, and shall integrate critical milestone elements within the program master schedule.
Program Schedule. The Orange County Jail Senior Program Coordinator will schedule the groups. The groups may be held in the daytime, evening, weekdays, or Saturdays based upon available program space and facility needs and constraints. The County reserves the right to alter classes based upon facility needs and programming schedules may vary based upon the constraints of the facility.
Program Schedule. The delivery of 5 frames of Flex circuits to VOLCANO shall occur in 13 weeks from receipt of PO. • VOLCANO will perform testing, analysis and approve/disapprove the delivered qualification parts in 3 weeks or less from receipt. • Upon approval of qualification, but no sooner than 6 weeks from delivery of the 1st 5 frames, EI shall produce and deliver Flex circuits of 2200 pieces on a frame per week for 3 weeks to validate manufacturing capacity. This may include a ramp to get to 2200 per week. • Manufacturing of Flex circuits shall continue at the rate of 2200 units per week minimum through December 2008.
Program Schedule. The Program Consultant will maintain and update on a monthly basis the Program Schedule which will be developed during the Program Initialization phase. The Program Schedule shall include all necessary details as required by the Program Manager to assist in the planning and management of the MAPS 3 Program.