Agreement - Software & Licence - Fleet & Asset Management Software - CCG Systems Inc. dba FASTER Asset Solutions

Home Browse Search

in Schedule A. The Soft Go -Live instance is tested in the FASTER data center and then deployed to the Customer's single environment that serves as the Customer's test environment during the implementation and will become the production environment upon Go -Live. This permits the Customer to perform whatever tests it deems necessary in the later environment to which it will have access. The Customer having one environment through the life of the implementation that will be promoted to production is a critical aspect of quality control that is a distinctly important part of the FASTER COTS implementation process. Any deviation from this may lead to additional cost. This process also reduces Customer IT expenses. While custom work product (if any) is built to specific customer -identified specifications, the nature of COTS software requires that FASTER will not provide custom modification, code changes or database structure changes to any COTS software since this could adversely affect other customers. FASTER does enhance the COTS software as part of its normal life cycle based on customer input from its more than 370 customers, market research and on -staff fleet professionals. b. Integrations & Business Intelligence Work Approvals & Testing: This work represents integrations and business intelligence for which the Customer has provided specifications. The following process will be followed to ensure that reliable work is delivered as part of the implementation: If the Customer has opted in the SOW to use an existing document or file (such as an existing report) as a template for the work to be done, in order to avoid the cost and time involved in the creation of written requirements, there will not be a requirement approval process outside of what is documented in the SOW. Or if the SOW calls for requirements to be documented during the implementation: After the Customer provides the following documentation, FASTER will create an extensive Requirements Document for the Customer to approve. This document will enable the Customer to have certainty about what it requires for a successful customization. Documents to be provided by Customer: • In the case of a Custom Report, a mockup in Excel or similar table. In the case of an Integration, a Data Flow Map which will show the data the Customer wants to import and/or export. • A written summary of: o Execution of the integration: How should the integration be executed? For example, would it need to be run manually or scheduled to run automatically. o User Interface: Will a user interface be needed? If so, what are the key elements needed in the user interface? o Error Handling: How should errors be logged? Are there any specific errors or failures that could occur that would need the integration to notify the Customer about?