SYSTEMS & SOFTWARE, INC. 1B (2) - 2016

Home Browse Search

Project Responsibilities For a project of this nature and in order to ensure a successful enQuesta upgrade, it is necessary for the Customer and S &S to work cohesively as a team. To achieve this goal and set the proper expectations regarding roles and responsibilities, the Customer and S &S will each maintain a set of project duties. Customer Responsibilities I. The Customer will name a dedicated Project Manager to serve as the primary Customer point - of- contact for this project and represent the Customer on the necessary project planning and implementation tasks and responsibilities. II. The Customer will name an Executive Sponsor and provide Functional Subject Matter Experts for duration of project. III. The Customer will work with S &S to identify requirements for those business procedures that have been modified since the last enQuesta Go -Live. Note that changes in process not supported by enQuesta may result in changes in project scope. IV. The Customer will ensure that the current enQuesta data environment is clean prior to the data conversion to enQuesta v4.5. The Customer will provide the first data cut. The Customer's data cleansing activities must be completed by the beginning of the second conversion test and include fixing all "bad" records identified during the initial conversion process. Bad data elements are identified as Eager and Lazy constraints. Eager constraints require correction or errors will exist within the enQuesta portal when an account is accessed. Clean data also entails completing end of day enQuesta tasks, such as work order, hand held, cash, and credit and collection run sheets. Except for the billing run sheet, where S &S will provide specific instructions on how and when to do a data cut so that we are able to do a billing parallel data validation test, clean data generally entails that there are no open batches in the system and that any daily/ weekly/ monthly and interface run sheets have been completed if they have been started. Run sheets, save for billing, should be complete by the beginning of each data cut and conversion. S &S will provide specific instructions and documentation on how to prepare your existing environment and how to execute a data cut for each data conversion. V. Prior to the first conversion, the Customer must have the latest MR in their production environment. VI. The Customer will participate in data conversion/ data validation through the use of existing enQuesta version to enQuesta v4.5 comparisons and then by reviewing specific reports. VII. The Customer will provide formal sign off (sample sign -off documents provided in Appendix D) on project related documents and deliverables including: Business Requirement Documents as required, Testing, Training, Simulation, Go -Live, 30 Days Post Go- Live /System Acceptance. Sign -off is required within 5 days of the completion of each milestone event unless a showstopper issue has been clearly identified, documented and agreed upon by both parties. VIII. The Customer maintains primary responsibility for the testing of enQuesta functionality once deployed to the Train environment. The Customer is responsible for creating and executing a set of Test Cases that will ensure the system is tested thoroughly by the Customer prior to Simulation. IX. The Customer is responsible for ensuring that key personnel and users have successfully completed end -user training offered remotely and /or onsite. The Customer bears the responsibility for any and all travel and living related expenses for customer personnel. S &S has provided a travel budget based on estimated number of trips. City of Santa Ana - enQuesta Upgrade Statement of Work Page 16 of 32 Proprietary and Confidential to Systems & Software, Inc. 2/16/2016 Document subject to the California Public Records Act