Implementation Methodology

Interact HRSM implementation and associated methodology are guided by the “Less is More” philosophy, and four principles:

less is more

The “Less is More” Philosophy calls for making things simple and this applicable to all facets of the project execution including planning, management, organization, documentation, communication, and other tools. The tools used in the implementation of the software need to be simple, flexible, and adaptable.

In support of the said “Less is More” philosophy, four guiding principle are used in the Interact Implementation Methodology:

Ease – The methodology and tools used in the implementation must be easy to learn, follow, and use.

Simplicity – In order for the implementation methodology to be easy to use, it must kept simple.

80/20 Rule – The 80/20 rule calls for focusing on the 80% of the features that are supported by the application, and leaving the 20% requirements which are less important to be addressed at later stage. In other words, do not let the 20% that is not there become the focus.

Focus – Focus is very in managing the implementation of a large enterprise software such Interact HRMS, thus once the plan is devised, we need to focus on achieving the milestones defines within the plan. We should not deviate from the implementation milestones, unless for good reason that adds value to the implementation timetable and the outcome of the implementation.

As previously stated, Interact Implementation Methodology is guided by the “Less is More” philosophy and the ease of use guiding principle. The methodology consists of six phases:

delivery

Planning – The planning phase is used to plan the project and consist:

• Project Kickoff Meeting
• Project Stakeholders and Responsibilities
• Preliminary Project Plan
• Prerequisites
• Change Control

Definition – This phase of the methodology is used to define and collect the data required for the implementation of the HRMS applications and consists of:

• Foundation Definition
• Policies, Procedures, and Processes Definition
• Data Conversion and Migration
• Review and Update Plan
• Review and Acceptance

Implementation – This phase consists of the setup of the software and include:

• Prepare Implementation Environment
• Software Installation
• Foundation Setup
• Policies Setup
• Workflow Setup
• Review and Acceptance

Validation – This phase consists of the validation of the HRMS transaction and processes against the setup of the foundation and policies and consists of the following:

• User Training
• Process/Transaction Cases
• Validate Processes
• Review and Acceptance

Deployment – This phase of the methodology consists of planning and preparing the software for go live and includes:

• Prepare Production Plan
• Prepare Production Environment
• Install Software
• Deploy Setup from Implementation
• Final Data Migration
• Production Support Procedures
• Review and Acceptance

Delivery – This phase consists of the go live of the software applications and the production support and include:

• Go Live
• Post-Production Support

Application Implementation Stages

As previously stated, Interact HRMS applications are implemented in stages, where a set of related applications based on prerequisites and co-requisites are grouped and implemented together, then the applications in the stage are put in production (Go Live). Based on the Interact software configuration purchased by client, there will be three Interact Application stages defined as follows:

Stage-1

1. Job Classification System
2. Organization Management System
3. Organization Self Service
4. Employee Hiring & Contracting
5. Employee Self Service
6. Grants/Funds Management
7. Leave Management
8. Time Management
9. Attendance Management
10. Time Clocks
11. Resources Scheduling
12. Compensation/Payroll Management
13. Travel & Expense Management
14. Employee Electronic Record

Stage-2

1. Financial System Interface
2. Third Party Payments
3. Position Budgeting & Control
4. Health & Safety
5. Assets Tracking
6. Recruitment Management
7. On-Boarding
8. Applicant Self-Service
9. Alerts Management
10. Benefit Planning & Enrollment

Stage-3

1. Workflow Management
2. Competencies Management
3. Performance Management
4. Training Management
5. KPI

Risk and Risk Mitigation

We recognize the risks associated with implementing advanced HRMS solutions, which are associated with lack of standards, lack of expertise, and end user learning of new structured and systemic approach to the management of HR Actions and processes. The later is the most critical to the success or failure of an HRMS project. This is specifically applicable to the introduction of advanced concepts, practices, and technologies applied to Talent Management. Few organizations, private and government have managed to successfully deploy an effective solution to Talent Management based on a systemic best practiced approach. But those who managed to introduce and use such solutions have benefited tremendously and have achieved a true Customer-Centric Culture within their environment. To mitigate the risks, 2Interact has adopted a Risk Mitigation program that is incorporated in the project management methodology.

The goal of this Risk Program is to enable engineers, managers, and other decision makers to identify, sufficiently early, the risks associated with software development, implementation, integration, and deployment so that appropriate management and mitigation strategies can be developed on a timely basis. Time is critical and the goal is to act early before a source of risk evolves into a major crisis. In other words, being mainly reactive in risk mitigation and control rather than proactive in risk prevention and control is at the heart of good risk management.

Clearly, the secret to effective risk management is the trade-off of mitigation cost against the potential adverse effects of avoided risk. In this context, the value of the methodologies and tools for software risk management is to manage more effectively and identify opportunities for continuous improvement, use available information and databases more efficiently, improve industry and raise the community’s playing field, and review and evaluate the progress made on risk management. Having said that, It is important to note that the developed software risk methodologies have three fundamentally different, albeit complementary, objectives:

1. Risk Prevention

2. Risk Mitigation and Correction

3. Ensuring Safe System Failure

The following seven risk management principles are instrumental in the quest to achieve these three objectives [Higuera 94]:

Sharing Product Vision

• Based upon common purpose, shared ownership, and collective commitment
• Focusing on results

Teamwork

• Working cooperatively to achieve a Common goal
• Pooling talent, skills, and knowledge

Global Perspective

• Viewing software development and implementation within the context of the larger system-level definition, design, development, implementation, and deployment
• Recognizing both the potential value of opportunity and the potential impact of adverse effects, such as cost overrun, time delay, or failure to meet product specifications

Forward-Looking View

• Thinking toward tomorrow, identifying uncertainties, anticipating potential outcomes
• Managing project resources and activities while anticipating uncertainties

Open Communication

• Encouraging the free flow of information between all project levels
• Enabling formal, informal, and impromptu communication
• Using consensus-based process that values the individual voice (bringing unique knowledge and insight to identifying and managing risk)

Integrated Management

• Making risk management an integral and vital part of project management
• Adapting risk management methods and tools to a project’s infrastructure and culture

Continuous Process

• Maintaining constant vigilance
• Identifying and managing risks routinely throughout all phases of the project’s life cycle

The above seven risk mitigation principles are incorporated in our Project Implementation Methodology to ensure that most of the risks are recognized and addressed, thus mitigating the risks and ensuring that the project meets it goals and objectives.