SIL Location Scheduling
Data model
Object Relationships
Object | Details |
---|---|
|
|
| A |
|
|
| A |
| A |
| A |
| A |
| A |
| A |
| A |
| A |
| A |
| An |
| An |
| An |
| A |
| A |
| A |
| A |
Actions List
Action / Trigger | Sub Action | Details |
---|---|---|
Generate Services |
|
|
| Create Service Batch |
|
| Run Batch | Creates Work Orders and Service Appointments based of the formats defined by the Service Schedules related to the Active Service Templates. |
| Delete Batch Items | Delete related all Child Records |
| Summary | Provide a summary of core records being create as part of the Generate Service Process |
Create Location Contact |
| From an active Service Agreement, if SIL, Create Location Contact at Select SIL Location |
Create SIL Resource |
| When a Service Schedule Resource Count != NULL, Create a SIL Resource record per required resource. |
Create Service Appointments |
| Based of Roster Format select on Location and on Service Schudule and Service Item Resource Count requirements. |
Data model expanded
Location
Field | Details |
---|---|
Type | Defines whether the Location is a SIL Location or normal Location |
Capacity | Defines the number of Participants a SIL Location can service. |
Active Participants | Is a Rollup Summary formula COUNT of Active |
Availability | Is a Formula field: Capacity - Active Participants |
Roster Format | The roster format assigned to the Location. Required for creating Service Appointments reflecting the Shift period. |
Location Contact
Field | Details |
---|---|
Contact | Lookup to related Contact Record |
Full Name | Formula field: Name of the Participant |
Active | Checkbox identifying if the Participant is a Current or Previous tenant |
Start Date | The Date the Participant became a Tenant |
End Date | The Date the Participant left the Location |
Service Agreement | Link the Contact to an active Service Agreement to create Service Schedules |
SIL Resource
Field | Details |
---|---|
Service Resource | Lookup to related Contact Record |
Active | Checkbox identifying if the Service Resource is currently working at the Location |
Start Date | The Date the Service Resource was assigned to the Location |
End Date | The Date the Service Resource was unassigned to the Location |
Service Schedule | Nominate the Service Schedule the particular Service Resource is responsible for delivering services. |
Service Schedule
Field | Action |
---|---|
Service Template | The parent record of this Service Schedule |
Participant | If applicable, the direct Participant this Service Schedule is related to. Based of a Roster of Care |
Interval (Days) | Used in scheduling to define interval/frequency |
Service Resource | If applicable, the direct Service Resource responsible for service delivery |
Resource Count | If applicable, the number or Service Resource required to deliver this Schedule |
Roster Format | If applicable, the Roster format that this schedule related to - inherited from Location |
Location Schedule | A Checkbox that defines if Supports are for indirect assignment. Note, this changes the way Work Orders are created. The date model is similar to multi - participant WOM |
Service Items
Field | Action |
---|---|
Service Schedule | The Parent record this Service Item is the child of |
Support Item | The Support Item from the NDIS Catalogure that is to be delivered |
Day | The day the Support Item is to be delivered |
Start Time | The Start Time the Support Item is to be delivered |
End Time | The End Time the Support Item is to cease being deliverd |
Recource Count | The number of Resources required to deliver the Support Item. |
Description | Additional details about the delivery of this service. |
Roster Format
Other Requirement: Roster Format
DCR has a Roster structure where shifts are structured by month, 24/7 for 7 days on, then 7 days off
February
Resource A: Start Date = Feb 1, 2024 9am, End Date Feb 8, 2024 9am
Resource B: Start Date = Feb 8, 2024 9am, End Date Feb 15, 2024 9am
Resource A: Start Date = Feb 15, 2024 9am, End Date Feb 22, 2024 9am
Resource B: Start Date = Feb 22, 2024 9am, End Date Feb 29, 2024 9amVertic needs to create a function that allows these resources to have one Service Appointment for the 7 days, but it be able to cover many
Service Items
.Consider a checkbox called
Location Item
and ifLocation Item = TRUE
Then it is part of the 7-day roster formatIf False, it is an independent Service Appointment