RTE MIS Product Documentation

State Management

In the State module, the state admin has the power to manage the roles of the other government authorities and their rights, schedule the campaign cycle, trigger different rounds of lottery, send SMS to allotted students, and perform the reimbursement process to the beneficiaries' (schools) accounts.

Individual School UDISE Code Approval

District administrators validate the new UDISE code entered in the RTE database by the block administrators. Block admins individually enter the Udise code of schools not registered in the RTE database because they are newly registered schools.

  1. District admins can approve the newly added Udise code. District administrators can do this by visiting the Udise portal, and after verifying information from there, the District admin will approve the Udise code.
  2. Once the Udise code is approved, only schools can create accounts to participate in the campaign.
  3. If district admin found any correction on information then either they can make modifications or ask BEOs to make necessary changes; once BEOs make the changes, DEOs can approve the UDISE code.

Campaign Creation

  1. Campion creation is the section where the duration for a particular section is defined, which is going to be followed in a particular campaign cycle.
  2. It should be possible that there should be two or more different cycles that may run on a particular campaign year. For this, a log should be maintained for each cycle and year.
  3. It is the State admin's responsibility to define the duration of a cycle to follow and that duration should also be entered as the start date and end date on the campaign creation panel of MIS portal.
  4. Below is the list of sections that shows the step-by-step process to follow to run a campaign and to define the duration for each:
    1. School registration (Start Date - End Date)
    2. School Renewal (Start Date - End Date)
    3. School registration / Renewal verifications (Start Date - End Date)
    4. School Mapping / Modifications (Start Date - End Date)
    5. Student Application / Modifications (Start Date - End Date)
    6. Student Application Verification (Start Date - End Date)
    7. Lottery (Start Date - End Date)
    8. Post lottery admission to school (Start Date - End Date)
    9. Student tracking (Start Date - End Date)
    10. Reimbursement claim (Start Date - End Date, Session for which claim will open)

New User Creation form for Block, State, and District

  1. User creation can be made in two different levels, one at the District level where the District admin can Create new block admins or modify the existing admins' information.
  2. Another is at the State level, where state admin can create new district admins or modify existing information.
  3. Fields that should be there in Block admin master tables are:
    1. Block Name (Alphabetic)
    2. Authority Name (Alphabetic)
    3. Mobile Number (Number only, 10 digit min and Max both, proper number check validation)
    4. Status(Active or not)(bool)
    5. Created Date (DateTime) (Auto-generated, not displayed at UI)
    6. Updated Date (DateTime) (Auto-generated, not displayed at UI)
    7. Deleted Date (DateTime) (Auto-generated, not displayed at UI)
  4. Fields that should be there in the District admin master tables are:
    1. District Name (Alphabetic)
    2. Authority Name (Alphabetic)
    3. Mobile Number (Number only, 10 digit min and Max both, proper number check validation)
    4. Status(Active or not)(bool)
    5. Created Date (DateTime) (Auto-generated, not displayed at UI)
    6. Updated Date (DateTime) (Auto-generated, not displayed at UI)
    7. Deleted Date (DateTime) (Auto-generated, not displayed at UI)
  5. OTP verification should be made for mobile number verification, and in the case of the mobile number modification.
State_Admin