From inception to date, Fedena’s Timetable module has been helping schools and colleges of various sizes schedule and manage timetables. The Timetable module has evolved since Fedena’s inception in 2009. After three major Fedena releases, a number of minor releases, many enhancements, and bug fixes, the Timetable module has come a long way. Thanks to our customer feedback and employee input, we have been able to enhance the experience for our users with every release.
How good it used to be
When Fedena was introduced back in 2009, the Timetable module was one of our major selling points. Then, the Timetable module allowed institutions to create only one timetable. This timetable had to be followed by all batches in the institution. This meant, for all batches, every period had to begin and end at the same time. Though institutions liked how easy it was to create a timetable, it soon became a challenge when each batch had different period timings and needed their own timetable.
For those of you who have been with us from the start, here’s a hazy image that might bring back some good memories, and some not so good ones as well.
A point I must add, from the very beginning, Fedena’s user experience has always been one of our top priorities. Even back then, the Timetable module was easy to use and included the smooth drag and drop functionality what you see today.
How better it became
With releases that followed, the Timetable module quickly evolved. Soon features such as the ability to create a timetable for each batch, define the workdays in a week for each batch, together with a few cosmetic enhancements were introduced. By now the Timetable module was gaining popularity among users. This is what the Timetable module looked like back then.
Then, with the release of Fedena 3.0, we introduced the concept of ‘class timings’. Class timings allowed institutions to define the number of periods and the duration of each period in a workday. The class timings were then automatically applied to all workdays of the week. Though this gave institutions a little more flexibility when creating timetables, it later brought about the question of ‘What if for a batch, periods begin and end at different times on each workday?’
The best yet…
As an answer to that question, we introduced ‘class timing sets’. Similar to the concept of ‘class timings’, a ‘class timing set’ defined the number of periods and the duration of each period in a workday. The difference was, institutions were now able to assign a unique class timing set to each workday. This brought about a small change in the workflow of creating a timetable. Here’s the current workflow to create a timetable.
In addition to all the enhancements, we also managed to give the Timetable interface a facelift, as seen in the image below.
All these features put together now offer institutions even greater control over the timetables they create. Today, Timetable is one of the most used modules by Fedena customers. And to let you in on how we plan to improve the Timetable module, we’re now working on ways to automate timetable generation to enable you create timetables even faster. So stay tuned for upcoming releases.
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?