The PosiEd/Education Cloud architecture looks like this:
...
As you can see, each layout layer builds on and depends on the layer below. Here is a description of each of the Posimente components.
...
Sometimes referred to as PosiEd Core. This is the primary PosiEd application. It is a managed package that includes most of the PosiEd objects (Refer to Data Dictionary) and defines the PosiEd namespace, as well as the following features (either currently or planned):
Cohorts - Class Groups, Cocurricular Co-curricular and Excursions (complete)
Sessions/Mark Roll (complete)
Student, Staff, Cohort, Asset and Multi-Calendars (complete)
LMS Integration (planned)
Student Comms - SMS & Email (scoping)
Timetabling (complete)
Emergency and Medical (planned)
Billing (planned)
This package is about to be submitted to has passed the Salesforce for security review. It has no dependencies other than Salesforce Sales Cloud.
...
It builds on top of the PosiEd app and adds support for a variety of functions necessary for running Australian K-12 schools including the following features (either currently or planned):
...
It has dependencies PosiEd, PosiEd K-12 and EDC.
PosiEd Wellbeing Config (planned)
This is a set of unmanaged code, config and other resources designed to support student and staff wellbeing processes. It includes a number of unmanaged automations and features that can be modified by clients to support specific requirements on top of the standard PosiEd package.
It has dependencies PosiEd.
PosiEd State Level Config (planned)
Each Australian state school system and some other school systems such as certain private school groups share many common requirements. As these are developed they will be added to config and code scripts for each. (planned)
