Axtension Content Gate – SoW
1.
SERVICES
The Supplier commits to assisting the Customer in implementing the Software for one (1) company within the Customer's environment by providing the following Implementation Services at the price specified in the Agreement.
- Start-up Meeting
The Supplier will schedule a Start-up meeting to discuss the implementation methodology, roles, and responsibilities, align the project scope and plan with the Customer. - Technical Meeting & Preparations
The Supplier will arrange a technical meeting to make sure the technical requirements and dependencies are fulfilled. - Design Workshops
The Supplier will arrange a workshop for the Customer. The purpose of the workshop is to gather information for how to configure the Product. - Configuration
The Supplier will set up and configure the Software according to best practices and decisions made during the workshop. The Software will be configured in all requested non-production environments for one (1) company. If the Customer requires assistance setting up additional companies, this assistance will be provided at the Supplier's Consultancy Services rate specified in the Agreement.
The fix price configuration will be limited to: - Super User Training
The Supplier will conduct training and instruct the Customer for how to use the Product. Additional training, if requested, will be provided at the Suppliers’ Consultancy Services rate specified in the Agreement. - Follow up sessions
The supplier can request periodic follow up sessions to discuss topics which might come up during the implementation. The supplier owns the agenda and preferably communicates the topics up front. - Project management
Project management includes the coordination of resources, timelines, and objectives, as well as facilitating kickoff calls, progress calls, internal communication, and monitoring project progress to ensure seamless collaboration, timely delivery, and the successful realization of project goals.
-
Connect with standard modules of Dynamics 365 Finance and Operations, assuming that there are public data entities available to connect with*.
-
Connect with standard entities of Dynamics 365 CE, assuming that there are public data entities available to connect with*.
*See for more information chapter 2 chapter vii.
2.
CUSTOMER RESPONSIBILITIES
The successful delivery of Implementation Services by the Supplier relies on the active involvement of the Customer and the Customer’s provisioning of reasonable assistance. Therefore, it is the Customer’s responsibility to:
- Deployment
Ensure the deployment and activation of the Software in accordance with Microsoft standard procedures. - Project Management
Assign a project leader from within the Customer's organization responsible for example allocating resources, managing work related to the implementation of the Software, and serving as the primary point of contact for all communication with the Supplier and arranging a remote connection for the Supplier to the Customer's environment. - Resources
Ensure that an adequate number of qualified personnel from the Customer's organization are present and available throughout the implementation and testing phases. - Standard Dynamics 365 Finance and Operations and Dynamics 365 Customer Engagement Setup, Master and Business data
Ensure that the Customer’s standard Dynamics 365 Finance and Operations and Dynamics 365 Customer Engagement Setup and Configuration are done according to agreed requirements and contains correct Customer’s Master & Business data. - Azure basic setup
Ensure that the necessary preparations are met related to the basic Azure setup. - Data entities
If the standard D365 data entities are not sufficient, it is the customers responsibility to create custom data entities. - Content Gate connector version
Ensure that the latest required Content Gate connector version is deployed on Dynamics 365 Finance & Operations and Dynamics 365 Customer Engagement. - User Acceptance Testing
Conduct thorough User Acceptance Testing (UAT) to validate the functionality and performance of the Software, ensuring alignment with the specified requirements and objectives. Promptly inform the Supplier of any defects found in the Software or its implementation during the Customer's acceptance testing. - User Acceptance Sign-Off
Upon successful completion of user acceptance testing in the Customer's test environment, the Customer shall formally accept the delivery of the Software. This acceptance shall be verified in writing, confirming that the Software has been tested and approved. Once the Software is deployed in the Customer's production environment, the Supplier considers its delivery accepted by the Customer.
-
Service principal account
-
Dual write in case both Dynamics 365 Finance and Operations and Dynamics 365 Customer Engagement are being used