Laserfiche WebLink
MEMORANDUM OF UNDERSTANDING NO. C-9-0826 <br />EXHIBIT A <br />1. All durations and dates within the Project Schedule and this SOW <br />shall be in reference to calendar days. <br />2. Project Schedule shall be provided in a clear, concise, and legible <br />format for approval by AUTHORITY. Project Schedule shall be <br />submitted at a minimum on 11 inches by 17 inches medium <br />suitable for black and white reproduction. Electronic file copies <br />shall be provided on Compact Disc (CD-ROM). <br />3. Project Schedule shall include: <br />a. Title block, revision block, CONTRACT number, and legend. <br />b. NTP date, interim milestones as specified in SOW, <br />completion of specific tasks, and CONTRACT completion <br />date. <br />c. Scheduled start and/or completion dates imposed on <br />schedule by CONSULTANT consistent with SOW. Define <br />milestone events as scheduled dates specified in SOW and <br />prominently identify (flag) and connect to appropriate activity, <br />denoting start and completion, as applicable. Verify that <br />start milestones constrain start of dependent items. <br />d. Project Schedule shall be created, updated, and submitted in <br />Microsoft Project 2007 format (.MPP file format). <br />e. CONSULTANT shall update the Project Schedule upon <br />changes showing actual progress, actual start/finish dates <br />(shown for work items in progress), and identify current <br />sequence to milestones and project completion. <br />f. CONSULTANT shall make revisions to the Project Schedule <br />in the same format and detail as the baseline Project <br />Schedule. Proposed revisions are subject to AUTHORITY <br />review and approval. <br />g. Failure to include items required for performance of the <br />SOW shall not excuse CONSULTANT from completing work <br />required to achieve milestone event completion, <br />notwithstanding AUTHORITY written approval of the Project <br />Schedule. <br />Scope of Work 25 05/07/1 O <br />