Migration BO 4.0 Challenges
Migration BO 4.0 Challenges
Migration BO 4.0 Challenges
0 Migration Challenges
http://www.apos.com/content/business-objects-4-0-migration-challenges
The migration challenges facing executives, platform managers, administrators, developers, report
writers and BI technicians as they adopt SAP's BI 4.0 platform are considerable, but not overwhelming.
It all comes down to project planning and preparation. Let's look at some of the most important
Business Objects 4.0 migration challenges.
Major considerations include:
Project size
Project schedule
Project resources
System criticality
System security
Data integrity
Regulatory compliance
Personnel training
There are many good reasons for Business Objects 4.0 migration (PDF), including improved data access,
usability and integration, but the most important reason is to embrace the future of business
intelligence within your organization. Committing to best practices and a well managed migration will
vastly increase the probability of realizing the benefits, reducing deployment costs, and improving
return on investment.
The migration process will be long and challenging. Let's start with some best practices that will help you
draw up a migration checklist.
BI 4.0 Migration Planning Best Practices
It's hard to over-estimate the importance of planning for your BI 4.0 migration. It is a truism for all
project management professionals: the more detailed your planning upstream, the better you will be
able to deal with contingencies downstream, and the closer you will get to completing your project on
schedule and on budget while delivering maximum benefit to your organization.
As you address your Business Objects 4.0 migration challenges, think first about the evolution of BI
within your organization. Can you remember a time when a small handful of administrators pushed out
a set of simple reports to a set group of executives and managers? If your experience is similar to that of
most BI practitioners, you have seen the size and complexity of your BI deployment grow rapidly along
with its impact within your organization, and the expectations of your information consumers.
Your BI deployment is a living system. It needs to be ready for new demands, and you need to be ready
to meet those demands through efficient, streamlined, and automated processes and best practices.
These growth factors need to be addressed when you consider:
Project size Is BI 4.0 migration manageable as a single all-encompassing project? Or do we
need to break it down by function, business unit, or some other classification? Do we need to
migrate all reports and instances? Or can we be selective while still complying with the letter
and spirit of regulatory compliance, and the needs of our information consumers? What tools
do we have that can help us inventory our system and understand the magnitude of this
project?
Project schedule What are the hard deadlines for each task on the schedule? Are the SDKs
available for custom features required by your deployment?
Project resources Are the personnel (universe designers, report designers, administrators,
testers) available and committed to the project schedule? Will we require new or additional
hardware to accommodate increased processing requirements and 64-bit architectural
advances?
One-time tasks Your project plan will include a number of one-time tasks that are labor- and
time-intensive, and potentially highly prone to human error. Examples: UNV to UNX conversion,
Web Intelligence report repointing, Crystal Report conversion, Desktop Intelligence report
scheduling, publishing and migration. Are there ways to automate and simplify these tasks so
that they don't extend your project schedule and rob you of resources you might better invest
elsewhere? See BI 4.0 Upgrade Resources for suggestions on how you can manage these tasks.
Report & Universe designers Do they understand the differences in Universes and Crystal
Reports in BI 4.0, both on the conceptual and process levels?
Line-of-business power users do they understand changes to the interface? Are they ready to
give up DeskIs?