This document outlines an initial development plan for the Education Management Information System (EMIS) in the Ministry of Education. It discusses improving the organizational structure of EMIS, developing strategies for hardware infrastructure, applications, networking, capacity building and change management. It also addresses developing policies and procedures, building technical capacity at EMIS, and standardizing software development across departments in the Ministry of Education. The goal is to create a long-term, comprehensive strategy to improve data collection, reporting and overall management of the education system.

1. Ministry of Education
Date: 20/06/2012
M.Ismail Khattab
Development Plan for EMIS
1

2. EMIS Current Status
 Organizational Structure
 Existing sections
 Responsibility of sections
 Activities
 Policies
 Functions/Services/Methods
 Services provided for the ministry, provincial offices and
schools
 Methods for performing the department functions
 Technical Review
 System developed structure
 Technologies used
 Functionalities
 A well defined software engineering methodology for
development of software at EMIS.
 Developing a policy for EMIS development at MoE
2

3. EMIS Current Status
 Human Resource
 The staff who are working on the system.
 Creating a sustainable organization
structure for EMIS at MoE.
 Problems and needs
 The current problems that exist in the
system and what changes needs to be
brought in the current procedures, policies,
technical side … .
3

4. EMIS Development Initial Plan
 EMIS Deployment Strategy (Central and
Provinces Level)
 The current strategy is not dominant on all aspects
of a strategic plan for a ministry’s EMIS.
 It is mostly focused on data administration.
 There are other important matters to be planned
such as technical infrastructure, application and
more.
 A long term and complete strategy is needed to be
developed, meanwhile improving the current
system.
4

5. EMIS Development Initial Plan
 Strategy for the following:
 Hardware Infrastructure development and implementation
 System software standardization at MoE ( Operating
systems, web platforms etc)
 Standard Application development & Implementation
methodology. Make or buy decision making. Develop Vs
outsource strategy.
 Networking and data centre strategy for MoE
 Capacity building strategy for the MoE
 Change Management strategy for the MoE
5

6. EMIS Development Initial Plan
 EMIS developed module review, installation
and configuration
 A thorough plan for application development should
be created. The structure of the application should
be specified. The technologies used in the
development of the application should be stated as
well.
6

7. EMIS Development Initial Plan
 The Required Softwares for Other Departments
 Different departments of MoE need software and
databases for their activities.
 It’s EMIS responsibility to make policy and standard for
all departments’ application development.
 Each department should not develop its own application
independently without cooperation of EMIS. Else it will
create lots of various problems for MoE in the future.
 The technical development should be under EMIS
supervision, the functional and administrative aspects
belong to each department.
 It’s necessary to prevent duplication, wastage of time,
system resources and so on.
 Developing the mechanism for an oversight committee
to regulate application development / deployment at
MoE
7

8. EMIS Development Initial Plan
 Policy and Procedure
 The current policy is very limited and does not cover
all aspects of EMIS activities. As the system is
developed and changed a new policy and modified
procedures need to be developed and
implemented.
8

9. EMIS Development Initial Plan
 Infrastructure
 The current infrastructure is very simple, disorganized
and contains some disadvantages.
 The central system needs lots of improvements in
infrastructure and application layers.
 The system must be developed in such a way that it
should be available in any circumstances.
 The system should be designed and built in three
layers, the central system (Data Center), the provincial
offices systems, and the district offices systems (The
Sub-Systems).
 Data can be transferred on monthly or weekly basis by
storage media. t is not needed to have internet
connection for transferring data to the central systems.
 The cooperation of the ICT department is needed in
development of the EMIS infrastructure and installation
of the systems.
9

10. EMIS Development Initial Plan
 Capacity building at central and provinces
level
 Trainings/Workshops/Seminars needs to be
planned held as the system is further developed
and changed.
 Different trainings are needed for different
categories of people such as training for technical
staff, M&R staff, provincial and district offices’ staff
and seminars and workshops for system provincial
and district managers.
 EMIS itself has very few technical staffs at the
moment. The work area is very wide and needs lots
of improvement. Therefore, EMIS needs more
technical employees.
10

11. Thank You!
Questions?
11