Opening of Proposals - Utility Billing System - Systems & Software, Inc. - Part 2

Home Browse Search

Systems " pr 2018 Systems & Software Support Program Guidelines & Software Product Changes and Enhancements Maintenance Releases: Our main priority in regards to maintenance releases is production environment stability. Our methodology allows customers to on a specific version level between upgrades but also have the ability to be on the most current version "head" level; this allows us to maintain a single set of source code for each of the supported enQues,ta versions. The thought is customers can stay on "their" level and opt to take releases as they are, made available; never take a release unless as required for a speidfc modification they want/need; or remain on "their" level until they opt to move forward with an upgrade. ALL customer sources will be managed' at S&S. Each developer will follow a defined standard processes for deployments of required code. The MR creation process will be an automated process versus requiring a manual tag movement which has been a root cause of issues with deployments (to date, because of the manual requirement, human error has resulted more times than not); We will only be delivering code enhancements/fixes which will result in MRs comprising of about 25 TTPs to test. Modifications/Quote Requests: S&S requests that in cases of specific custom requests (modification, customization, new features, new interfaces, and enhancements) from a customer, the entire scope of such a request should accompany the inquiry. A TTP will then be created and S&S will then validate the written scope document. A Business Requirements Document (BRD) will accompany the Quote document as required. S&S requires sign -off on both the BRID and quote document to officially begin work. A maintenance release is typically required for all new functionality. S&S will notify the customer as to which maintenance release the new functionality will be part of. As with all maintenance releases, the deployment will first be delivered to the customier's Test/Train environment, Once successfulfly tested, the maintenance release will then be deployed to the customer's Production environment. If the modification requested does not require an MR, it is expected that the customer will test the modification in their train environment within 30 days of receipt. When a modification remains in a customer's train environment beyond 30 days, there is a risk of the work being over -written by the deployment of MRs, train refreshes, other code deployments, etc. After the new functionality has been delivered to the customer's Test/Train environment, the remaining invoice amount will be billed. *Please note that if a maintenance release is required for this new functionality, the customer must be up-to-date on, their maintenance release deployments, 4 CONFIDENTIAL Systems & Software 426 Industrial Avenue Williston, VT 05495 www.ssivt.corn, p: 802-865-1170 IF: 802-865-1171 Page 14