We all struggle with complexity of designing, building and maintaining BI apps. Why? Among many other reasons, the simplest one is that there's just too many components involved. Just to name a few
Data modeling (star schemas, cubes)
Delivery (portals, schedulers, emails, etc)
For years there were many attempts to automate some of these steps via metadata. So rather than than coding source to target SQL transformations or DDL for DW generation vendors came up with, what I know call "1st generation" metadata driven BI tools, such as
ETL tools where metadata auto-generated SQL scripts for data extraction, loading and transformation
BI tools where metadata auto-generated SQL for queries
Data modeling tools where metadata auto-generated logical data models and DDL for physical data models
But, the "2nd generation" metadata driven BI apps (note apps vs tools now) do much more. For example, they:
Use metadata to generate multi vendor apps (like BalancedInsight, Kalido and BIReady do), and having a single place where changes can be made
Use metadata to generate all three (ETL SQL, BI SQL, DW DDL, like Cognos, Wherescape, BIReady do), and having a single place where changes to all 3 can be made
Using metadata to generate report layouts (like Cognos does)
Jean-Jacques Rousseau wrote, man is born free and is everywhere in chains. So too Enterprise app deployments are conceived as self contained yet everywhere are integrated with legacy and complementary apps.
My colleague Ken Vollmer and I are looking at packaged apps integration best practices and how these might change as some apps move to the cloud. We are asking:
What kind of middleware do you use?
How do you help process owners to assemble (composite) processes that have transactional integrity?
What do you do about the conflicting data models of apps from different stables – for example yours and those of a third party or perhaps in –house?
How far can so called “canonical” data models and meta data help to overcome such problems?
If you have experience and an opinion about what constitute the top three best practices in such packaged apps integration, or if you can warn about the three most egregious pitfalls to avoid we would love to talk with you.
Forrester analysts will host a Tweet Jam on March 24, 2010, from 1:00 – 3:00 PM USA ET (6 to 8 PM GMT) to answer questions from business and IT executives about the top challenges they face in orchestrating customer-facing business processes to drive top-line growth. During this interactive Jam session, Forrester analysts will share results of our latest research into the topics of: customer experience management, CRM technologies and vendor trends, social media, and business process management.
Key questions we will tackle during this Tweet Jam include:
What are the key trends you need to take into account in planning CRM initiatives in 2010?
How do you know if you are delivering a differentiated customer-experience, and does it make a difference to the bottom line?
Social CRM: The real deal, or blogger hype?
How do CRM vendor solutions stack-up, and which ones are really delivering results?
Does business process management (BPM) “lean-thinking” have a place in CRM strategies?
Drowning in (bad) customer data: What to do about it?
How to take advantage of next-generation Business Intelligence tools for deeper customer insights?
Who should lead your customer management process improvement efforts?
What are the best ways to drive user adoption of CRM technologies?
What change management strategies and skills are needed to succeed?
What are the right metrics for success?
CRM pitfalls: What are they, and are there new ones to worry about?
After the recent board changes the strategy will change too
After the recent board changes at SAP the message we could read in most news was like ‘new board – old strategy’. Along with the board changes SAP did not announce (yet) any significant strategic changes. But what good is it to change the board and leave everything else as is?
The recent SAP board changes are just the visible tip of the iceberg of much deeper changes SAP will and has to go through to renew itself as a leading IT vendor. Below are 10 predictions for changes in SAP’s strategic direction I expect within the next 10+ months:
1. More SAP Board Changes Will Come
Additional board changes will further strengthen the product & technology focus and competence within the SAP board. See also Forrester’s blog on the recent SAP board changes: SAP CEO Resigns – Long Live The Co-CEOs
2. Business ByDesign Will Get Back Into SAP’s Strategic Center
Business ByDesign will become again the corner stone of SAP’s growth strategy and the successful introduction will mark a ‘make it or break it’ milestone for SAP.
3. SAP Announces The Next-Generation ERP
SAP will announce a next-generation ERP solution to regain leadership in its core business area and it will likely be based on the ByDesign platform.
4. SAP Changes Its Cloud Strategy
SAP will rework its whole On-Demand strategy and will unify and align all components based on the ByDesign platform. See also Forrester’s recent blog on SAP’s On-Demand strategy: SAP Is Skydiving Into The Clouds.
Hi, I'm happy to report that analyst George Lawrie of our team that serves Application Development and Delivery Professionals has been working with a host of analysts from across the company to put together our first-ever SAP Jam on March 22-25!
Today Collabnet announced the acquisition of Agile PPM vendor Danube. As an Agile PPM vendor Danube are farmous for their support for Scrum, with their offerings ScrumWorks and ScrumWorks Pro. With this acquisition, Collabnet has taken a significant step in merging the disciplines of Agile project and portfolio management with ALM. Collabnet has traditionally stayed away from supporting any one-process model, describing themselves as process agnostics. This started to change at the end of 2009 with the TeamForge 5.3 release, which provided simple support for Agile projects. Now with the purchase of Danube Collabnet will continue to extend their support for Agile projects. So, why should Application development professionals care?
The NoSQL Movement Is Gaining Momentum, But What The Heck Is It?
The NoSQL movement is a combination of an architectural approach for storing data and software products (such as Tokyo Cabinet, CouchDb, Redis) that can store data without using SQL. Thus the term NoSQL.
The mobile channel is increasingly relevant in business strategies, application architectures and applications of financial services firms. Consequently, we are all aware that the headline represents a strong exaggeration. So, why this statement? Is there any substance in it that application architects, application developers, and enterprise architects need to consider? Interactions with a number of banks indicate that the answer is yes.