Difference between revisions of "Batch Planning"

From JUNO Wiki
Jump to: navigation, search
(Terminologies Used:)
(Step by step)
 
(21 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
Batch is a bunch of students administered to a program from admission year up-to expected passing year.  
 
Batch is a bunch of students administered to a program from admission year up-to expected passing year.  
 +
Suppose a bunch of 60 students is taking admission in a four year course of BE - Comp program, in the academic year 2018-2019 than the batch BE - COMP 2018-2022 will be formed and expected passing year for students would be 2022.
 +
Few student may however have year down and pass later, but for identification the batch will be BE - COMP 2018-2022 as the batch indicates the admission year.
  
(**Suppose a bunch of 60 students is taking admission in a four year course of BE - Comp program, in the academic year 2018-2019 than the batch BE - COMP 2018-2022 will be formed and expected passing year for students would be 2022.
 
 
Few student may however have year down and pass later, but for identification the batch will be BE - COMP 2018-2022 as the batch indicates the admission year**).
 
 
Batch planning allows a user to create future batch/term which can be activated when the semester is active.
 
Batch planning allows a user to create future batch/term which can be activated when the semester is active.
All the batches created remains in planning state once user marks the batch as active the status changes to running and the batches are moved to batch management tab.
+
All the batches created remains in planning state once user marks the batch as active the status changes to running.
  
 
== ''' Roles ''' ==  
 
== ''' Roles ''' ==  
Line 13: Line 12:
  
 
== ''' Path ''' ==  
 
== ''' Path ''' ==  
 
+
Head Admin login >> Academics >> Academics Plan >> Batch Section Planning >> Batch Sections
Academic Admin login >> Planning >> Batch Section Management >> Batch Section Planning >> Batch Sections
 
  
 
OR
 
OR
  
Head Admin login >> Academics >> Academics Plan >> Batch Section Planning >> Batch Sections
+
Academic Admin login >> Planning >> Batch Section Management >> Batch Section Planning >> Batch Sections
  
== '''Terminologies Used:''' ==
+
== '''Terminologies Used''' ==
  
 
* Program: Program is usually similar to qualification but not always. In Engineering colleges, all first year students are allocated to the program "Applied Science" which is a mixed group for teaching basics of Engineering to all specialization. In the second year Applied Science students are distributed to different programs(non-functional departments) like BE - Comp, BE - Civil, BE Mech.
 
* Program: Program is usually similar to qualification but not always. In Engineering colleges, all first year students are allocated to the program "Applied Science" which is a mixed group for teaching basics of Engineering to all specialization. In the second year Applied Science students are distributed to different programs(non-functional departments) like BE - Comp, BE - Civil, BE Mech.
Line 33: Line 31:
  
 
* Programme Name
 
* Programme Name
* Term Name/Semester Name
+
* Academic Batch
* Section/Division Name
+
* Term(Semester) Name
 +
* Academic Session Date
 +
* Teaching Plan Date
  
== <b>Functionality:</b> ==
+
== <b>Functionality</b> ==
* Edit option for term start date and term end date.
+
* Add new future term.
* Students of a particular program can be divided into batches/division/sections.
+
* Edit option to modify already created term.
* Batches/division/sections can be activated and deactivated.
+
* Add, modify or delete division/section.
<b>For a batch / division / section following settings can be configured :</b>
 
  
<b> Primary Functionality :</b>
+
<b> Primary Functionality </b>
* Can change batch status from Running to Planning.
+
* Add new batch.
* Mark running batch as In-active.Would mark the current running batch as Inactive.
+
* Option to configure term as previous section/division.
<b> Miscellaneous Functionality :</b>
+
* Option for fetching bio-metric attendance for student.
* Re-admissions/next year course(subject) choice can be defined.
+
* Define evaluation type.
* Initiate no due process for students.
 
* Can fetch history data for faculty course(subject) allocation and time table.
 
* Can fetch history data for concurrent evaluations.
 
* Allocate students with core course(subject).
 
* Can define other course(subject) choice activity.
 
* Update or modify student course(subject) joining date.
 
* Teacher can add date for marks entry.
 
* Can modify syllabus in case of syllabus mismatch.
 
* Can perform student course(subject) group mapping.
 
* Student course(subject) priority can be mapped.
 
  
<b> For a batch / division / section the following can be configured :</b>
+
<b> Miscellaneous Functionality </b>
* Define source of attendance.
+
* Mark this planned class as active
* Define evaluation parameters like round/ceiling/truncate etc.
+
* Employee choice configuration
* Define SMS/Email configuration settings as to at what regular interval the attendance records should be sent to both present & absent students via SMS/Email.
+
* Fetch previous employee course(subject) allocation and time table
* Define SMS/Email configuration settings for non conduction of lecture.
+
* Fetch previous course(subject) evaluation file
* Define Time slots for marking attendance for theory as well as practical session.
+
* Re-admissions / next year course(subject) choice
* Define SMS/Email configuration settings for alerts to be sent to faculty for lectures(Upcoming lecture,Cancelled lecture &  Adjusted lecture).
 
  
<b> For a Term following can be configured :</b>
+
<b> For a Term following can be configured </b>
* Can add new Division.
+
* Can add new division.
* Specify Division Capacity.
+
* Specify division capacity.
* Define Prefix and Roll number start digit.  
+
* Define prefix and roll number start digit.  
* Can edit or delete Division.
+
* Can edit or delete division.
  
 
== '''Configuration and it's effects''' ==
 
== '''Configuration and it's effects''' ==
 
<b> Primary Functionality :</b>
 
<b> Primary Functionality :</b>
  
'''CASE 1 :- Change to Planning'''
+
'''CASE 1 :- Mark this planed class as active'''
 
* Batches can be created in two states running & planning.
 
* Batches can be created in two states running & planning.
* Running Batch indicates that current batch is active and divisions under same batch are functioning for regular academics.  
+
* Planned batch can be marked active.
* Future term batches can be created with status as planning.
+
* Change the batch state from planning to running.
* Change batch from running status to planning status.
+
* Running batch indicates that current batch is active and divisions under same batch are functioning for regular academics.  
 +
* Once marked as active running batch shall be moved to batch management tab.
  
'''CASE 2 :- Mark it Inactive'''
+
'''CASE 2 :- Employee course(subject) choice configuration'''
* Currently active batch can be marked as inactive.
+
* Enables faculty to give preference for their choice of course(subject).
* If current term is marked in-active, user will not be able to access this term in any academic activity.
+
* Dates can be defined to submit choice preferences.
* Academic session date & teaching plan date should be past dates only then batches can be marked as inactive.  
+
* Announcements for same can be sent to staff.
* Another effect of this functionality is : if user has no batches in planning state and still current batch is marked inactive all the students available in the batch will be automatically be added to fresher student list.
+
* Faculty
  
<b> Miscellaneous Functionality :</b>
+
'''CASE 3 :- Fetch previous employee course(subject) allocation and time table'''
 
+
* This option helps to fetch allocations of course(subjects) to employees of the last academic year in the current year.Pre-condition being the syllabus pattern should be the same in last academic year and this year.
'''CASE 1 :- Re-admission/Next year course(subject) choice'''
+
* The option is available or valid only if there is no new faculty course(subject) allocation done in the time table at all,If their is any allocation done than this functionality shall not work and would throw an exception.
* Enables admission process options for students, say student passing from first year and going to second year, shall take admission again in second year.
 
* Can define next year course(subject) choice for students.
 
* Based on selection of semester, course(subject) selection option gets enabled for students for defined duration.
 
* Admission process fees collection payment mode can be defined. From the given options any combination of payment modes can be configured. Accordingly payment options will be available at the student end. 
 
 
 
'''CASE 2 :- Initiate Student No Due'''
 
*
 
 
 
'''CASE 3 :- Fetch Previous Employee Course(Subject) Allocation and Time table'''
 
* This option helps to fetch allocations of course(subjects) to employees of the last academic year in the current year. Pre-condition being the syllabus pattern should be the same in last academic year and this year.
 
* The option is available or valid only if there is no new faculty course(subject) allocation done in the time table at all, If their is any allocation done than this functionality shall not work and would throw an exception.
 
 
* Although after fetching the employee & course(subject) from past user can edit or modify the same.
 
* Although after fetching the employee & course(subject) from past user can edit or modify the same.
  
'''CASE 4 :- Fetch Previous Course File Evaluations'''
+
'''CASE 4 :- Fetch previous course(subject) evaluation file'''
* The option helps to fetch Course file evaluation parameters from past respective semester.
+
* The option helps to fetch course file evaluation parameters from past respective semester.
 
* For example a faculty may teach “Mathematics” to second year batch odd semester every year, so she can fetch course file evaluation parameters from last year batch odd semester for current running batch in odd semester.
 
* For example a faculty may teach “Mathematics” to second year batch odd semester every year, so she can fetch course file evaluation parameters from last year batch odd semester for current running batch in odd semester.
 
* The evaluation parameters could be Assignment, Quiz, Assessment, Projects, etc.
 
* The evaluation parameters could be Assignment, Quiz, Assessment, Projects, etc.
  
'''CASE 5 :- Student Core Course(Subject) Allocations'''
+
'''CASE 5 :- Re-admission/Next year course(subject) choice'''
* The option enables allocating mandatory course(subject) to all the students available in batch.
+
* Enables admission process options for students, say student passing from first year and going to second year, shall take admission again in second year.
 +
* Can define next year course(subject) choice for students.
 +
* Based on selection of semester, course(subject) selection option gets enabled for students for defined duration.
 +
* Admission process fees collection payment mode can be defined. From the given options any combination of payment modes can be configured. Accordingly payment options will be available at the student end.
  
'''CASE 6 :- Other Course(Subject) Choice Activity'''
+
== '''Step by step''' ==
* This functionality is used for extra credit scores concept.
+
Follow Below mentioned steps
* It helps student select course(subject) other than regular batch.
+
1)  
* Say in an university their are multiple institute with different programs but students from any program are allowed to select any elective course(subject) from options available at university level.
+
[[File:BatchSectionPlanning.png|border|center|frameless|900x900px]]
* Based on student selection the elective course(subject) group would be formed and regular academic process can be carried out.
 
 
 
'''CASE 7 :- Update Student Course(Subject) Joining Date'''
 
* When a batch is created the same date is considered as section joining date for students, from the same date academic begins for students.
 
* This update functionality enables to update student course(subject) joining date.
 
* Assume a student joins section/division a month later after the actual academic session begins, in this scenario the attendance and other activity for this student would start a month later.
 
  
'''CASE 8 :- Teacher/Faculty Marks Entry Date'''
+
2)
* The functionality is used to add dates for marks entering for students.
+
[[File:BatchSectionPlanning(1).png|border|center|frameless|590x590px]]
* Evaluation schema and its parameters can be defined.
+
3)
* For example program BE - COMP has Unit Test of 50 marks and there are multiple parameters for unit test say orals has 10 marks, written is 30 marks and internal assessment is 10 marks. In the mentioned scenario the Evaluation schema is Unit Test and Oral, Written and Internal assessment are parameters for evaluation.
+
[[File:BatchSectionPlanning(2).png|border|center|frameless|900x900px]]
 +
4)
  
'''CASE 9 :- Syllabus Mismatch'''
+
[[File:BatchSectionPlanning(3).png|border|center|frameless|900x900px]]
* Syllabus mismatch is used in case of multiple syllabus allocated to a batch.
 
* In case if a particular batch has replicated copies of syllabus and user wish to delete other mismatching syllabus he may do the same from this option.  
 
  
'''CASE 10 :- Course(Subject) Group Mapping'''
+
5)
* Enables to select existing group of student based on course(subject) group selection and same shall be applied to current term.
+
[[File:BatchSectionPlanning(4).png|border|center|frameless|900x900px]]
* Say in First year (semester 1) of a program you already have group of students created based on elective course(subjects) so by using this functionality you can map the same group in First year (semester 2) for current batch.
 
  
'''CASE 11 :-Student Course(Subject) Priority Mapping'''
+
6)
* Helps in matching course(subject) priority from past semester with current semester.
+
[[File:BatchSectionPlanning(5).png|center|frameless|560x560px]]
 +
7)
 +
[[File:BatchSectionPlanning(6).png|border|center|frameless|800x800px]]
  
== '''Step by step:''' ==
+
8)
Follow Below mentioned steps
+
[[File:BatchSectionPlanning(7).png|border|center|frameless|560x560px]]

Latest revision as of 12:43, 18 November 2019

Batch Planning

Batch is a bunch of students administered to a program from admission year up-to expected passing year. Suppose a bunch of 60 students is taking admission in a four year course of BE - Comp program, in the academic year 2018-2019 than the batch BE - COMP 2018-2022 will be formed and expected passing year for students would be 2022. Few student may however have year down and pass later, but for identification the batch will be BE - COMP 2018-2022 as the batch indicates the admission year.

Batch planning allows a user to create future batch/term which can be activated when the semester is active. All the batches created remains in planning state once user marks the batch as active the status changes to running.

Roles

Head Admin, Academic Admin

Path

Head Admin login >> Academics >> Academics Plan >> Batch Section Planning >> Batch Sections

OR

Academic Admin login >> Planning >> Batch Section Management >> Batch Section Planning >> Batch Sections

Terminologies Used

  • Program: Program is usually similar to qualification but not always. In Engineering colleges, all first year students are allocated to the program "Applied Science" which is a mixed group for teaching basics of Engineering to all specialization. In the second year Applied Science students are distributed to different programs(non-functional departments) like BE - Comp, BE - Civil, BE Mech.
  • Batch: Batch is a Lot of students administered to a program from admission year upto expected passing year. For example a four year course of BE - Comp with admission year 2018 and expected passing year 2022 will have the batch 2018-22 The student may however have year - down and pass later, but for identification batch remains the same.
  • Term Name/Semester Name: In a four year program there can be 8 semesters/term or 12 semesters/term or only 4 semesters/term depending on whether the term is 6 months or 4 months or 12 months.
  • Section/Divisions: In a program BE Comp Batch 2018-22 there can be 3 sections/divisions of 40 students each.

Inputs Needed

  • Programme Name
  • Academic Batch
  • Term(Semester) Name
  • Academic Session Date
  • Teaching Plan Date

Functionality

  • Add new future term.
  • Edit option to modify already created term.
  • Add, modify or delete division/section.

Primary Functionality

  • Add new batch.
  • Option to configure term as previous section/division.
  • Option for fetching bio-metric attendance for student.
  • Define evaluation type.

Miscellaneous Functionality

  • Mark this planned class as active
  • Employee choice configuration
  • Fetch previous employee course(subject) allocation and time table
  • Fetch previous course(subject) evaluation file
  • Re-admissions / next year course(subject) choice

For a Term following can be configured

  • Can add new division.
  • Specify division capacity.
  • Define prefix and roll number start digit.
  • Can edit or delete division.

Configuration and it's effects

Primary Functionality :

CASE 1 :- Mark this planed class as active

  • Batches can be created in two states running & planning.
  • Planned batch can be marked active.
  • Change the batch state from planning to running.
  • Running batch indicates that current batch is active and divisions under same batch are functioning for regular academics.
  • Once marked as active running batch shall be moved to batch management tab.

CASE 2 :- Employee course(subject) choice configuration

  • Enables faculty to give preference for their choice of course(subject).
  • Dates can be defined to submit choice preferences.
  • Announcements for same can be sent to staff.
  • Faculty

CASE 3 :- Fetch previous employee course(subject) allocation and time table

  • This option helps to fetch allocations of course(subjects) to employees of the last academic year in the current year.Pre-condition being the syllabus pattern should be the same in last academic year and this year.
  • The option is available or valid only if there is no new faculty course(subject) allocation done in the time table at all,If their is any allocation done than this functionality shall not work and would throw an exception.
  • Although after fetching the employee & course(subject) from past user can edit or modify the same.

CASE 4 :- Fetch previous course(subject) evaluation file

  • The option helps to fetch course file evaluation parameters from past respective semester.
  • For example a faculty may teach “Mathematics” to second year batch odd semester every year, so she can fetch course file evaluation parameters from last year batch odd semester for current running batch in odd semester.
  • The evaluation parameters could be Assignment, Quiz, Assessment, Projects, etc.

CASE 5 :- Re-admission/Next year course(subject) choice

  • Enables admission process options for students, say student passing from first year and going to second year, shall take admission again in second year.
  • Can define next year course(subject) choice for students.
  • Based on selection of semester, course(subject) selection option gets enabled for students for defined duration.
  • Admission process fees collection payment mode can be defined. From the given options any combination of payment modes can be configured. Accordingly payment options will be available at the student end.

Step by step

Follow Below mentioned steps

1)

BatchSectionPlanning.png

2)

BatchSectionPlanning(1).png

3)

BatchSectionPlanning(2).png

4)

BatchSectionPlanning(3).png

5)

BatchSectionPlanning(4).png

6)

BatchSectionPlanning(5).png

7)

BatchSectionPlanning(6).png

8)

BatchSectionPlanning(7).png