Requirements/Notes Clause Samples
The 'Requirements/Notes' clause outlines specific obligations, instructions, or important information that parties must consider or comply with under the agreement. It typically details particular standards, procedures, or documentation that must be followed, such as providing certain reports, adhering to technical specifications, or noting exceptions to general terms. This clause serves to clarify expectations and ensure that all parties are aware of and can meet the detailed requirements necessary for successful contract performance, thereby reducing misunderstandings and disputes.
Requirements/Notes. The Project Work Plan will contain: • Project's activities and tasks • Dates of project activities and tasks • Specific resources assigned to project tasks • Detailed Project schedule / Work Breakdown Structure (WBS) featuring phases, deliverables, and work packages • Control Points and Deliverables • City Review Periods for Control Points and Deliverables • Project Acceptance of Implementation Control Points • Decisions will be made in a timely fashion in order to achieve scheduled due dates on tasks and prepare for subsequent training sessions. Decisions left unmade may affect the project schedule as each analysis and implementation session builds on the decisions made in prior sessions • The project plan will be consistent with the SOW • All homework and other activities required of either the City Project Team or Contractor consultants will be included on the project plan.
Requirements/Notes. ▇▇▇▇▇ will ensure that all referenced knowledge base documents are current and applicable for Client’s project. • References to documents on the knowledge base will be specific and direct Client to specific documents. • ▇▇▇▇▇ will provide guidance and demonstrate to Client project team members how to use the knowledge base to find necessary information.
Requirements/Notes. Risks will be monitored, recorded, and assessed using an agreed upon methodology in the Contractor Risk Plan. All risks will be actively monitored by both Contractor and City • Contractor will have responsibility for maintaining the project risk plan.
Requirements/Notes. As part of the Project Kick Off, The Contractor Project Manager will provide an overview of the SharePoint Site, its organization, included documents and policies for use. The City and Contractor will mutually agree upon SharePoint use for the project. Contractor performs a daily routine backup for all City SharePoint sites using industry standard backup techniques and processes. Site-specific backup files can be provided as a billable service with a minimum of 4 hours (1/2 day) charged for each backup file using the contracted Contractor rate for implementation services. Contractor does not provide SharePoint consulting services to restore provided backup files in client-hosted environment.
Requirements/Notes. Any issues identified on the site report will also be identified on the Project Issues Log • All site reports will be completed no later than one week after completion of a site visit. • All site reports will be reviewed and edited for quality by the ▇▇▇▇▇ project manager prior to posting for Client review. • The Tyler Project Manager will be responsible for ensuring that site reports are complete and accurate. • Completion of site reports will be part of acceptance criteria for each phase.
Requirements/Notes. In the event that there are project issues that require Contractor's on-site participation, City will not be required to reimburse the costs of travel for Contractor's Project Manager, Regional Project Manager, or Contractor Executive Sponsor's on-site participation City may cancel Executive Steering Committee Meetings if there are not a sufficient number of items to discuss or if items can be deferred until the following meeting.
Requirements/Notes. All Contractor project managers and implementation consultants will become familiar with the contract, SOW, and any applicable City policies. • The kick off meeting presentation will be a collaborative effort between City and Contractor. • Contractor will lead development of the kick off presentation (City to provide input) and the kick off presentation will be developed specific to the City project (not a generic kick off PowerPoint template). • All Key Personnel assigned to the project will be present at the respective phase kick off meeting, assuming that applicable and effective project tasks can occur with subsequent to the kick-off. • Kick Off meetings will occur prior to the beginning of each phase.
Requirements/Notes. All review periods will be tracked on the project plan. • The Client project manager will have decision authority to approve/reject all project Control Points and Deliverables. • Acceptance will be initiated and managed by utilizing an agreed upon workflow approval process. • All control point reviews will be identified on the project plan. • Both ▇▇▇▇▇ and Client recognize that failure to complete tasks and resolve open issues may have a negative impact on the project. • For any tasks not yet complete, ▇▇▇▇▇ and Client will provide sufficient resources to expedite completion of tasks as to not negatively impact the project.
Requirements/Notes. The format for the status reports will be mutually agreed as part of the project planning phase of the project. City will cooperate and provide information for inclusion on the status report. Contractor will submit one status report that identifies issues related to the entire project. In the event that Contractor has multiple resources working on the project at one time, the Contractor project manager will coordinate issues and submit one status report. The Status report will be delivered at least two (2) business days prior to any scheduled Executive Sponsor, Steering Committee, or Project Manager meeting at which the status report is being discussed. Biweekly status reports are due on Wednesday by close of business (5pm CT).
Requirements/Notes. Risks will be monitored, recorded, and assessed using an agreed upon methodology in the Tyler Risk Plan. All risks will be actively monitored by both ▇▇▇▇▇ and Client • ▇▇▇▇▇ will have responsibility for maintaining the project risk plan.