Getting started with Maica
- Jan Tenenberg
Maica is principally based on the Salesforce platform (Professional Edition and above) as outlined in the below diagram. It's important to understand that any organisation, nonprofit or not, can utilise the features offered by the Nonprofit Success Pack, in particular Relationships and Households, although this is not a required component of the Maica solution.
Our solution utilises a range of standard Salesforce data objects to enable user access to all Salesforce features as well as other functional solutions to sit side-by-side by the NDIS management platform.
The key data objects being used by Maica are listed below with a description of their purpose and relationship to other data elements within the solution.
Contact: represents a person, such as client, partner, supporter, referrer, guardian, etc
Account: represents an organisation, such as service provider, commercial partner, household, etc
Opportunity & Opportunity Product: tracks any potential revenue, such as service agreements, product sales, etc
Product & Price Book: defines the underlying product structure from the NDIS, including support category, support item number, purpose, etc
Case: represents any incoming enquiry, complaint, issue as well as a set of support coordination features
Service Contract: represents the actual delivery contract once a service agreement (via opportunity) has been finalised
Plan: represents the overall NDIS plan for a participant which is automatically synced from the NDIA via their APIs
Plan Budget: represents a plan's recorded budget items which are automatically synced from the NDIA via their APIs
Service Booking: represents a support category budget which can be created/amended directly from within Salesforce; also automatically synced to the NDIA
Booking Item: represents the individual budget items within a service booking which can be created/amended directly from within Salesforce
Invoice: represents the mechanism of entering completed services (either internal or external) which require automatic claiming from the NDIA
Invoice Line Item: represents an individual support item (product) which is to be automatically claimed from the NDIA
Payment Request: represents the mechanism for submitting an automated claim to the NDIA and triggering payment (once approved)