This page outlines our collaborative approach to supporting the integration of Praxedo with your existing business systems. We recognize that effective integration is essential for optimizing your workflows and data management. Our role is to provide expert guidance and API support to your integration team, ensuring a streamlined and successful integration process.

1. Business Process Analysis & API Access

Our collaboration commences with a comprehensive business process analysis. We'll work closely with your team to understand your core business processes, current system ecosystems, and desired information flow. This initial phase also includes providing your integration team with access to our API documentation, facilitating early technical understanding.

Key Deliverables:

• High-level data flow diagram.
• Roadmap for integration, clearly identifying which flows are critical for UAT, critical for go-live, and nice to have after go-live.
• Access to Praxedo API documentation provided to the integration team.

2. Detailed Field Mapping

Following the initial analysis, we'll conduct a dedicated session to define the precise data transfer requirements. This meeting focuses on meticulous field mapping, clarifying the source and destination systems for each data element to ensure accuracy and consistency throughout the integration. This is an iterative phase, as progress made in configuring the application will lead to additional fields / needs to be considered. It is therefore important to design the integration with flexibility in mind, especially when it comes to custom fields and/or forms report fields. The deliverable of this session will also serve as a support for the UAT phase of the integration project.

Key Deliverables:

• Detailed field mapping document, for each object / data flow.

3. Timeline, Milestone Planning & Prioritization

We'll collaborate with you and your integration team to establish a realistic timeline and define key milestones. During this phase, we'll consider the prioritization of data flows, your desired timeframe, and the development effort required from your integration team, ensuring a well-managed project. It is important to notice that any delay in the integration process, more specifically on the flows considered critical for UAT or go-live, will have a corresponding impact on the go-live date of the whole project.

Key Deliverables:

• Project timeline with key milestones

4. Weekly API Support Meetings

To ensure consistent progress and address technical inquiries, we'll schedule weekly meetings between your integration team and a dedicated Praxedo API expert. This expert will provide guidance and support regarding our API, ensuring your integration team remains aligned with established milestones. A best practice is to share your questions ahead of the meeting, so that our expert - and our configuration lead if necessary - may come prepared.

Key Deliverables:

• Meeting minutes with action items.
• Regular progress updates against the timeline.
• Resolution of technical questions related to the Praxedo API.

5. Test Plan & Test Case Design

Upon the integration team's completion of initial development, we'll collaborate with your team to design comprehensive test cases and a detailed test plan. This crucial step ensures that the integration will be thoroughly validated against your specific requirements and expected functionalities.

Key Deliverables:

• Test plan and test cases.

6. User Acceptance Testing (UAT) & Final Modifications

With the test plan and test cases in place, your team will conduct User Acceptance Testing (UAT) to ensure the integration functions as intended and meets your business needs. During this phase, we'll provide support for any necessary modifications or refinements identified during UAT to achieve a fully optimized and validated integration. Successful UAT marks the completion of the integration phase.

Key Deliverables:

• Documentation of UAT results and identified issues.
• Support for final integration modifications.
• Confirmation of successful integration validation.

7. Go-Live Readiness & Roll-out

Prior to launch, we will conduct a go-live readiness assessment to verify that all key functional requirements outlined in the initial blueprint have been fulfilled. On the day of roll-out, our team will block off our calendars to provide immediate support and address any issues that may arise. A designated meeting link will be available for quick access to our support team as needed.

Key Deliverables:

• Completed go-live readiness checklist.
• On-demand support during the go-live period.

8. Post Go-Live Support

Following the go-live date, we will provide a period of dedicated support to ensure a smooth transition and address any initial issues.

Post Go-Live Activities:

• Weekly meetings for two weeks to review any questions and track outstanding requests.
• Maintenance of an action register to document and resolve any post-go-live issues.
• Transition to Customer Care as the primary point of contact for ongoing support.