Service Rotation System -- 2

Product: Service Rotation System. Dear All, Our client is a government agency for which we want to build a Minimum Viable Product (MVP) of a Talent Management/Employee Rotation System called Service Rotation System (SRS). The proposed system should have the capabilities to rotate the staffs through different vertical offices such as Ministries, Departments, & Agencies (MDA’s) while they are in service and before they are due to retire. The SRS should have the capability of generating the names of employees who are due for a new posting. The winning entry should include the following features: Employees should be due for posting every 2-3 years depending on their cadre. (The frequency of posting per cadre is information that will be supplied for the development of application logic). Be able to group all MDA’s into 5 clusters. Some of these clusters will be termed Category A MDA clusters while others will be Category B MDA clusters. Employees currently in one cluster should not be posted to another MDA within the same cluster. Employees being posted from a Category A cluster should not be posted by the system into another Category A cluster but must be posted to a Category B cluster in their next due posting. Until an employee has been posted across all 5 clusters of MDA’s, he/she may not be eligible to be posted back to an office or cluster for which he/she has previously been posted, except under special posting circumstances. The SRS should flag also have the capability to flag employees due for retirement 3-6 months before retirement. This it will compute based on the employees date of first engagement and add another 30 years of service to same. The SRS should not post employees it has identified are due for retirement to another MDA in a posting round but periodically generate notifications and reports of employees that are due for retirement. The SRS must allow special and manual posting request. ( This feature should be embedded). The SRS will have 3 roles; Super Administrator, Administrator, & User. The User will be the Desk Officer with the capacity to manage the system on a daily basis and initiate postings. The SRS should then generate a posting report that will be sent to the Administrator in a workflow approval request for Approval or Rejection with ability to comment on whatever choices are made. Where a posting is approved by an Administrator, such posting is released into the system and affected employees are notified of their new postings. Where a posting is rejected by an Administrator, such postings will revert in a workflow request back to the SRS User to re-initiate after having read and actioned the comments from the Administrator. Only the Super Administrator may initiate a Manual Posting or override an automatic posting done the SRS. System must be able to send notifications Functional Requirement Features used by user Login to Admin page. Admin page with Norminal Roll Posting Due Posting Due for Posting Due for Retirement Feature requirement Login to Admin page User should login with username and password. Admin page includes Norminal roll : It should include a list of staff details which are: IPPIS Number Full name Rank SGL Present MDA Previous MDA Cadre Effective date Status Note* All Information will be provided. Posting: it should include a search by date icon and search by MDA ( Different ministries . Also include a GENERATE button under the selection which brings a list of due names for posting. Due Posting: i) All notifications should come through this feature. ii) It’s should have two selections : Due for posting System should generate list of all staffs due for posting. Due for Retirement System should generate a list of all staff due for retirement. Other Information Link [login to view URL] More details available on request