The e Sri Lanka project has been implemented by Information and Communication Technology Agency (ICTA) of Sri Lanka with the objectives of using Information and Communication Technology (ICT) to foster social integration, peace, economic growth and poverty reduction. Re-engineering Government Program (Re-Gov) is one of the key programmes of ICTA which implements the e-Sri Lanka project. There are number of projects already implemented by the Re-Gov and e-Samurdhi is one of such projects.
This document outlines
(1) Concept of the e-Samurdhi project where it contains scope, objectives, deliverables, time lines, cost estimation and envisaged benefits
(2) Implementation Approach
(3) Current Status of the project
a) The Background
The Samurdhi Authority of Sri Lanka (SASL) is the primary stakeholder of the e-Samurdhi project where there are other stakeholders such as Samurdhi beneficiaries, Samurdhi Commissioner General’s Department (SCGD) and the Government of Sri Lanka (GoSL).
The Samurdhi Authority of Sri Lanka as an organization has number of functional divisions and the activities are carried out at different levels of the organization such as National level, District level, Divisional Secretariat level and Wasam level. The following diagram illustrates the information flow and organization structure of the SASL.
Figure 1-Organization structure
According to the above diagram (figure 1) functions of the SASL have been distributed for the local government level with different authority levels. There are subsidiary organizations of SASL at local government level such as Samurdhi Banks, Maha Sangams and beneficiary organizations.
b) Key problems related to existing Samurdhi activities
The numbers of welfare activities directed towards the citizens who are below the poverty line are very high in Sri Lanka. The number if organizations which are involved in the welfare activities are also high hence duplication of works is also evident. As a result of poor coordination between organizations involved in this activity and the lack of a common mechanism to monitor and evaluate the activities, the information on such activities at national level has not been made available for decision making. Due to this fact even the activities are planned and carried out without proper coordination.
The main problems in related to Samurdhi activities are listed below.
i. Problems relating to development projects
The lack of proper mechanism for management information in relation to development projects – All work related to development projects are carried out manually. Since currently there is no mechanism to manage such information in a coherent manner, it is difficult for SASL to use the information efficiently for decision making. Due to the absence of a MIS to support activities in the areas of live hood improvement, income generation and social development projects, the organizational decision making, monitoring and evaluation processes have become inefficient.
ii. Problems relating to human resource management of SASL
a. SASL manages 24,000 Samurdhi personnel who are involved with Samurdhi activities.
b. Lack of human resource information for efficient deployment, monitoring and evaluating the performance is an obstacle for achieving the objectives of Samurdhi program
iii. Problems relating to Financial Management
All financial activities are based on paper based manual accounting system, hence delays have been observed in the areas of payments, reimbursements and recovery of funds. SASL needs to have a more reliable financial management system.
iv. Problems relating to Samurdhi beneficiaries
a. SASL provides direct social benefits to 1.7 Million Number of citizens. Various Divisional Secretariats (DSs) use different databases built by them for carrying out their functions related to Samurdhi. SCGD also has a moderately advanced electronic system to manage the Samurdhi lottery information. However neither SASL nor SCGD has a reliable mechanism to keep track of the Samurdhi beneficiaries and their activities. This is one of the main problems that SASL and SCGD are facing. Data redundancy is another problem since the details of Samurdhi beneficiaries are maintained at various locations in different formats. Though the information related to Samurdhi beneficiaries are maintained in various electronic forms and formats, the lack any information security measures in current systems has created another problem that should be addressed urgently.
b. All Samurdhi Societies are working in isolation; therefore the absence of a mechanism to exchange knowledge and experience among the various society groups has become a limitation for improving Samurdhi societies.
c) Project Development Objective and Scope of the Project
To establish an ICT based Management Information System for SASL for
i. Providing better services to Samurdhi beneficiaries
ii. improved, effective, transparent and accountable management in the areas such as
• Beneficiary information management
• Programme and Project Management
• Human Resource Management
iii. Better control over the financial activities with respect to the beneficiary or development projects
a. Software development
eSamurdhi system is being developed through an architecture driven solution based on the Service Oriented Architectural principles. Therefore, high level business architecture was prepared following the system study to provide a clear picture for the software vendors.
In order to phase out the project activities rationally, the project was modeled based on the Rational Unified Processes (RUP). All the software development activities are aligned with the RUP disciplines that are stated in the below diagram (figure 2).
Figure 2 – RUP based approach to solution development
In contrast to the widely adopted water-fall software development approach, Software Development Services Approach (SDSA) was used to solution procurement and development, as illustrated in figure 3. The focus was on procuring vendors who would provide implementation capabilities to build the solutions according to a predefined enterprise architectural design. The key steps which were followed in this approach were,
(1) procuring a vendor to do a high-level BPR/systems study,
(2) formulating an overall enterprise architectural view, including identification of major software modules, the grouping of the modules into projects/phases (including a logical systems architectural view), the deployment architectural view and the overall implementation timeline,
(3) procuring vendors to develop the software components within each project, in an iterative manner,
(4) procuring a vendor to provide software maintenance and support services for 3-5 years
(5) procuring a Software Quality Assurance vendor for ensuring the quality of all software modules and integration of those
(6) obtaining the services of Sri Lanka Computer Emergency Response Team to assure the security of the system
Similar to the original approach, ICTA is involved in overall project management. However, in addition, ICTA would also drive the formulation of the overall enterprise architectural viewpoint, and other disciplines such as strategic re-use of software components. ICTA typically completes these aspects with the assistance of a Software Architecture Group of Experts (SAGE) for obtaining the assistance of industry experts for ensuring the accuracy of the design, architecture, user interfaces and coding.
Figure 3 Software Development Services Approach to solution development
SDSA naturally reduces the risk for the vendor, since their overall responsibilities are reduced. Likewise, this approach significantly reduces the overall risk for ICTA since the project complexity and duration is highly reduced. Furthermore, this approach provides a huge advantage to the government stakeholders since they receive their solutions iteratively, quicker, and in a more flexible manner, thereby allowing for agile deviations from the original plans.
A typical SDSD driven project would be 3-4 months in duration. The primary selection criteria is the vendor's capabilities in developing solutions according to a given architecture, whilst leveraging specified technologies.
Major re-engineering government program initiatives under e-Sri Lanka, such as the LankaGate and e-Samurdhi were procured according to this new SDSA.
As per the RUP discipline business analysis was taken place at the beginning and established the business requirements for the project. According to the business requirement study nine modules were identified. However due to time and money constraints stakeholders decided to prioritize the modules depending on the urgency of the Samurdhi Authority. Therefore, mainly three modules were identified for implementing under eSamurdhi project. Such as,
a. Beneficiary Relationship Management module (CRM)
b. Program and Project Management module (PPM)
c. Human Resource Management module (HRM)
Figure 4 illustrates the high level business architecture that was envisioned after the business analysis.
Figure 4 – High level Business Architecture of eSamurdhi Project
The eSamurdhi solution has been architected as represented in the figure 4 business architecture diagram. According to above diagram eSamurdhi architecture has three layers such as Information Portal, Business Functions and System Integration layer.
Business Functions Layer
Business layer provides services relating to operations of the SASL which are grouped as applications such as PPM, CRM, HRM and other business functions should also be able to plug in subsequently.
The following companies won the contracts to develop the 3 main modules.
a. CRM – Delloite of India
b. HRM- hSenid of Sri Lanka
c. PPM - PWC of Sri Lanka
Further to the above modules that were identified during the initial system study, the Subsidy Management System of SCGD was also included under eSamurdhi scope based on the request from the Ministry of the Economic Developmet. This module is referred as Improving Monitoring and Evaluation System of Samurdhi Safety Net Program. (IMESSP)
Currently the SCGD is implementing the IMESSP with the following objectives.
Objectives of IMESSP
a. To ensure the recipients of the Samurdhi subsidy are selected based on the regional indicators and in a transparent manner
b. To ensure on-going information in relation to recipients and their families are captured on a regular basis into the System.
c. Creating and managing of (a) Subsidy Schemes and (b) Distributors within the Samurdhi Program.
d. Managing the beneficiaries within a Subsidy Scheme including the Issue and Recall of Subsidy Stamps.
e. Managing the disbursement of the benefit to the beneficiary and to receive re-imbursement for the benefits disbursed.
Development of IMESSP module has also been awarded to Delloite
In this layer it is required to define web services to expose and consume data with other related services of the individual applications in the Business Functions layer hence all the services are loosely coupled with each other.
According to the available similar freely deployable tools, multiple tools and frameworks used to develop applications within the business functions layer. Further within one application even different types of tools and frameworks were suggested to use to build different functions and services required.
The tools and frameworks that are used in the Business Functions Layer should be platform independent and free to use.
However each application in the Business Functions Layer should be integrated in the Integration Layer as per the above architecture.
Further individual application which provides services to citizen (G2C), government (G2G) and business organizations (G2B) should contain web services to be included in the Country Portal (www.srilanka.lk) as portlets.
Information Portal Layer
The end user should see the complete set of applications as a unified ‘portal’. This can be achieved by:
• Creating a similar look and feel across all applications.
• Sharing identity management across all the applications.
• Sharing session management across all the applications.
Therefore, this is the user interface layer of the eSamurdhi solution where different types of users interact with.
This layer should consist of data capturing interfaces as well as reporting interfaces of different applications.
The information portal should cut across the entire Business Applications layer and should interact with the integration layer in relation to sharing identity management and ‘Single Sign On’ (SSO) requirement. The each application in the Business Functions Layer should use identity management system of the Information Portal through Integration Layer.
The applications within the business layer should be integrated with the interfaces defined with each application. For example PPM should have services to interact with HRM and CRM where every each other application needs not to access the database the other application.
Therefore, simplified Service Oriented Architecture (SOA) was used to govern the architecture of the eSamurdhi solution.
Integration layer cut across Business Applications layer and Information Portal layer to provide seamless integration of business functions and user interfaces.
b. Software Quality Assurance (SQA)
This is a key process with respect to the project governance model. SQA is used as an independent audit team to review entire software development process as stated in the RUP model. Therefore, the key objectives of this process are as follows,
1. To ensure that SWDs have followed industry accepted SQA process for developing the eSamurdhi solution
2. To ensure that the eSamurdhi solution is developed with the acceptable quality standards.
3. To ensure that the eSamurdhi should have smooth and successful User Acceptance Test (UAT) and signing off.
The SQA assignment has been awarded to a JV led by KPMG and 99x.
This is a metrics based monitoring method where measurement metrics were defined for each and every phase in the software development process. Metrics were defined based on the software testing best practices.
According to the Automated testing process, every development activity is mirrored by a test activity. The testing process follows a well-proven testing methodology called W-model. Following Figure-5.0 explains, the way of testing activities of W-model involve with the standard software development life-cycle.
Figure 5.0 – The W-model
While the execution of the project, either developers or SQA team can generate the related metrics.
Skills required to generate Metrics
During these development stages, several roles and parties will be involved with development and testing activities. In Figure 6.0 shows the development stages, the activities which should perform during the stages, the roles or the parties should involve and the metrics which derive and maintain in the stages.
Figure 6.0- Skills required to generate Metrics
Evaluation of similar tools
World Bank approval for procurement plan
Procurement of software developers
Procurement of independent software quality assurance consultant
Oct/2010 to May 2012
User Acceptance Testing
System live run