Discovery and Design
1.1 Discovery. Services Provider will work with Customer to document the Automation Solution's purpose; material inputs, outputs, and data categories; third-party dependencies; systems and actions the automation is authorized to access or perform; human-review and approval points; anticipated volumes; and Acceptance Criteria. That scope is stated in the applicable Order Form or in a Build Specification identified in and incorporated into it
1.2 Design Changes. A material change to that scope after the Order Form is signed requires a Change Order.
Back to contentsBuild And Revisions
2.1 Revision Rounds. The applicable Order Form or Build Specification states the number of revision rounds included in the build Fee. A revision round consists of Customer's consolidated written feedback on a delivered build and Services Provider's corresponding update. Additional revision rounds beyond those stated there are a Change Order.
2.2 Out-of-Scope Requests. A request that would change the Automation Solution's fundamental scope, architecture, or data flows, or add a new system integration not described in the Order Form or Build Specification, is out of scope for the build Fee and requires a Change Order or new Order Form, regardless of whether raised during a revision round.
Back to contentsAcceptance Testing
3.1 Test Environment. Where the Order Form or Build Specification so states, Services Provider will make the Automation Solution available in a test or staging environment for Customer's review against the Acceptance Criteria before requesting acceptance under Section 5 of the Agreement.
3.2 Test Data. Customer will provide test data or access sufficient for Services Provider to validate the Automation Solution against the Acceptance Criteria. Services Provider is not responsible for a delay in acceptance testing caused by Customer's failure to provide adequate test data or access.
Back to contentsCredentials and Access
4.1 Provision. Customer will provide only credentials and access rights that it is authorized to provide and that are reasonably necessary for the build. Credentials and secrets must be delivered through a Services Provider-approved secure method and not through ordinary email or an unapproved shared chat channel.
4.2 Use. Services Provider will use Customer-controlled credentials solely to perform the build, apply least-privilege access, and restrict access to authorized personnel.
Back to contentsHandoff for Operation
5.1 Vectra View-Hosted Automation Solutions. Where the applicable Order Form states that the Automation Solution will be hosted and operated by Vectra View, Services Provider will complete the build and provide the proposed Operational Specification for Customer's approval under Schedule B to the MSSA. Hosted operation is governed by that Schedule.
5.2 Customer-Environment Deployments. Where the applicable Order Form states that the Automation Solution will be deployed into Customer's own environment, Services Provider will deliver the build together with deployment instructions. Any license to use the Automation Solution in Customer's environment is granted by Vectra View Technologies Inc., which owns it, under the applicable Order Form or separate license terms.
Back to contentsWarranty Period
6.1 Build Warranty. For thirty (30) days following acceptance under Section 5 of the Agreement (the "Warranty Period"), Services Provider will correct, at no additional charge, a reproducible failure of the Automation Solution to conform to the Acceptance Criteria, provided the failure is not caused by a change to Customer's environment, an outage, defect, or change in a third-party dependency outside Services Provider's reasonable control, or data outside the categories described in the Order Form or Build Specification. Correction of a nonconformity identified after the Warranty Period, or caused by an excluded cause, is a Change Order or new Order Form.
6.2 Interaction with Support. Where the Automation Solution is hosted by Vectra View and an Automation Solution support package under Schedule D to the MSSA becomes active before the Warranty Period ends, Section 6.1 continues to govern conformity to the Acceptance Criteria, and the support package governs bug fixes, maintenance, and dependency management as stated in Schedule D.
Back to contents