Constraints and Assumptions. The Professional Services Fees for the Conversion Project contained in this PRDA are a good faith estimate of the effort required to complete the Conversion Project. If the quoted tasks are at risk of exceeding the specified fees, Fiserv will elevate the issue to the Client’s management for discussion and developing alternatives to contain the scope and fees to the agreed upon level. Three file cuts are included in the Professional Services Fees for the Conversion Project. The first file cut is for the initial testing, mapping, and internal verification. The second file cut is for a standard mock conversion/merge, data verification and card re-issuance purposes. The third file cut is for the live merger. In Fiserv’s discretion, multiple runs against each of the three test files will be done to verify and test the conversion. One full test run (consisting of 3 file cuts) is provided in the estimate. The Professional Services Fees for the Conversion Project are based on Client and CBK being on the same release levels of the application software. This estimate does not include conversion of the VRU application and related information residing on the InterVoice hardware. This estimate does include conversion of all VRU records residing on the CBK CBS Host system. Client will establish all new common file values on their production BNKPRD to support the CBK accounts. This must be completed at least one month prior to the data verification date outlined in the Project Plan. All ACH Common File and customers from CBK must be manually set up in the Client’s environment, however, ACH transactions contained within CBK’s ACH warehouse will be merged with Client’s ACH warehouse. Client’s data will remain with all of its original information and no specific data changes of Client’s data will be required, except that Fiserv will accommodate requests to data changes which, in Fiserv’s sole opinion, are reasonable under the base project. Such requests may necessitate the need to establish additional environments which may result in additional costs. The reserved merger date will be mutually agreed upon between Fiserv and Client prior to the project kick-off meeting, provided however, that in no event will it be earlier than five months from the date of signing this Amendment. The Client will provide, at Client’s expense, high-speed connection to Client’s system during the conversion to facilitate the processes, and communication between Client and Fiserv. Whenever possibl...
Constraints and Assumptions. 1. The City of Milpitas will switch to standard Cayenta Support after the Transition Support period as outlined in the Project Plan.
Constraints and Assumptions. Constraints and Assumptions identify any deliberate or implied limitations or restrictions placed on the project along with any current or future environment the project must accommodate. These factors will influence many project decisions and strategies. The potential impact of each constraint or assumptions should be identified here.
Constraints and Assumptions. 1. Milpitas will provide a copy a snapshot of their PROD database for the creation of the QA environment in Vancouver.
Constraints and Assumptions. 1. Milpitas will conduct all End User training using in-house staff.
Constraints and Assumptions. The basis for all the UNIVERUS deliverables during this phase will be from the UNIVERUS and CITY developed project methodology.. • All project resources will be in place by the end of this phase and will be dedicated for the duration of the project as defined by the Project Schedule. • Software installation will be completed in time to support the System Overview training following the Kick- off session. • From phase start to Kick-off is scheduled to occur within 2 months.
Constraints and Assumptions. The City has the facilities and equipment necessary to effectively deliver end-user training. • The City trainer(s) will be included as members of the Core Team so that they can learn the Solution through Discovery, Custom Development and Testing to be well acquainted with the system prior to delivering the training to end users. • UNIVERUS will provide a Train-the-Trainer approach to complete the end-user Training. • UNIVERUS will support the City with the development of the end-user training plan. UNIVERUS will provide end-user training materials that can be modified by the City to meet the specific needs the configured and modified Solution. • The City is responsible for prerequisite education and training such as basic PC skills, MS Windows training, and/or fundamental business process knowledge of the business processes. • The City will modify, with guidance from UNIVERUS, the standard training plan and training materials to reflect the City’s specific business process activities that will performed in the Solution. • The City has the facilities and will provide the necessary logistics support for all training sessions, including: class schedules, meeting rooms, training rooms, material reproduction, overhead projectors, training workstations, and any other necessary training supplies. • The City will ensure end-user attendance at training. • End-user training will be the joint responsibility of the City and UNIVERUS with the City leading the training and UNIVERUS assisting. • UNIVERUS and the City will jointly develop the training plan for training specifically identified in this SOW or separately contracted for. • UNIVERUS and the City will jointly deliver the training to the end-users.
Constraints and Assumptions. 1. All prices are quoted in US dollars.
