Laserfiche WebLink
<br />Deliverable <br />Deliverables for this Task will be negotiated as a Task Order which describes the <br />activities, budget and schedule that are identified and mutually agreed upon in writing by <br />RTi and the State, <br /> <br />Task R9 - Management <br /> <br />Approach <br />In this Task, Rti will perform activities necessary to guide the project in accordance with <br />the scope, budget and schedule, <br /> <br />Rti will prepare an invoice each month which is similar to that used in Phase 2 which <br />describes expenditures by person and major task. In addition, a budget analysis will be <br />prepared which describes, for each Subtask, expenditures by reporting period, project to <br />date, budget, balance and % spent. J 7 / , <br />l &"4' t. Co ,.....;v~ <br /> <br />Rti will prepare progress reports each month which are similar to those used in Phase 2, <br />The progress reports will describe activities performed by Subtask to support the invoice, <br />In addition, the progress report will contain a section where comments or concerns related <br />to the contracted scope, budget or schedule are identified, <br /> <br />Deliverable <br />I. Monthly invoice of expenditures, <br />2, Monthly progress reports, <br /> <br />Assumptions and Conditions <br />There are a number of assumptions that must be met for the RTi to produce the <br />deliverables mentioned above, on schedule, on budget, and in a manner which satisfies or <br />exceeds the State's objectives, These assumptions are as follows: <br /> <br />. RTi will perform no modifications to the final design (Exhibit I), unless expressly <br />authorized in writing by the CRDSS project manager. These changes will be <br />considered out of the present scope and the funds for these changes must be <br />authorized prior to any work being performed, The names of all entities and <br />attributes and relationships between entities will remain the same as the names and <br />relationships in Exhibit I. Note the names included in Exhibit I have been limited to <br />18 characters in order to allow both physical and logical names to be the same, <br />. The data received by the RTi will be assumed to have been subjected to quality <br />assurance procedures by the State, If a record of data contains errors, (for example, <br />they do not contain unique ID's, or ~tain duplicate records, or nulls in key and <br />constrained fields), it will not be con rted, A list of the erroneous records will be <br />sent to the State for correction, RTi is ' not responsible for correcting data errors, <br /> <br />~~\.3 <br /> <br />Scope of Work, HB - CRDSS, 12120/96 <br /> <br />11 <br />