Beruflich Dokumente
Kultur Dokumente
3 Key Characteristics
As described in [2], the key characteristics of Oracle methodology for implementing
packaged software, methodology known as Applications Implementation Method (AIM) for
Business Flows, that support these objectives include:
A business process focus
A predefined Future Process Model (i.e. Business Flows) as a starting point
Early introduction of hands-on familiarization and testing
Iterative testing cycles
3.1 A Business Process Focus
Oracle Business Flows are central to the AIM for Business Flows implementation
approach. A business flow is a sequence of related business processes designed to achieve a critical
business objective. Business flows often cross-organizational and application boundaries, reflecting
how business is actually conducted within an enterprise. Order to Cash is an example of a
business flow, that addresses the revenue cycle of a business.
Because Business Flows are expressed in neutral business language familiar to business
people, they improve Oracles ability to communicate with customers about how they can manage
their business using Oracle Applications. This focus on business processes, rather than on product
features and functions, contributes to better communications between customer and implementers,
resulting in improved understanding of business requirements and software options/ capabilities,
etc.
3.2 Oracle Business Flows as the Starting Point
Oracle Business Flows reflect standard business practices for an industry, optimized for
Oracle Applications. They represent a leading practice approach to employing standard
functionality contained in Oracles E-Business Suite to satisfy common business requirements. AIM
for Business Flows employs Oracle Business Flows as the starting point for an implementation.
By positioning Oracle Business Flows as the proposed future process model, and
employing iterative, hands-on testing cycles to refine the model, its possible to expedite the
establishment of an application instance suitable for testing early in the project, thereby achieving
significant savings in time and effort.
Additionally, by effectively demonstrating how the customer can operate the business using
Business Flows employing standard functionality, the approach also increases the likelihood that
the Application software will be implemented without unnecessary customizations or extensions,
resulting in additional savings.
AIM for Business Flows also recognizes, and leverages, pre-seeded delivery materials,
which are based upon the Business Flows, to streamline the implementation. These accelerator
assets, such as pre-defined Business Flow diagrams, Application setup documents, and pre-seeded
test scripts provide a baseline set of deliverables that are usable, with little or no modification, to
support the initial round of testing. The assets are updated, as changes are identified, to support
subsequent testing cycles.
Likewise, refinements identified in CRP 2 are also reviewed with the customer and, if approved,
incorporated in the delivery materials in preparation for CRP 3.
Several business architecture workshops are planned during the Definition Phase, which are
designed to assist the customer in defining suitable Chart of Accounts, Multi-Org, and Trading
Community Architecture structures, which have implications across the entire E-Business Suite.
Application extensions, if required to fill gaps in functionality, are identified during the first and
second CRP cycles, designed and built during Elaboration and Build phases, and tested during CRP
3.
Should more than one iteration of CRP 2 and/or CRP 3 be necessary due to the complexity
of the engagement, or other criteria, the method provides the flexibility to plan those additional
iterations, as indicated in the diagram.
5 Key Features
AIM for Business Flows was developed with the following key features:
Scalability
Structured Framework
5.1 Scalability
AIM for Business Flows was designed with scalability in mind. From the largest, multinational, multi-site, multi-entity projects, through to the smallest, limited size, constrained scope
projectsAIM for Business Flows provides the scalability required by each unique project. AIM
for Business Flows identifies implementation tasks and task steps as either core or optional.
A foundation of core tasks defines the minimum set of steps necessary to implement Oracle
Applications. Task selection guidelines aids in determining which optional tasks to include in the
project plan. This greatly reduces the complexity for the project management team in planning the
work effort required for the implementation.
configuration changes resulting from CRP 2.0 are also validated during this test cycle. Only minor
changes should be identified, if any, during this test evolution.
Transition
During Transition, the project team deploys the new system into the organization. All the
elements of the implementation must come together to transition successfully to actual production.
The project team trains the users while the technical team configures the Production Environment
and converts data. Transition is a demanding experience for the project team, and in particular, for
the users who have to maintain exposure to two systems until a new production system is declared.
Production
The Production phase starts immediately with the production cutover. Production marks the
last phase of the implementation and the beginning of the system support cycle. Included in this
final phase is a series of refinement and measurement activities. The Information Systems (IS)
personnel work quickly to fine-tune the system and begin regular maintenance. They provide
ongoing support to the organization for the remaining life of the system. If multiple deployments
exist, Production occurs at different times for the various geographical sites and/or business units.
5.2.2 Project Processes for Continuity
All AIM for Business Flows tasks are organized into processes that group related
deliverables together. Project team members are assigned to these groupings according to their
specialization and background.
Business Process Mapping
Business Process Mapping addresses the activities surrounding the customers initial
familiarization with Oracle Business Flows, and the initial mapping of the customers business to
the Flows. It also encompasses the definition of customer data needed to personalize the system
for the customer, including the Chart of Accounts, Multi-Org, and TCA structures. Iterative revision
activities related to
Business Flows, procedures, and application setups, which are completed after each
Conference Room Pilot (CRP) cycle, are also part of Business Process Mapping.
Application and Technical Architecture
During the Application and Technical Architecture process, the project team designs the
information system architecture around the organizations business vision. Included are Oracle,
third party, and custom applications; computing hardware; and networks and data communications
infrastructure.
Module Design and Build
The Module Design and Build process produces custom application extensions to fill gaps
in functionality identified during Conference Room Pilots 1 and 2. Custom systems include
program modules (forms, reports, alerts, database triggers, and so on) that must be designed, built,
and tested before they can be incorporated into the new system. Module Design and Build addresses
the design and development of the custom modules; the Business System Testing process supports
testing of custom modules.
Data Conversion
The Conversion process defines the tasks and deliverables required to convert legacy data
to the Oracle Application tables. The first step of this process is to explicitly define the data
business objects identified for conversion along with the legacy source systems. System testing,
training, and acceptance testing require converted data before production cutover.
Documentation
The Documentation process begins with documentation standards materials created early in
the project to build quality operation support reference materials. Documentation requirements and
implementation complexity are closely correlated, and the amount and level of detail in the
documentation varies by project.
Business System Testing
The Business System Testing process is a formal, integrated approach to testing the quality
of all application system elements. It focuses on preparing for testing early in the project lifecycle,
linking testing requirements back to business requirements, and securing project testing resources.
The Business System Testing process takes on additional significance in an AIM for Business
Flows implementation because of its early introduction in the project and the iterative nature of the
testing, or Conference Room Pilot cycles, in the approach. Business System Testing tasks make up
the majority of CRP 2 and CRP 3 activities, where the configuration of the future business system is
refined, finalized and validated.
Performance Testing
The Performance Testing process helps the project team define, build, and execute a
performance test on specific system configurations. This process provides a powerful and direct
means of assessing the performance quality of the system. This assessment enables the customer to
determine whether performance is acceptable, and to propose changes and perform tuning to correct
any initial performance shortfall.
Adoption and Learning
The Adoption and Learning process accelerates the implementation teams ability to work
together through team building and organization-specific application learning. This process also
helps determine human support requirements so that the organization structure and job roles align to
meet new performance expectations resulting from the technology change. Learning needs of all
personnel impacted by the implementation are considered, and appropriate training materials and
learning events are developed and conducted.
Production Migration
The objective of the Production Migration process is to migrate the organization, systems,
and people to the new enterprise system. Following production cutover, additional objectives
include monitoring and refining the production system and planning. The Production Migration
process encompasses transition to production readiness, production cutover, and post-production
support.
6. Deployment Strategy
AIM for Business Flows method materials (i.e. guidelines/documentation, workplans,
accelerator assets, and deliverable templates, etc.) are being deployed to delivery consultants via
Oracle Consultings iProjects toolset. Oracle iProjects is a hosted, Internet platform for project
execution and knowledge management. iProjects allows project teams (Oracle consultants,
customers and partners) to collaborate "virtually" to deliver e-business solutions better and faster, at
a lower cost.
By leveraging iProjects ability to create tailored project workspaces, pre-seeded with
method materials appropriate to the engagement, project teams are able to access the most current
and up-to-date materials available from the customer location, or anywhere else.
7. Conclusions
AIM for Business Flows is the latest iteration of Oracles proven Application
Implementation Method (please refer to [1] for further details regarding prior releases of the
method). It incorporates changes that support the use of Oracle Business Flows, asociated software
environments, and pre-seeded implementation assets, to accelerate the implementation timeline and
keep the focus of an implementation on business processes and benefits, rather than software
features and functions.
Some hallmarks of the AIM for Business Flows approach include:
A Business Process Focus
Use of pre-defined Oracle Business Flows as the starting point Future Process
Model
Rapid establishment of a software environment, based on Oracle Business Flows,
for use in mapping the customers business to Oracle Business Flows
Early introduction of iterative hands-on user testing cycles
The AIM for Business Flows approach is applicable to any assemble to order engagement
involving the implementation of Oracles E-Business Suite, for which pre-defined business flows
exist.
Like earlier versions of AIM, AIM for Business Flows is intended to be a complete,
comprehensive delivery method, which addresses all potential aspects of an implementation. As
with previous versions of AIM, not all tasks need to be performed on every project. Task selection
guidelines incorporated in the method assist Project Managers and practitioners in determining
which tasks are appropriate for a given project, based on the specific circumstances of the
engagement.
References
Robert KOMARTIN, Metodologii de realizare a sistemelor informatice integrate. Taxonomii
metodologice, Informatica Economic vol. VI, nr. 3/2002, pag. 55 58
[2] ***, Applications Implementation Method (AIM) Advantage Handbook, Oracle Corporation,
2004
[1]