Assumptions
1. MuleSoft is responsible for determining appropriate licensing based on flows, data volume and anything else that consumes credits
2. Deployment model will be to Cloud-Hub 2.0 Private Spaces
3. MuleSoft and Kenway to review estimated consumption before contract signing
4. Customer signoff on flow design expected at project handover
5. Does not include any additional licensing costs
6. APIs to retrieve or send data outside of MuleSoft already exist
7. MuleSoft has pre-existing connectors for the source and target platforms
8. Loading / cleansing historical data out of scope
9. Existing components will be reused where appropriate
10. If VPN is required, there will need to be network support on the customer's side to make configurations within their network
11. Changes to source and target platforms to accommodate integrations are not included
12. Does not include HL7 data formats
13. Does not include FTP source or target platform
14. Does not include support and maintenance needs after deployment
15. Source platform has a field that indicates when a record was last modified
Disclaimer: This tool is intended for estimation purposes only and provides a rough approximation of development costs. Actual project timelines and costs may vary.