maica.
×
Opal Healthcare proposal portal
This site is intended for Opal Healthcare stakeholders. If you need access, contact alex.hughes@maica.com.au
Welcome. This portal brings together Maica's complete response to Opal Healthcare's request for proposal: the proposed technical solution, the full implementation plan, the commercial model, and everything your evaluation team needs, in one place.
Maica proposes to install its Salesforce-native aged care platform directly into Opal's existing GEM Salesforce org: one environment, one data model, and no synchronisation layer between the resident journey and the new claiming, billing, and funding capability. Dynamics 365 remains the financial system of record, connected through Opal's retained Boomi middleware, while Maica's packaged Services Australia integration handles claiming through the ACWS and B2G channels and is kept compliant with legislative change at no cost under licence.
Delivery follows a phased plan of approximately 137 individually estimated activities, run as four week sprints with a rehearsal-first approach to go live: the complete deployment, data migration included, is executed in a full copy sandbox before it ever touches production. The plan lives in a shared Jira workspace both teams can see at all times, and go live is followed by structured hypercare, with an optional four month extended service supporting Opal's first four month-end claiming and billing cycles.
Commercially, the engagement is a capped time and materials model: Opal controls scope, pace, and priorities, and Maica will not exceed the capped effort without agreement. Licensing converts to an unrestricted site licence, a single organisation-wide fee with no per-user assignment for data access.
The complete response: delivery methodology, the eight phase plan, sprint framework, governance, discovery approach, data migration, security and compliance, and assumptions.
Read the proposal →The ten components of the proposed architecture, from the single org Maica install and D365 integration through to the optional Teams MCP server, plus the single versus two org assessment.
View the solution →The capped effort model, effort and indicative investment by phase, the optional extended hypercare, software licensing tiers, and the commercial assumptions behind the numbers.
Review the costs →Every phase, activity group, and activity with individual effort estimates. Browse the full plan, search across all 137 activities, and see effort by phase at a glance.
Explore the plan →Delivery runs as four week sprints inside this phased structure, each sprint closing with a demonstration against agreed acceptance criteria. The whole plan lives in a shared Jira workspace that Opal can see at all times: scope, estimates, schedule, and progress in one source of truth.
Access to the live Jira implementation plan is provisioned separately; your nominated representative will receive credentials directly. The contents of this portal are confidential and prepared exclusively for Opal Healthcare's evaluation.