Introduction to R2A Interim Solutions

1. Introduction to R2A Interim Solutions January 2010

2. Agenda

3. Agenda

4. Objectives for Today In today’s session, we will target to achieve the following objectives: To understand what are interim solutions for GEMS Release 2A To learn how and when to use interim solutions To understand the interim solutions for each process

5. Interim Solutions: What are they? Interim Solutions are temporary processes and/or procedures to be used while GEMS is being deployed to completion A We are here! • All processes available • Only selected departments rolled-out – interim processes required for departments not yet impacted by GEMS B • 4 out of 10 processes deployed in R1 – need to maintain non-deployed processes • Only 5 departments rolled-out – interim processes required for departments not yet impacted by GEMS

6. Interim Solutions: Why are they important? • Because… • GEMS deployment is staggered – Brunei Civil Service Ministries and Departments are deployed to GEMS gradually from R2A to R2E • SIMPA is still active – affects processes that cross ministries and/or departments, e.g. promotion, transfer, recruitment • GEMS Interfaces with TAFIS and Payroll are ongoing – need to balance between manual and automated processes

7. Interim Solutions: What should you expect to see? As you learn about interim solutions in this session, you should notice the following: + + A mix of GEMS, manual activities and/or other systems GEMS SIMPA Your actions depend on which Department an employee is from SIMPA For some processes, you will still need to maintain data in SIMPA

8. Common Terminology in Interim Solutions You will also hear these common terms as we discuss interim solutions: Rolled out department A department deployed to GEMS, where its departmental details and employee data are available in GEMS Non-rolled out department A department that has not been deployed to GEMS, therefore no departmental or employee data is available in GEMS Manual process A process that is done outside the system, e.g. by paper submission, hardcopy dispatch, etc. GEMS process A process conducted in GEMS As-Is process An existing process currently executed before deployment of GEMS

9. Assumptions When Using Interim Solutions When using Interim Solutions, the following assumptions should be considered: You have been trained on the complete GEMS process (i.e. from Train-the Trainer, End User Training or Change Agent Training sessions) You are aware of the departments that have been rolled out in GEMS (6 departments in R1 and R2A) Non-rolled out departments will maintain their As-Is processes (No changes to daily operations) Employee records converted to GEMS have been flagged in SIMPA (An employee can be in a non-rolled out dept and also be in GEMS)

10. Guiding Principles When Using Interim Solutions Guiding Principles are basic rules to remember when executing interim processes: Once in GEMS, always in GEMS – Once an employee record is in GEMS, it should be maintained there Employees in non-rolled out departments do not have access to GEMS – No Self Service capabilities Check for GEMS flag in SIMPA when updating data in SIMPA – Employee records in GEMS will have ‘Y’ in SIMPA and therefore should be maintained in GEMS

11. Let’s talk about Interim Solutions!

12. Agenda