Both PosiEd and Salesforce Education cloud Cloud are designed with one primary purpose in mind, to put the student first and foremost.
To that end both architectures are designed to provide immense levels of flexibility and detail to support even in the most complex multi school, multi campus environments. In most platformsmany SIS applications, offering students flexibility to do things like enroll in more than one campus at a time, to move between classes without interrupting academic assessment, to provide innovative core course structures such as IIB and RTO . In in addition to HSC etc., have all come to the come with the price of compromise when it comes to the architecture and storage of data records on those students. Schools Many schools often resort to notes and separate records applications to keep track of the the sometimes complex details.
PosiEd and Education Cloud is are designed to cater for as many of these challenges as possible. With this in mind, please understand that as you review the architecture . Some some of the architectural choices might not immediately appear obvious, so change that to the reasoning behind some of the certain architectural choices may not immediately appear obvious. There is a far greater depth of consideration for providing are highly flexible Student Record This can be part of the challenge of providing a highly flexible student record keeping architecture that will accommodate even the most complex School school environments and unique needs.
...
Below is a slightly stylized version ERD of a typical student. Note that it does not include other capabilities that are delivered on top of the standard PosiEd in and K-12 applications such as well-being, academic assessments, etc. At this point, we are just reviewing the core requirements.
...
The students and their
...
Family
The 1st first and most obvious record is to create Contact Record for the student themselves, so change contact to person accountthe student’s Person Account record. Here you will populate the student's primary contact details. Note that you do not yet have to specify anything related to items such as their grade level. Househouse, etc. This will come later.
The second step is to create Person Account records for their family and career carer contacts. These can be associated with the student contact via contact, contact relationshipsContact/Contact Relationships. Review how relationships are to be optimally configured. How the cascading of contact details will work and how data import of these relationships can occur?
Billing Account
A Billing Account record should then be established. This is an account of type billing account Billing Account and this is the level at which all billing for one or more students to a single bill , payer is made. It is also the point at which Contract contract associations, etc., are made.
Once the billing account Billing Account record has been created on the student account , link the Student Account record link to the bill.Billing Account. [Under Development]
Academic Term Enrollments
An Academic Term enrollment Enrollment associates a student with a particular Academic Term. While some information about a student's enrollment history with an educational institution is held by the student record. It Student Record, this object is not granular enough Academic for academic term/grade level analysis. Academic term enrollments Term Enrollments are typically also used to drive enrollment billing functions.
Each year, the student should have a new Academic Term Enrollment record created for them and these records will also consequently be associated with Course Offering Participant Recordsrecords, which in turn are associated with cohort members Cohort Members.
Other Accounts Record Types
PosiEd and EDC require a number of account record types to be configured, including Grade Levels, House, Tutor role group /Roll Group and so on. [There (there are others such as Department Educational Institution, etc., but these are not relevant for this discussion.])
A common question as is to why some of these entries are - Why are these entities set up as accounts Accounts as opposed to simple pick lists for example. ? The reason is that account associations Account relationships provide a more flexible and long-term recording of various associations. It allows you to, for example, see that a student moves from roll group moved from one Roll Group to another which is something that you can't see with just a pick listpicklist.
These associations also provide better reporting such as Generating the program term application timeline in brackets [PTAT]generating the Program Term Application Timeline (PTAT) reports. Note check on review this.
These count Account records need to be set up prior to establishing student records Academic Student Records and Academic Term Enrollments.