# BasicScheduleModel

**URL:** <https://forum.inductiveautomation.com/t/basicschedulemodel/93645>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [July 24, 2024, 5:13am UTC](https://forum.inductiveautomation.com/t/basicschedulemodel/93645 "2024-07-24T05:13:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Booth](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_booth/32/82019_2.png) [@Steve\_Booth](https://forum.inductiveautomation.com/u/Steve_Booth)\
**Post date:** [July 24, 2024, 5:13am UTC](https://forum.inductiveautomation.com/t/basicschedulemodel/93645/1 "2024-07-24T05:13:08Z")

</div>

I'm considering the perspective implementation of the Ignition scheduler downloaded from Igntion Exchange [Ignition Exchange | Inductive Automation](https://inductiveautomation.com/exchange/2144/overview)  
It uses the class  
[com.inductiveautomation.ignition.common.user.schedule.BasicScheduleModel](https://files.inductiveautomation.com/sdk/javadoc/ignition80/8.0.12/com/inductiveautomation/ignition/common/user/schedule/BasicScheduleModel.html#set(com.inductiveautomation.ignition.common.user.schedule.BasicScheduleModel)) .  
Unfortunately the options for repetition are limited to 'off', 'daily' and 'weekly'. I need to add 'monthly' and 'yearly' frequencies. I have considered scripting these special circumstances and generating a limited number of manual set() commands with frequency of 'off' but it is messy and confusing for the user. Any thoughts on how I could modify the class to add additional frequencies. Or should I look at creating my own custom scheduler.  
P.S\> The funny thing is that the related class [com.inductiveautomation.ignition.common.user.schedule.HolidayModel](https://files.inductiveautomation.com/sdk/javadoc/ignition81/8.1.20/com/inductiveautomation/ignition/common/user/schedule/HolidayModel.html) includes annual repetition

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/a/da05e5b9dd7edd9dee6e218e7898cd498450f584.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b5b4ba01f91d31061389ff8bee6aae3e5a8565f3.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/4/942e5fdaf8135b4b0a9e4735931180aff582745c.png)

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [July 24, 2024, 3:47pm UTC](https://forum.inductiveautomation.com/t/basicschedulemodel/93645/2 "2024-07-24T15:47:41Z")

</div>

You could definitely create your own module to add a new schedule type -- schedules are [extension points](https://www.sdk-docs.inductiveautomation.com/docs/programming-for-the-gateway/extending-ignition-with-extension-points/).

Schedules and holidays have different repeat types because for the vast majority of our users they repeat differently. Workers often have the same schedule every week (or on alternating weeks) while holidays often repeat annually.