eServices Management forms an integral part of the government online solution for the provision of more efficient government services to society at large. eServices Management provides the technology not just to create and add own eGovernment services, but even to plug in third party developed eServices to the framework, given that they adhere to the required standards. The solution is based on interoperable standards and can be scaled throughout the years when additional eServices are added to the platform.
eService Management enables the Central Administration to maintain the entire eService life-cycle, from subscription and delegation, to termination of the subscription.
Service Provider Registration and Verification
The government entity applies and registers to be an eService Provider with the Central Authority. The authority, established by the government, will have the responsibility to promote the use of eServices and disseminate the same eServices to the citizens. The Central Administration will verify and authorise the service provider to disseminate its eServices over the common government website infrastructure.
eService Registration and Configuration
The scope of the eGovernment services framework is to allow additional eServices to be added onto the framework and published through the unified myGov portal. The eServices can be placed into categories and sub-categories that determine how the eService will be displayed within the myGov Portal. The eService Provider has the authority to register new eServices and publish them onto the myGov portal. Each eService can be configured to provide the behaviour required by the eService Provider.
Each eService is allocated a specific subscription type. A level 0 type will make the eService available by default to all eCitizens and no subscription to the specific eService is required, whilst a level 1 requires an eCitizen to subscribe for the eService before the access is granted.
Each eService is assigned a specific security level. At a level 0 security, normally assigned to eServices that are by default offered to all users, authentication is not required. At a level 1 security level, assigned when a minimum level of security is required to identify the individual accessing the eService, authentication is required via username and password. Further security at level 2 and level 3 can be implemented. At level 2 security, for eServices requiring a higher level of security than level 1, authentication is required via username, password and digital certificate. Digital certificates provide a higher level of assurance and provide a more secure link between the individual and his/her unique online identity. At level 3 security, for eServices requiring the highest security level at which non-repudiation is mandatory, authentication is required via the eID card.