I work with the following objects- Services, Service Schedules, Service Sessions. The scenario is marking classroom attendance for kids enrolled in after school programs. In this case, the service is 'marking attendance', service schedule is the classroom (identified by location and academic session), and service session is every single day that the service is delivered (attendance is marked every single day the class meets).
When a student is added to a service schedule as a service participant, a program engagement record is created against that student. I'm trying to understand the difference between service delivery and program engagement. Is service delivery a record created for every single service session?
Also, am I correct in my understanding of the hierarchy?
Initiative > Program > Service > Service Schedule > Service Session?
@* Salesforce Administrators * @Nonprofit Hub
#ProgramManagement@Nonprofit Success Pack @Program Management Module (PMM) @All About AppExchange
Hi @Apoorva Mahale!
>> Re: am I correct in my understanding of the hierarchy? Initiative > Program > Service > Service Schedule > Service Session?
Here is the ERD for PMM in NPSP (wow that's a lot of acronyms): https://help.salesforce.com/s/articleView?id=sfdo.PMM_ERD.htm&type=5
Notes:
- Note that there is now a second ERD for Nonprofit Cloud, similar data model but it's built on a different product, so disregard that one.
- Also note that those are the default object labels, and your organization miiiiight have had at least one label change (e.g. the Programs object being relabeled to 'Initiatives')
>> Re: I'm trying to understand the difference between service delivery and program engagement. Is service delivery a record created for every single service session?
Some definitions:
- A student should have an overall program engagement for any program (Initiative). That's where participation/delivery information is aggregated for their total participation in a program across multiple services, schedules, benefits, etc. It also tracks their status in the program. Typically you only need one program engagement per Program+Contact, but you might have multiple if the student goes through a particular program multiple times.
- A student's service participant record is the most confusing! But it is necessary. It's basically their registration for an overall schedule -- and only for that one schedule. (it works with some of PMM's custom interfaces for signing people up for recurring classes)
- Then, as Terry said above, Service Delivery is participation in the specific class session on that day (or in the context of other types of programs and services, it can show that they received a specific benefit and in what quantity. This is why you can have 'service deliveries' without any 'service participant' record).
