Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

PMP vs AIM vs. OUM

Posted on May 27th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

If you compare PMP process group in refrence to Oracle AIM and Oracle Unified Method (OUM) here is quick compare :

 

PMBOK® PROCESS GROUPS ORACLE AIM PHASES ORACLE OUM PHASES
Initiating Operation Analysis Inception
Planning Solution Design Elaboration
Executing Build Construction
Monitoring and Controlling Transition Transition
Closing Production Production

Posted in Methodology/Process | No Comments »

Quick comparison: AIM Vs OUM

Posted on May 15th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

A reader asked a very good question, how OUM differ from AIM in term of deliverable ? Considering the fact of Implementation project phases how and what is percentage you can consider as per OUM curves?

If you already practiced AIM's methodology you will not find a very big difference, majority of task and deliverable remain same, but they reclassified under different Process. Lets take a quick look, if you take first on Phases then AIM was based out of 6 phases where as OUM only 5.

Read the rest of this entry »

Posted in Methodology/Process | No Comments »

Oracle Unified Method (OUM) :Envision – Part -III

Posted on May 9th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

The OUM focus area provides a framework for development and maintenance of enterprise level IT strategy, architecture, and governance.

The Envision focus area consists of two phases:

  • Initiate

During Initiate, you perform a set of foundational tasks that have a broad range of objectives and applicability. At one end, delivering a service based on the Envision Roadmap process can establish the vision for one or more projects intended to achieve a focused set of business objectives. On the other end, Initiate phase processes can be used to establish a broad set of enterprise level IT processes that are continued in the Maintain and Evolve phase.

  • Maintain and Evolve

The processes and tasks of the Maintain and Evolve phase bring the work begun during Initiate into the day to day life of the enterprise. This phase forms the foundation for governing and managing enterprise level business processes and strategies.

Envision is organized into six processes:

  • Envision Roadmap
  • Enterprise Business Analysis
  • Organizational Change Management
  • Enterprise Architecture
  • IT Portfolio Management
  • Governance

Envision OUM

dgreybarrow Similar Post

Posted in Methodology/Process | No Comments »

Oracle Unified Method (OUM) : Manage – Part -II

Posted on May 7th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

As mention in previous post, OUM Second focus area is Manage, which provides a framework for all types of projects which can be planned, estimated, controlled, and completed in a consistent manner.

Similar to Implement , The Manage focus area (or PJM) has three phases:

  • Project Start Up Phase

The purpose of the Project Startup phase is to provide strong and clear directions for producing a product or service which delivers identified benefits or purpose for the client. During the Project Startup phase, resources are allocated to achieve specific objectives, satisfy needs, and set expectations through a planned and organized approach.

  • Project Execution and Control Phase

The purpose of the Project Execution and Control Phase is to provide adequate visibility into actual progress so that management can take effective actions when the project's performance deviates significantly from the project plans

  • Project Closure Phase

Project Closure Phase is the last phase of the Project Life Cycle. The commencement of the Project Closure Phase is determined by the completion of all Project Objectives and acceptance of the end product by the customer. Closure of any financial issues,Collection and Completion of All Project Records & Archiving of All Project Records are typical elements of this phase.

Manage OUM

The Manage focus area is organized into 13 processes as:

  1. Bid Transition The Bid Transition process, Typically represented in Project Start Up, is in reality more of a project initiation task. The first major activity that a project manager is expected to perform is to participate in the handoff from the "sales cycle" to the "delivery cycle".
  2. Scope Management - The goal of the Scope Management process is to identify clear boundaries of what is to be implemented and what key work products are to be produced.
  3. Financial Management - In order to control costs and provide a basis for financial monitoring and reporting, the project manager needs to plan the project costs in detail.
  4. Work Management - The objective of the Work Management process is to develop the work plan and to define and document the processes and policies to be used to execute, maintain, control and close-out the Project Workplan.
  5. Risk Management - Risk Management is a structured process for identifying, documenting, gaining agreement on, and communicating risks throughout the lifecycle of a project.
  6. Issue and Problem Management -Issue and Problem Management is a structured process for identifying, documenting, tracking, and resolving issues and problems as they occur throughout the lifecycle of a project.
  7. Staff Management - The objective of the Staff Management process is to plan resource requirements, assign roles and responsibilities, staff the project, and manage the project team.
  8. Communication Management - The objective of the Communication Management process is to regularly inform project stakeholders of the project status and continually set expectations.
  9. Quality Management - Very similar to PMI , The Quality Management process “implements the quality management system through the policy, procedures, and processes of quality planning, quality assurance, and quality control, with continuous process improvement activities, conducted throughout...."
  10. Configuration Management - The objective of the Configuration Management process is to reduce project risk by defining appropriate management and control processes for important work products including both documentation and software.
  11. Infrastructure Management - The objective of the Infrastructure Management process involves setting up the team work environment and technical infrastructure for the project.
  12. Procurement Management - The objective of the Procurement Management process is to document the procurement requirements, procure required contracted goods and/or services, and manage the procurement of the goods and/or services.
  13. Organizational Change Management - The objective of the Organizational Change Management process is to be aware of the Client’s Organizational Change Management Strategy and to effectively create a Change and Communication Plan that addresses this strategy. The goal is to create the change momentum needed to increase buy-in and reduce resistance - thus reducing productivity losses.

Next post will more focus on Envision Focus Area. Keep watching.

dgreybarrow Similar Post

 

Posted in Methodology/Process | No Comments »

Oracle Unified Method (OUM)

Posted on May 4th, 2011 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Since retirement for Oracle legacy methods, there was lot of queries on OUM vs AIM , therefore this post will help reader to know more about new method.

The OUM aka Oracle Unified Method supports the entire Enterprise IT Life cycle, including support for the successful implementation of every Oracle product.

It is a robust, technology agnostic methodology Oracle Methods …

  • Based on industry standards and field experience
  • Highly scalable to support project or program specific requirements
  • Iteratively developed through a continuous, evolutionary process

dgreybarrow OUM Principal

This is based out of five main principles

  1. Business: Focus on the business and assure stake holder acceptance and delivery of the development’s efforts.
  2. Architecture: Define architecture before resources are committed for development and implementation.
  3. Adaptability: Encourages adaptability for scalable delivery across small and large projects possessing disparate resources and skill levels.
  4. Implementation: Provides rapid implementation techniques to ensure business solutions in short time frames
  5. Standards: Leverage the Unified Modeling Language and the Unified Software Development Process

dgreybarrowOUM is able to…

Support the complete range of Oracle technology projects including

  • Service-Oriented Architecture (SOA)
  • Enterprise Integration
  • Custom Software
  • Enterprise Performance Management (EPM)
  • Business Intelligence (BI)
  • Enterprise 2.0
  • Enterprise Application Implementation
  • Software Upgrade

Currently Oracle Consulting using this methods, tools support a complete range of technology engagements.

dgreybarrow In Summary... OUM structure

  • is a comprehensive set of method materials that is applicable to any type of information technology project.
  • is a plan-based method – that includes overview material on various approaches and standards.
  • It includes base guidelines for focus areas, views, phases, activities, processes and tasks, as well as work product descriptions.

OUM basically have focus areas and there underline phases and processes , in summary

dgreybarrow OUM FOCUS AREAS

These 3 Focus Areas provide a frameworks for enterprise level planning, project and program management and implementing .

  1. Envision Focus Area deals with development and maintenance of enterprise level IT strategy, architecture, and governance. This also assists in the transition from enterprise-level planning and strategy activities to the identification and initiation of specific projects.
  2. Manage Focus Area provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner.
  3. Implement Focus Area This focus Area provides a framework to develop and implement Oracle-based business solutions .

Next let take a quick overview for Implement Focus area which got replacement of old methods like AIM Foundation, AIM for Business Flows, Compass, Results Roadmap, etc.

dgreybarrow Understanding OUM's Implement Focus

This focus area typically based out of milestone based approach.Typical Milestone are:

  • Life cycle objective milestone
  • Life cycle architecture milestone
  • Initial operation capability milestone
  • System in production milestone
  • Sign-off milestone

As mention earlier this comprises of 5 phases and 14 processes, details as follows:

dgreybarrow OUM Project Phases

The Workflows within an OUM project are categorized into five phases: Inception, Elaboration, Construction, Transition, and Production. These phases are described below:

(A) Phase I: Inception :As the first phases in the project life cycle.Major goal of this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. Kick off's, review , high-level business requirements along with initial project plan is being targeted in this phase only.

(B) Phase II: Elaboration :This is the second phases in the project life cycle, where major focus would be to develop the detailed requirements models, partition the solution, develop functional prototyping, and baseline the architecture of the system.

(C) Phase III: Construction :As the third phases in the project life cycle, Construction focuses on design, implementation, and testing of functions to develop a complete system.

(D) Phase IV: Transition :This typically consist from installation onto the production system through the UAT and launch of the live application, open and ready for business.

(E) Phase V: Production : The goal of the Production phase is to operate the newly developed system, assess the success of the system, and support the users. This includes: monitoring the system; acting appropriately to ensure continued operation; measuring system performance; operating and maintaining supporting systems; responding to help requests, error reports and feature requests by users; and managing the applicable change control process so that defects and new features are prioritized and assigned to future releases.

dgreybarrow OUM Process - Typically OUM process defined as "A discipline or sub-project that defines a set of tasks related by subject matter, required skills, and common dependencies". A process usually spans several phases in an approach.

All OUM tasks are also organized into processes that group related tasks together. Project team members are assigned to these groupings according to their specialization and background. OUM includes the following 14 processes

Oracle Unified Method (OUM)

  1. BUSINESS REQUIREMENTS [RD] – Objective of the Business Requirements process is to identify, refine, and prioritize the business requirements for the proposed system
  2. REQUIREMENTS ANALYSIS [RA]– Objective of the Requirements Analysis process is to further analyze the requirements identified during the Business Requirements process as the basis for analysis and design.
  3. ANALYSIS [AN]– Objective of the Analysis process is to analyze, refine, and structure the system requirements via the Analysis Model.
  4. DESIGN [DS] – Objective of the Design process is to translate requirements into a system design that meets all functional and supplemental requirements.
  5. IMPLEMENTATION [IM] – Objective of the Implementation process is to develop the final system, through a number of iterative steps.
  6. TESTING [TE]– The Testing process is an integrated approach to testing the quality and conformance of all elements of the new system.
  7. PERFORMANCE MANAGEMENT [PT]– Objective of the Performance Management process is to define, construct, and execute an effective approach to managing performance throughout the project life cycle.
  8. TECHNICAL ARCHITECTURE [TA]– Objective of the Technical Architecture process is to design an information system architecture that realizes the business vision.
  9. DATA ACQUISITION AND CONVERSION [CV]– Objective of the Data Acquisition and Conversion process is to convert all legacy data necessary for the operation of the new system.
  10. DOCUMENTATION [DO]– Objective of the Documentation process is to develop documentation that augments product manuals with information about custom software and business procedures.
  11. ORGANIZATIONAL CHANGE MANAGEMENT [OCM]– Objective of the Organizational Change Management process is to identify the human and organizational challenges of the project in order to mitigate risk.
  12. TRAINING [TR]– Objective of the Training process is to adequately train the project team to begin the project and train the users to run the new system.
  13. TRANSITION [TS]– Objective of the Transition process is to install the system and go production.
  14. OPERATIONS AND SUPPORT [PS]– Objective of the Operations and Support process is to monitor and respond to system problems to fix errors and performance problems and plan enhancements.

Believe with this method companies get simplified project management, improved planning, reduced risk which make them manage project within time within Budget.Next post will more the details for other Focus area.Keep watching this space.

Posted in Methodology/Process | No Comments »

Retirement of Oracle AIM & AIM for Business Flows

Posted on December 19th, 2010 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Last week there was an email from Oracle for retirement for legacy Methods like AIM Advantage, AIM for Business Flows, EMM Advantage. These methods and Methodology been used by mostly Oracle Consulting,and there partners. The retirement date is January 31, 2011. Going Forward , OUM is going to be replaced by these methods, and not to forgot OUM version 5.3 was released a month back (November 13,2010).

OUM aka ORACLE UNIFIED METHOD is currently available to certified Oracle Partners(Platinum and Gold) and it is not freely downloadable publically. OUM supports the complete range of Oracle technology projects including:

  • Oracle Database
  • Oracle E-Business Suite
  • Oracle Enterprise 2.0
  • Oracle Fusion Middleware
  • Oracle Service-Oriented Architecture (SOA)
  • Oracle Business Intelligence – Applications
  • Oracle Business Intelligence – Technology
  • Oracle Data Warehousing
  • Governance, Risk, & Compliance (GRC)
  • Identity Management (IdM)
  • Oracle Transportation Management
  • Performance Management - Business Intelligence and Analytics
  • JD Edwards EnterpriseOne
  • PeopleSoft Enterprise
  • Siebel

Will keep you posted with some more updated on OUM time to time.

To be continued ....

dgreybarrow Reference

Posted in Methodology/Process | 1 Comment »

E2E Business Processes

Posted on March 21st, 2009 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

E2E Business Processes based implementaion always provide a means for engaging the functional communities who perform the activities within the process steps. some of E2E flows are:

  • Acquire-to-Retire
  • Concept-to-product
  • Cost Management
  • Hire-to-Retire
  • Market-to-Prospect
  • Order-to-cash
  • Plan-to- Produce
  • Plan-to-Stock-inventory
  • Procure-to-Pay
  • Prospect-to-order
  • Record-to-report
  • Service Request-to-Resolution
  • Campaign-to-cash

Posted in Methodology/Process | No Comments »

A bit on Oracle’s business flow

Posted on November 27th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Do you know in Oracle EBS there are more than 30+ pre-defined integrated process flows available to cater today's competitive marketplace, where speed, value & Simplicity are important factors to drive the implementation cycle. These concepts are fully aligned with the method enhancements, in the following ways:

  • Time required to implement is reduced by using the pre-seeded assets in the delivery (Speed). This is achieved by pre-seeded, pre-tested, certified deliverables for faster implementation.
  • The focus on solving customer business processes brings value to the customer instead of talking about product features and functions (Value).
  • Key performance indicators identified with each Flow also brings value in that they provide a means to measure the leverage points of the flows (Value).
  • Starting with a pre-tested flow, and avoiding a lengthy analysis of the current environment, provides a simple way to begin any Oracle Applications implementation (Simplicity).

Some of the important business flow's with oracle applications are:
businessProcess

Posted in Methodology/Process | 2 Comments »

What is CEMLI’s Framework?

Posted on July 2nd, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Some one asked today what is CEMLI's framework in oracle....I have no answer at that time. It was surprise for him to know that , after so many years playing with EBS, never have come across this terminology.. :)

Anyway,here are some of extracted information for you.

CEMLI Defined as Configurations,Extensions, Modifications,Localizations and Integrations, all of which refer to recommended ways in which the standard solutions could be modified, if required.

"Oracle defined the CEMLI Framework, which translates into 20 classes of extensions that customers can add to their Oracle systems."

The framework was established by Oracle On Demand to categorize customizations, meaning software that had to be added by the customer or implementer to the Oracle applications.

Another classic example of software that must be added to the system unique to a specific application is a localization. Localizations are country-specific requirements statutory and country-specific business practices that are not included in the standard software package.

To Simplify CEMLI is Oracle's published guidelines for developing and implementing custom extensions to Oracle Applications.

Posted in Methodology/Process | 6 Comments »

Oracle’s Application Implementation Methodology (AIM) : Part – II

Posted on June 29th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

As promised, here is yet another detailed analysis for AIM's.

Big -5 Implemenation consulting companies uses AIM (Application Implementation Methodology) to manage all of its Oracle Application projects. AIM can also be used for other different software implementations and does not limited to only Oracle Applications. However, the methodology was/is purposely built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind, as these are initially used for oracle consulting guys, and with time these are adopted methodology in Oracle application across the industry.

The following Oracle Applications Areas are covered by AIM:

  • Oracle Financials
  • Oracle Distribution
  • Oracle Human Resources
  • Oracle Manufacturing
  • Oracle Projects
  • Oracle Process Manufacturing
  • Business Intelligence

AIM incorporates two things. First, it is a methodology showing what tasks are required, what order they should be completed in, and what resources are required . Secondly,it provides deliverable templates for all the tasks that require them. Hence the hybrid of methodology with a deliverable template tool makes AIM a powerful product.

One biggest disadvantage of AIM methodology is that is very complicated. Complicated in the sense it has ample number of deliverables which are more than 225 in number. In other word , the project time frame can be makes direct impact on this methodology , i mean to say if you tried to use them all you would be spending atleast 9-12 months implementing a 3 month project. AIM is supposed to be used by experienced project managers that pick and choose the tasks they require for each project.Most of Consulting company have fine tuned and took tailored approach for AIM's methodology, based of there standard implementation practice.

AIM defines business needs at the beginning of the project and maintains their visibility throughout the implementation. It defines internal, external, and time sensitive business events and maps each event to the responding business and system processes. Using this method, the client gains an accurate understanding of the business requirements that need to be focused on during the course of the implementation.

AIM Structure Framework

AIM is a framework of related elements. It involves phases, processes, tasks and dependencies:

  • A task is a unit of work, which results in a single deliverable. That deliverable may take many different forms like reports, schedules, code, or test results for example.
  • A process is a closely related group of dependent tasks, which meets a major objective. A process is usually based on a common discipline.
  • A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver projects.

Processes and phases are explained in more detail below.

handProcesses

A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialization and background. A brief description of the AIM processes are given below:

1. Business Requirements Definition: Business Requirements Definition defines the business needs that must be met by the implementation project. You document business processes by identifying business events and describing the steps that respond to these events.

2. Business Requirements Mapping: Business Requirements Mapping compares the business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. As gaps between requirements and functionality emerge, they are resolved by documenting workarounds, alternative solutions, application extensions, or by changing the underlying business process.

3. Application and Technical Architecture: During the Application and Technical Architecture you design an information systems architecture that reflects your business vision. Using the business and information systems requirements, this process facilitates development of a plan for deploying and configuring the hardware required for a successful implementation.

4. Module Design and Build: Module Design and Build produces custom software solutions to gaps in functionality identified during Business Requirements Mapping. Custom software solutions include program modules that must be designed, built, and tested before they can be incorporated into the system.

5. Data Conversion : Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The first step of this process explicitly defines the business objects that are required for conversion and the legacy source systems that store these objects. The converted data may be needed for system testing, training, and acceptance testing as well as for production.

6. Documentation :Documentation begins with materials created early in the project. Using detailed documents from the project, the writing staff develops user and technical material that are tailored to the implementation.

7. Business System Testing: Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. It supports utilizing common test information including data profiles to promote testing co-ordination and to minimize duplication of test preparation and execution effort.

8. Performance Testing:Performance Testing enables you to define, build, and execute a performance test. Use the results to make decisions on whether the performance is acceptable for the business and to help propose tactical or strategic changes to address the performance quality shortfall. Performance Testing is closely related to Application and Technical Architecture; they are interdependent.

9. User Training:Training prepares both users and administrators to assume on the tasks of running the new application system. It includes development of materials and methods as well as administration. Instructors and courseware developers orient their material toward roles and jobs, and not toward application modules.

10.Production Migration : Production Migration moves the company, system, and people to the new enterprise system. Following production cutover, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cutover, and post-production support

The Process can easily understood by this diagram against Phases discussed below.

aimprocess

handPhases

An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal. During a project phase, your project team will be executing tasks from several processes. A brief description of the AIM processes are given below:

1. Definition: This consist of review the organization's business objectives, evaluate the feasibility of meeting those objectives under time, resource, and budget constraints. Moreover this can be best consider as SOW(statement of work) preparation phase.

2. Operations Analysis:During Operations Analysis, the project team develops Business Requirements Scenarios based on deliverables from Definition that are used to assess the level of fit between the business requirements and standard application functionality. Gaps are identified and corresponding solutions developed. The analysis results in a proposal for conducting business operations under the envisioned application technical architecture. Solutions for gaps evolve into detailed designs during Solution Design.

3. Solution Design:The purpose of Solution Design is to develop the detailed designs for the optimal solutions to meet the future business requirements. During this phase, project team members create detailed narratives of process solutions developed during Operations Analysis. Supporting business requirements may require building application extensions to standard features; several alternative solutions may have been defined during Operations Analysis. The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.

4. Build:The coding and testing of all customizations and other custom software including enhancements, data conversions, and interfaces is done during Build. Policy and procedure changes relating to business process modifications are developed. Business system testing is performed to validate that the developed solutions meet business requirements. If customizations, extensions, or conversions are not required, Build is still important because it includes the business system test, which is commonly conducted as a formal conference room pilot. The business system test validates the solutions and is performed in an environment that closely resembles production.

5. Transition: During Transition, the project team deploys the finished solution into the organization. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the end users while the technical team configures the production environment and converts data. Transition ends with the cutover to production, when end users start performing their job duties using the new system.

6.Production: Production begins immediately with the production cutover. It marks the last phase of the implementation, and the beginning of the system support cycle. Included in this final phase is a series of refinements and performance measurement steps. The inhoues MIS/IT Department personnel work quickly to stabilize the system and begin regular maintenance. They will provide the ongoing support to the organization for the remaining life of the system. During Production, you compare actual results to project objectives.

For more Information about AIM's ..here is the link for you..

Posted in Methodology/Process | 11 Comments »

Page 1 of 212

« Previous Entries