Oracle Aim Methodology

96,096 views

Published on

Oracle Aim Methodology

Published in: Technology
12 Comments
62 Likes
Statistics
Notes
No Downloads
Views
Total views
96,096
On SlideShare
0
From Embeds
0
Number of Embeds
1,742
Actions
Shares
0
Downloads
5,499
Comments
12
Likes
62
Embeds 0
No embeds

No notes for slide

Oracle Aim Methodology

  1. 1. Oracle AIM Methodology<br />An Overview<br />Presented By:-<br />Shivmohan Purohit<br />
  2. 2. Agenda<br />What is Oracle AIM<br />Oracle AIM – Structure<br />Oracle AIM – Phases<br />Oracle AIM – Processes<br />Oracle AIM – Preview / Demo<br />Recommendations<br />Questions<br />
  3. 3. Software Development Methodology<br /><ul><li>Waterfall
  4. 4. Prototyping
  5. 5. Incremental
  6. 6. Rapid Application Development
  7. 7. Rational Unified Process
  8. 8. Agile Unified Process</li></li></ul><li>Project Management Methods<br /><ul><li>Project Management Institute – PMBOK
  9. 9. PRINCE 2
  10. 10. Critical Chain Project Management
  11. 11. Process based Project Mgmt
  12. 12. Agile Project Management</li></ul>Before moving ahead, Let’s capture the Answers for some AIM Related Questions !!<br />
  13. 13. Oracle Methodologies<br />Oracle AIM 3.1 ( Application Implementation Methodology)<br />Oracle EMM ( Easy Migration Methodology)<br />Oracle Unified Method ( OUM)<br />Our discussion is focus on “Oracle AIM”, version 3.1 ( also known as AIM Advantage)<br />
  14. 14. What Oracle says about AIM<br />Highest degree of quality<br />Quick return on investment<br />Short time to benefit<br />AIM brings a proven process to the table for implementing Oracle E-Business Suite Business Solutions with<br />
  15. 15. A Complete, Effective Toolkit<br />Deliverable Templates<br />All delivered in an easy-to-use, web-based interface<br />Pre-seeded Content and Sample Data<br />Customizable Workplans<br />Project Management Support<br />Detailed Task Description<br />On-line, Context Sensitive Documentation<br />
  16. 16. What is Oracle AIM<br />Oracle AIM provides templates for all the tasks that require them.<br />The methodology is purpose built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind.<br />Oracle AIM is a methodology showing what tasks are required, what order they should be completed in, and what resources are required<br />
  17. 17. Oracle AIM - Advantages<br />Oracle's AIM is a proven approach for implementing packaged applications. It comprises a set of well defined processes that can be managed in several ways to guide you through an application implementation project.<br />AIM provides the tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement business solutions.<br />AIM defines business needs at the beginning of the project and maintains their visibility throughout the implementation. <br />It defines internal, external, and time sensitive business events and maps each event to the responding business and system processes.<br />Client gains an accurate understanding of the business requirements that need to be focused on during the course of the implementation.<br />
  18. 18. Oracle AIM - Structure<br />A task is a unit of work, which results in a single deliverable. I. e reports, schedules, code, or test results for example. <br />A process is a closely related group of dependent tasks which meets a major objective. A process is usually based on a common discipline.<br />A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver projects. <br />
  19. 19. Oracle AIM – Project Phases<br />An AIM project is conducted in phases that provide quality and control checkpoints to co-ordinate project activities that have a common goal.<br />During a project phase, your project team will be executing tasks from several processes<br />Oracle AIM Project Phases as follows ( 6 Phases )<br />Definitions<br />Operation Analysis<br />Solution Design<br />Build<br />Transition<br />Production<br />
  20. 20. Oracle AIM – Project Phases<br />Definition<br />Plan the project<br />Review the organization's business objectives<br />Evaluate the feasibility of meeting those objectives under time, resource, and budget constraints<br />Emphasis is on building an achievable work plan and introducing it with guidelines.<br />Strategies, objectives, and approaches are determined for each AIM process<br />Establishing scope early in the implementation gives the team a common reference point and an effective way to communicate.<br /><ul><li>Operations Analysis
  21. 21. Project team develops Business Requirements
  22. 22. Assess the level of fit between the business requirements and standard application functionality.
  23. 23. Gaps are identified and corresponding solutions developed.
  24. 24. Solutions for gaps evolve into detailed designs during Solution Design.</li></li></ul><li>Oracle AIM – Project Phases<br />Solution Design <br />Develop the detailed designs to meet the future business requirements.<br />Project team members create detailed narratives of process solutions developed during Operations Analysis<br />Supporting business requirements may require building application extensions to standard features<br />The project team carefully scrutinizes these solutions and chooses the most cost effective alternatives.<br /><ul><li>Build
  25. 25. coding and testing of all customizations and other custom software
  26. 26. Coding & testing of enhancements, data conversions, and interfaces
  27. 27. Policy and procedure changes relating to business process modifications are developed.
  28. 28. Business system testing is performed to validate that the developed solutions meet business requirements.</li></li></ul><li>Oracle AIM – Project Phases<br />Transition<br />Deploys the finished solution into the organisation <br />The project team trains the end users<br />Technical team configures the production environment and converts data<br />Transition ends with the cutover to production, when end users start performing their job duties using the new system.<br /><ul><li>Production
  29. 29. It marks the last phase of the implementation, and the beginning of the system support cycle.
  30. 30. The Information Systems (IS) personnel work quickly to stabilise the system and begin regular maintenance.
  31. 31. Provide the ongoing support to the organisation for the remaining life of the system.
  32. 32. Compare actual results to project objectives.</li></li></ul><li>Oracle AIM – Processes<br />A process in AIM represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs.<br />A task can belong to only one process.<br />Project team members are usually assigned to a process according to their specialization and background.<br />12 Processes as referred in AIM – <br />Project Management<br />Business Process architecture<br />Business Requirement Definition<br />Business requirement definition<br />Application & technical architecture<br />Module Design & Build<br />Data Conversion<br />Documentation<br />Business System Testing<br />Performance Testing<br />Adoption & Learning<br />Production migration.<br />
  33. 33. Oracle AIM – Processes<br />Project Management ( PJM)<br />Project & Phase Planning, Execution, Control, Reporting & Completion<br />Work Management & Resource Management<br />Quality Management & Configuration Management<br />Project Management itself is a comprehensive process and has separate way to handle it, i.e. PMBOK , Oracle PJM etc<br />Task ID<br />CR: Control & Reporting , WM: Work Management, RM: Resource Management<br />QM: Quality Management, CM: Configuration Management<br />
  34. 34. Oracle AIM – Processes<br />Business Process Architecture<br />Task Code/ID : BP<br />Provide the framework for combining change in business processes with implementation of software applications <br />It focuses on high-level business processes and operations generally applicable to the organization<br />Make business focused decisions either to change the current processes to suit the application or to customize the application.<br />Commonly used templates<br />
  35. 35. Oracle AIM – Processes<br />Business Requirements Definition<br />Task Code/ ID: RD<br />Defines the business needs that must be met by the implementation project.<br />Develop a complete set of business requirements scenarios that can be used to map business requirements to application functionality.<br />Analyze and identify the reporting requirements for the business<br />Carefully document audit and control requirements to satisfy financial and quality policies.<br />Commonly used templates<br />
  36. 36. Oracle AIM – Processes<br />Business Requirements Mapping<br />Task Code/ ID: BR<br />Ascertain the fitness for use of application features in satisfying detailed business requirements expressed at a business process step level.<br />Business Requirements Mapping encompasses the following areas: <br />Mapping<br />Business system testing<br />Application setups<br />Mapping is an iterative approach with the following objectives:<br />Prove business process designs through demonstration<br />Identify gaps in the application<br />Propose feasible bridges to gaps<br />Commonly used templates<br />
  37. 37. Oracle AIM – Processes<br />Application & Technical Architecture<br />Task Code/ ID: TA<br />Design an information systems architecture to realize the business vision.<br />This process divide into two areas:- 1. Application Architecture, 2. Technical Architecture<br />The process takes the business and information systems requirements and develops a blueprint for deploying and configuring:<br />Oracle, third-party, and custom applications<br />Supporting application server environments<br />Critical interfaces and data distribution mechanisms between applications, servers, and sites<br />Computing hardware, including servers and client desktop platforms<br />Networks and communications infrastructure<br />
  38. 38. Oracle AIM – Processes<br />Module Design & Build<br />Task Code/ ID: MD<br />Focus on the design and development of customizations to satisfy functionality gaps identified during Business Requirements Mapping (BR).<br />Modification — changes to the base Oracle Applications code<br />Extension — new forms, reports, programs, tables, interfaces and triggers that add functionality without changing the base application code<br />Configurable Extension — addition of functionality through flex fields, alerts, and other configuration options provided by the Applications<br />Continue to Next Slide<br />Commonly used templates<br />
  39. 39. Oracle AIM – Processes<br />Module Design & Build<br />
  40. 40. Oracle AIM – Processes<br />Data Conversion<br />Task Code/ ID: CV<br />Convert and test all necessary legacy data for the operation of the new system<br />Conversion Approaches<br />Manual Conversions<br />Programmatic Conversion with or w/o tools<br />Automated Data Entry<br />
  41. 41. Oracle AIM – Processes<br />Documentation<br />Task Code/ ID: DO<br />Reference that shows the users how to use application functionality<br />Set of procedures for using the application in response to day-to-day business events<br />Documents that describe the technical details of the application for the maintenance staff<br />Produce a set of procedures for managing the system<br />
  42. 42. Oracle AIM – Processes<br />Business System Testing<br />Task Code/ ID: TE<br />Three main aspects of Business Testing – Planning, Early Introduction of Testing & CRP<br />Business System Testing does not address performance testing or the testing of data conversion programs<br />
  43. 43. Oracle AIM – Processes<br />Performance Testing<br />Task Code/ ID: PT<br />Enables you to define, build, and execute a performance test.<br />To make decisions on whether the performance is acceptable for the business<br />Propose tactical or strategic changes to address the performance quality shortfall.<br />Automated V/s Manual<br />Types of Performance Testing<br />System Performance <br />Module/ Code Performance<br />Hardware and Networks<br />
  44. 44. Oracle AIM – Processes<br />Adoption & Learning <br />Task Code/ ID: AP<br />Training prepares both users and administrators to assume on the tasks of running the new application system<br />Adoption and Learning impacts the following five major audiences:<br />Executives<br />Implementation project teams<br />Functional managers<br />Users<br />Information technology groups<br />
  45. 45. Oracle AIM – Processes<br />Production Migration<br />Task Code/ ID: PM<br />To migrate the organization, systems, & people to the new enterprise system<br />Assessing readiness for transition to production<br />Executing cutover to the new system<br />conducting post-production support<br />
  46. 46. Oracle AIM - DEMO<br />Oracle AIM Advantage 3.1 Demo<br />Templates<br />Q&A<br />Discussion<br />
  47. 47. My Experience & Thoughts<br /><ul><li> MD050– Functional Design
  48. 48. MD070 –Technical Design
  49. 49. System Integration Testing
  50. 50. CV010 – Data conversion Strategy
  51. 51. CV060 – Data Conversion Templates
  52. 52. PM010 –Transition Strategy
  53. 53. TE040 –Test Scripts
  54. 54. BR110 – Security Profiles (Roles and Responsibility Matrix)
  55. 55. User Acceptance Testing (UAT)
  56. 56. Cutover and Production Migration Plan
  57. 57. End User Training (End User Manual)
  58. 58. BR100 –Application Set up
  59. 59. CR010 – Project Management Plan / Project Plan (WM020)
  60. 60. Overview Training
  61. 61. RD010 – Organization Structure
  62. 62. RD020 – Business Requirement Gathering
  63. 63. RD050 / BR030 – MAP Business Requirements
  64. 64. TA040 –Application Architecture Strategy
  65. 65. CRP Session I
  66. 66. BP080 – Future Business Model
  67. 67. BR010 – GAP Analysis
  68. 68. CRP Session II</li></li></ul><li>A Sample Project Level Activities<br />
  69. 69. Some Recommendations<br />Follow the documentation principle like Preparer, reviewer with dates and approvers with version controls details in all documents.<br />Try to avoid Word, Excel, PPT attachments to the templates.<br />Collect enough details from client to prepare the process flow.<br />Stick on to the Project schedule to submit the documents on time.<br />Ensure to fill the open and closed issues on all updates if any.<br />Follow the uniformity in using templates across all modules.<br />Avoid providing internal intranet URL etc for reference.<br />Follow the Oracle Custom standards while preparing Technical Docs.<br />Documents prepared by one person must be reviewed by another before submitting to Client.<br />Get a sign off from client and as well as from PM on all docs.<br />
  70. 70. Questions ?<br />Presented By:-<br />Shivmohan Purohit<br />

×