1 / 82

AIM for Business Flows Method Overview

AIM for Business Flows Method Overview. Agenda. Installing the ABF Desktop Method Pack Navigating the ABF Method Pack Method Overview ABF Project Flow: Definition Phase ABF Project Flow: Elaboration Phase ABF Project Flow: Build Phase ABF Project Flow: Transition Phase

badrani
Download Presentation

AIM for Business Flows Method Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AIM for Business Flows Method Overview

  2. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  3. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  4. Method Pack Description • Easy to Install • Single downloadable installation file • One click installation (self extracting process) • Designed to accept updates • Self Contained • Easy to use • Minimal learning curve (Standardized across method offerings) • No requirement to understand underlying file structure • HTML interface to all materials…only two clicks away • Tight integration between all method offering components

  5. Installation Process • Installing the AIM for Business Flows Desktop Method Pack is a three (3) step process: • Step 1 – Obtain the self-extracting zip executable file • Step 2 – Double-click on the ABF14.exe file • Step 3 – Follow instructions displayed during installation Note the following tips during installation process… • Be patient…let the process complete • It is okay to reinstall…prefer this versus stopping process • The method offering will display in your default browser • For desktops with XP, you may need to adjust your Pop-up blocker settings (The install process will not complete until you close the browser window)

  6. Post Installation • Congratulations, you now have AIM for Business Flows Method Pack installed on your desktop! • All method components are located in a protected, pre-designated directory structure on C:\Method, which you have access to through anHTML user interface… • Launching AIM for Business Flows Desktop Method Pack: • Click “start” • Click “All Programs” • Place cursor on “Oracle Methods” • Slide cursor over to “AIM for Business Flows 1.4 and left mouse click

  7. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Working with Templates • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  8. Online Walkthrough of the ABF Method

  9. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  10. What is AIM for Business Flows? • Latest iteration of Oracle Consulting’s proven Application Implementation Method (AIM) • Incorporates changes that: • Promote a business process focus • Employs Conference Room Pilots (CRPs) • Iterative Approach • Does not restrict tailoring of Flows or system configuration to satisfy client requirements

  11. Approach Objectives • Rapidly deploy an environment using Standard Business Flows, and pre-tested configurations Standard => “Future Process Model” • Incorporate user involvement throughout the lifecycle using iterative conference room pilots (CRPs) • Employ CRP’s to map business flows to customer business processes and identify gaps • Flows are reasonably “good fit” • Customer´s willingness to adopt basic elements of E-Business Suite best practices as described in flows

  12. Definition Elaboration Build Transition Production Project Planning Prepare CRP 2 Environment Create and test Custom Extensions Prepare Production Environment Prepare for CRP 2 Workshop(s) Prepare CRP 3 Environment Build Required Assets Conduct CRP 2 Workshop(s) Prepare for CRP 3 Workshop(s) Convert and Verify Data Conduct CRP 3 Workshop(s) Conduct Business Architecture Workshops Design Extensions Verify Production Readiness Prepare Custom Test Scripts Perform Systems Integration Test Prepare for CRP 1 Workshop(s) Conduct CRP 1 Workshop(s) Solution Review & Sign-Off Perform User Acceptance Test Begin Production Maintain System Conduct Phase End Review Conduct Phase End Review Conduct Phase End Review Propose Future Direction Approach Overview – Top Level Flow

  13. Method Structure Fundamentals • Ataskis a unit of work that results in output of a single work product or revision of an existing work product (deliverable) • A phase is a chronological grouping of tasks in an approach. Services are delivered by phase to reduce project risk. Phases allow checkpoints against project goals and measurement of quality. • A process is a grouping of tasks within a method based on common functions or disciplines which lead to one or more key deliverables.

  14. Build Transition Definition Elaboration Production Definition Phase Objectives: • Plan the project • Familiarize customer with Flows • Map Flows to the Business • Identify potential changes Key Activities: • Build/update Delivery Assets • Prepare CRP 1 Environments • Conduct Business Architecture WS • Customer Education on CRP Process • Conduct CRP 1 Outputs: • CRP 1 Results • Preliminary Conceptual Architecture • Key Configurations (COA, TCA, Multi-Org)

  15. Production Build Transition Definition Elaboration Elaboration Phase Objectives: • Validate COA, TCA, Multi-Org Setups • Refine mapping of Flows • Identify remaining changes • Design Custom Extensions • Determine/freeze scope of solution Key Activities: • Prepare CRP 2 Environment • Design custom extensions • Conduct CRP 2 • Solution Review and Sign-off Outputs: • Refined Configuration • Approved designs for customizations • Conversion Data Mapping • Updated Test Scripts • High-Level Solution Document

  16. Production Build Transition Definition Elaboration Build Phase Objectives: • Develop, test, and accept custom software • Propose a transition strategy • Execute performance test • Conduct a system test • Finalize the solution Key Activities: • Create & test custom extensions • Prepare CRP 3 Environment • Conduct CRP 3 • Conduct User Acceptance Test Outputs: • System Tested Applications • User Acceptance Test Results • Performance Test Report • Transition and Contingency Plan

  17. Production Build Transition Definition Elaboration Transition Phase Objectives: • Prepare Production Environment • Convert and verify legacy data • Train user personnel • Transition to Production Key Activities: • Plan Transition • Go-Live Checklist • Final System Check • Users & Support Ready • Convert & Load Data • Fallback Plan Outputs: • Converted and verified data • Skilled Users • Production Support Infrastructure • Production system ready • GO-LIVE

  18. Production Build Transition Definition Elaboration Production Phase Objectives: • Maintain the Production System • Measure System Performance • Promote user acceptance • Propose and plan future direction Key Activities: • Assess effectiveness of system • Reinforce adoption of system • Recommend Business direction • Recommend technical direction Outputs: • Effectiveness Assessment • Business Direction Recommendations • Technical Direction Recommendations

  19. Production Build Transition Definition Elaboration ABF Processes BF Process TA Process MD Process CV Process DO Process TE Process PT Process AP Process PM Process A process is a grouping of tasks within a method based on common functions or disciplines which lead to one or more key deliverables

  20. ABF Process Objectives [BF] Business Process Mapping:The goal of the BF process is to familiarize the Customer with Oracle Business Flows and conduct the initial mapping of flows to the client’s business. [TA] Application and Technical Architecture: The goal of the TA process is to design an information system architecture that realizes the business vision. [MD] Module Design and Build: The MD process focuses on the design and development of custom extensions to satisfy gaps in functionality. [CV] Data Conversion: The goal of the Data Conversion process is to convert all legacy data necessary for the operation of the new system. [DO] Documentation: The Documentation process augments Oracle Applications manuals with information about custom extensions and business procedures.

  21. ABF Process Objectives (Cont.) [TE] Business System Testing:The Business System Testing process has the goal of refining the business solution through iterative Conference Room Pilots and testing the quality of all elements of the application system. [PT] Performance Testing: The Performance Testing process involves the definition, construction, and execution of a performance test. [AP] Adoption and Learning: The Adoption and Learner (AP) process fosters acceptance of the new applications by all users [PM] Production Migration: The goal of the Production Migration (PM) process is to migrate the organization, systems, and people to the new enterprise system.

  22. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  23. Definition Phase Objectives Objectives of the Definition Phase include: • Define Project Scope clearly • Verify Senior Executive Buy-in • Facilitate Informed Project Startup Decisions • Build Consensus around scope, objectives and approach • Familiarize Client with Business Flows • Perform initial mapping • Develop preliminary conceptual architecture • Determine high-level requirements • Obtain Approval to proceed to next phase

  24. Definition Elaboration Build Transition Production Project Planning Prepare CRP 2 Environment Create and test Custom Extensions Prepare Production Environment Prepare for CRP 2 Workshop(s) Prepare CRP 3 Environment Conduct CRP 2 Workshop(s) Prepare for CRP 3 Workshop(s) Build Required Assets Convert and Verify Data Conduct CRP 3 Workshop(s) Conduct Business Architecture Workshops Design Extensions Verify Production Readiness Prepare for CRP 1 Workshop(s) Prepare Custom Test Scripts Perform Systems Integration Test Conduct CRP 1 Workshop(s) Solution Review & Sign-Off Perform User Acceptance Test Begin Production Maintain System Conduct Phase End Review Conduct Phase End Review Conduct Phase End Review Propose Future Direction Key Activities – Definition Phase

  25. Project Planning • Define and Confirm Scope* • Review Project Approach* • Define Management Strategies and Processes* • Prepare Project Management Plan (PMP)* • Obtain Client Approval of PMP* • Orient and Train Project Team * Performed in Project Startup Phase when using PJM 4.1

  26. Build Required Delivery Assets • ABF is “aware of”and leverages pre-defined/pre-seeded delivery assets to “accelerate” the implementation • Business Flows • Core Functionality Definitions • Application Setup Documents • System Test (Demo) Scripts • Inventory available delivery assets • Determine “degree of fit” • Identify missing delivery assets • Identify delivery assets requiring modification • Build/Modify delivery assets, as necessary

  27. Conduct Business Architecture Workshops • Workshops for identifying key setup parameters that apply across the entire EBS: • Multi-Org Structure • Chart of Accounts (COA) Structure • Trading Community Architecture (TCA) • Other Workshops to consider: • Other Key Flexfields (Asset Category, Inventory Itm) • SysAdmin Security • Territory Manager (CRM Flows) • Roles, Groups, Team (CRM Flows) • Architecture Review and Performance Mgmt Assessment Workshop

  28. Prepare for CRP 1 Workshops • Review status of CRP 1 Environment preparation • Ensure “tailoring” of environment is completed, if required • Conduct test to verify proper configuration • Determine number of Business Flow streams/ number of workshops per stream • Identify demo/test scripts to be conducted during each workshop • Identify participants (including Client personnel) • Schedule Workshops and participants • Gather and review demo/test scripts

  29. Conduct CRP 1 Workshops • CRP 1 typical duration ~ 2 weeks • Initial session to orient participants and familiarize client with baseline Flows • Recommend assignment of facilitator and scribe, if possible • Hands-On session ½ day + Review results • Execute test scripts as scheduled on the pre-configured system • Familiarize client with Business Flows • Map standard Flows to client’s business • Document potential changes needed (Change Catalog) • Review all changes identified at end of each workshop session

  30. High-Level Solution Document [Initial] • Prepare it based on CRP 1 results • Describes Business Flows and associated functionality to be implemented • Future Process Model (diagrams) • Narrative description of processes • Explicitly identifies any standard functionality that will not be implemented

  31. Conduct Phase-End Review • Review proposed business process changes or other modifications • Document/present options for filling gaps • Prepare MoSCoW prioritization of proposed changes • Must Have • Should Have • Could Have • Won’t Have • Obtain client approval/signoff

  32. Definition Elaboration Build Transition Production Business Process Mapping (BF) Application & Technical Arch. (TA) Module Design and Build (MD) Data Conversion (CV) Documentation (DO) Business System Testing (TE) Performance Testing (PT) Adoption and Learning (AP) Production Migration (PM) Active Processes – Definition Phase

  33. Key Deliverables of the Definition Phase • Skilled Project Team • Mapped Business Data • Preliminary Conceptual Architecture • Project Readiness Roadmap • CRP 1 Workshop Results • Test Script results • Change Catalog • Updated Business Flows • Updated Application Setups • Updated Test Scripts/Scenarios • Phase-End Review Results

  34. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  35. Elaboration Phase Objectives Objectives of the Elaboration Phase include: • Conduct CRP 2 to refine the solution • Validate decisions on Multi-Org, COA, and TCA structures • Refine the technical architecture design • Develop Performance Testing models and scenarios • Design the security architecture • Develop designs for Custom Extensions • Develop Test Scripts • Design Performance Test Scripts and Programs • Develop User Learning Plan

  36. Definition Elaboration Build Transition Project Planning Prepare CRP 2 Environment Create and test Custom Extensions Prepare Production Environment Prepare for CRP 2 Workshop(s) Prepare CRP 3 Environment Conduct CRP 2 Workshop(s) Prepare for CRP 3 Workshop(s) Build Required Assets Convert and Verify Data Conduct CRP 3 Workshop(s) Conduct Business Architecture Workshops Design Extensions Verify Production Readiness Prepare for CRP 1 Workshop(s) Prepare Custom Test Scripts Perform Systems Integration Test Conduct CRP 1 Workshop(s) Solution Review & Sign-Off Perform User Acceptance Test Begin Production Maintain System Conduct Phase End Review Conduct Phase End Review Conduct Phase End Review Propose Future Direction Key Activities – Elaboration Phase Production

  37. Prepare CRP 2 Environment • Begin with a freshly installed,unconfigured Applications environment • Hosted or Onsite • Configure environment to incorporate: • Client’s Multi-Org structure • Client’s Chart of Accounts (COA) Structure • Client’s Trading Community Architecture (TCA) • Other changes identified during CRP 1 • Oracle Accelerator Pre-Production instance with Setup Tool an option

  38. Prepare for and Conduct CRP 2 Workshops • Ensure Key Delivery Assets are updated with changes, including: • Business Flows • Test Scripts/Business Flow Scenarios • Application Setup Documents • Business Procedure Documentation (Tutor Procedures) • Plan and schedule CRP 2 Workshops • Execute CRP 2 Test Scripts/Scenarios • Document needed changes • Objective – identify all remaining changes so scope can be frozen

  39. Design Custom Extensions & Prepare Test Scripts • Define and Estimate Application Extensions and Interfaces • Review alternative solutions with client and obtain approval to proceed with selected option • Create Functional Design • Design Database Extensions • Create Technical Design • Review Functional and Technical Designs • Obtain client acceptance • Develop Unit Test Scripts • Develop Link Test Scripts

  40. Solution Review and Sign-Off • Finalize High-Level Solution Document • Review proposed business system with client/Project Steering Committee • Obtain Client acceptance of the proposed solution and approval to proceed.

  41. Conduct Phase-End Review • Review proposed business process changes or other modifications • Document/present options for filling gaps • Prepare MoSCoW analysis of proposed changes • Must Have • Should Have • Could Have • Won’t Have • Obtain client approval/signoff

  42. Definition Elaboration Build Transition Production Business Process Mapping (BF) Application & Technical Arch. (TA) Module Design and Build (MD) Data Conversion (CV) Documentation (DO) Business System Testing (TE) Performance Testing (PT) Adoption and Learning (AP) Production Migration (PM) Active Processes – Elaboration Phase

  43. Key Deliverables – Elaboration Phase • CRP 2 Results • Conceptual Architecture • Application and Database Server Architecture • Platform and Network Architecture • Application Extension Definition and Estimates • Approved Designs – Custom Extensions • Conversion Program Designs • Updated System Test Script • System Integration Test Script • User Learning Plan • High-Level Solution Document [Final] • Solution Acceptance & Signoff

  44. Agenda • Installing the ABF Desktop Method Pack • Navigating the ABF Method Pack • Method Overview • ABF Project Flow: Definition Phase • ABF Project Flow: Elaboration Phase • ABF Project Flow: Build Phase • ABF Project Flow: Transition Phase • ABF Project Flow: Production Phase • Planning an ABF Project

  45. Build Phase Objectives Objectives of the Build Phase include: • Prepare the Development Environment • Develop, test and accept custom software • Create, test and accept database extension and installation routines • Propose a transition strategy • Finalize the solution • Conduct CRP 3 (System Test) • Conduct Performance Test

  46. Definition Elaboration Build Transition Production Project Planning Prepare CRP 2 Environment Create and test Custom Extensions Prepare Production Environment Prepare for CRP 2 Workshop(s) Prepare CRP 3 Environment Conduct CRP 2 Workshop(s) Prepare for CRP 3 Workshop(s) Build Required Assets Convert and Verify Data Conduct CRP 3 Workshop(s) Conduct Business Architecture Workshops Design Extensions Verify Production Readiness Prepare for CRP 1 Workshop(s) Prepare Custom Test Scripts Perform Systems Integration Test Conduct CRP 1 Workshop(s) Solution Review & Sign-Off Perform User Acceptance Test Begin Production Maintain System Conduct Phase End Review Conduct Phase End Review Conduct Phase End Review Propose Future Direction ABF V1.3 Top Level Flow

  47. Create and Test Custom Extensions Create: • Prepare Development Environment (MD.090) • Create Database Extensions (MD.100) • Create Application Extension and Interface Modules (MD.110) • Create Installation Routines (MD.120) Test: • Perform Unit Test (TE.070) • Perform Link Test (TE.080) • Perform Installation Test (TE.090)

  48. Prepare CRP 3 Environment • Begin with a freshly installed,unconfigured Applications environment • Hosted or Onsite • Configure environment to incorporate: • All changes confirmed in CRP 2 • New changes identified in CRP 2 and approved • Oracle Accelerator Pre-Production instance with Setup Tool an option • Employ Data Conversion programs to load legacy data • Employ installation routines to install custom extensions

  49. Prepare for and Conduct CRP 3 Workshops • Ensure Key Delivery Assets are updated with changes from CRP 2 • Update Test Scripts to include business processes involving custom extensions and converted legacy data • Plan and schedule CRP 3 Workshops • Consider how best to integrate custom extensions • Execute CRP 3 (System Test) Scripts • Validate Business Procedure Documentation • Document needed changes (minor changes OK) • Objective – System Test/Validate the system

  50. Perform Systems Integration Test • Test Oracle E-Business Suite integration with other application systems • Conducted in a Production-like environment • Objective – validate the operation of the business system across and between application systems • Includes testing of operating routines and procedures, as well as programs

More Related