slide2 02

BASA International Co.

  • Presenting Oracle Solutions

In order to use a single, unified and standard method for localization and implementation of systems, Basa Company uses the customized version of OUM (Oracle Unified Method for ERP system implementation). The OUM methodology is the latest and most up-to-date methodology offered by Oracle, which supports the phase of strategy development, project management and implementation in a complete and integrated manner. In the project management method, the manage focus area of ​​this methodology, which is the new version of PJM, is used. One of the strengths of the OUM methodology is to provide special editions for customizing and developing Oracle's specific solutions. This means that, in addition to providing a standard methodology for localization and implementation of systems including ERP modules, for example, for the development of portals and websites based on its Webcenter tools, Oracle has also provided a complete methodology adapted from OUM. This methodology includes phases, activities, guidelines, output formats and the method of doing the work is presented in detail. It is worth noting that this methodology is not accessible to the public and only Oracle partners can use it. Considering that Basa company is a Gold Partner of Oracle in Dubai, therefore this methodology and its tools are fully available to this company and it is a strong point for carrying out system implementation projects based on this methodology.

Inception phase:

The main goal of this phase is to create a common vision among all stakeholders regarding the goals of the project's life cycle. This phase is important for all projects because in this phase the scope of the project, high-level requirements and general risks must be identified before the project continues. In this phase, the strategic goals of the project are reviewed and the high-level requirements of the project are prioritized, documented and approved. In cases where it is possible, the functions of the system are grouped in such a way that professional and distinct teams can work on the project in parallel. The work agenda of the first iteration of the Elaboration phase is also prepared in this phase.

Elaboration phase:

The purpose of this phase is to move from the major requirements known in the previous phase to the details of the requirements, segmenting the solution, creating a prototype (if needed) and establishing the system architecture for design and implementation activities in the next phase (Construction). In this phase, the project team must ensure that the requirements are correctly understood in order to reduce the risk of not understanding the requirements.

Construction phase:

The purpose of the Construction phase is to transform the identified micro-requirements into customized components, custom-made components and the integration of all these components. At the end of this phase, the first version of the system is ready for operation. This version is usually the beta version of the system. In a nutshell, in this phase, the construction and development of the system is done, the integrity of all components is ensured, and the system is prepared for acceptance testing and deployment.

In this phase, an iterative process is done to refine the data and Use Cases.

Transition phase:

The purpose of this phase is to transfer the guideline and system to operational servers and make the system available for the employer's organization. During this phase, the system is accepted by the employer's organization, the organization is prepared to use the system, and if the new system must replace an old system, in this phase, a smooth transition from the old system to the new system will be done. Although the system is acceptable for operation, it may need improvements. In this case, the required minor improvements are planned and carried out in this phase.

Production phase:

The purpose of the Production phase is to exploit the new system, evaluate the system and support its users. This phase includes monitoring, evaluating the efficiency of the system, taking necessary actions  to ensure the operation and usage of the system, supporting the software, responding to users' requests and troubleshooting, planning for the development of new versions of the system in the future.