Friday, February 18, 2005
Saturday, February 12, 2005
CanyonBridge -- Web Services integration framework and deployment platform
"Using cbIntegrate, CanyonBridge's Web Services integration framework and deployment platform, CanyonBridge applications can be easily combined as 'application blades' with other enterprise applications to create a new and exciting generation of enterprise software with rich, highly interactive clients for Web browsers and wireless devices that rival installed desktop applications. "
Friday, February 11, 2005
Wednesday, February 02, 2005
Sun rolls out pay-per-use computing
cost:
- $1 per microprocessor per hour
- $1 per gigabyte used storage per month
- $1 per microprocessor per hour
- $1 per gigabyte used storage per month
Why JP Morgan Chase Really Dropped IBM - And Got Swallowed by BankOne
In August 2004 JP Morgan cancelled a $5 billion outsourcing contract with IBM after 21 months. Why? Because in the meatime they merged with Bank One, which had gained a reputation for consolidating data centers and eliminating thousands of computer applications.
The company's CIO, Austin Adams, said at the time: "We believe managing our own technology infrastructure is best for the long-term growth and success of our company ... to become more efficient." JP Morgan Chase would now switch from IBM to self-sufficiency to take advantage of BankOne's cost-cutting know-how.
But there's more behind it.
Here's some very interesting figures (MEDIAN VALUES, 1999-2003):
JP Morgan Case <-> Bank of America / Citicorp / Wachovia / Wells Fargo
I.T. spending per employee: $ 28.297 <-> $12.729
Compensation per employee: $110.702 <-> $55.057
Return on shareholder equity: 9.45% <-> 15.79%
JP Morgan Case simply paid way too high salaries to its employees, and in the consequence got swallowed by its competitor.
The company's CIO, Austin Adams, said at the time: "We believe managing our own technology infrastructure is best for the long-term growth and success of our company ... to become more efficient." JP Morgan Chase would now switch from IBM to self-sufficiency to take advantage of BankOne's cost-cutting know-how.
But there's more behind it.
Here's some very interesting figures (MEDIAN VALUES, 1999-2003):
JP Morgan Case <-> Bank of America / Citicorp / Wachovia / Wells Fargo
I.T. spending per employee: $ 28.297 <-> $12.729
Compensation per employee: $110.702 <-> $55.057
Return on shareholder equity: 9.45% <-> 15.79%
JP Morgan Case simply paid way too high salaries to its employees, and in the consequence got swallowed by its competitor.
Tuesday, February 01, 2005
InfoWorld Interview with SAP's Kagermann: The role and importance of a Business Process Platform
SAP plans to extend the Netweaver platform into a Business Process Platform.
Kagermann: Behind NetWeaver is a fundamental shift in architecture, which we call enterprise service architecture, or services-oriented architecture as it is also called in the industry. The idea behind this architecture is to give people on the outside access to functions inside our technology. In this sense, NetWeaver is a kind of composition platform for them to compose services.
We could stop with NetWeaver, but if customers really want to adapt more quickly to new business models and be more innovative with their use of business software in the future, then they also need to be able build new services faster and with greater flexibility. To achieve this, we will take what is generic enough in our technology, such as components, business objects and processes like billing, and put these into an application platform. So if a company wants to develop a new add-on application, it now has access to functionalities such as CRM (customer relationship management) and SCM (supply chain management) through open interfaces.
What all this means is that we want to create reusable processes at the application level and combine these with NetWeaver. This, in a nutshell, is the idea behind our new Business Process Platform. It's essentially an evolution of NetWeaver with the added capability to run ready-to-run processes.
IDGNS: Does this mean you ... give customers the choice between developing their own applications like CRM and SCM to run on your platform or buying these ready-built from you?
Kagermann: Exactly. Customers won't have to plug into our CRM application completely if they want to use our CRM technology. Instead, if they so choose, they can make use of reusable pieces -- available through the new Business Process Platform -- to compose their own application. A reusable part, for example, could be the order management function of our CRM application, which is the same in our ERP system. ... Now with the Business Process Platform, we're taking NetWeaver and melding it with a piece of the applications layer. This new platform, in turn, supports a higher services layer, which isn't hard-coded but model-driven. Here I can imagine consultants composing processes and building analytic tools. We will offer applications at this level but so will others in competition with us. ... Oracle still believes everything revolves around data. We say everything revolves around processes.
Kagermann: Behind NetWeaver is a fundamental shift in architecture, which we call enterprise service architecture, or services-oriented architecture as it is also called in the industry. The idea behind this architecture is to give people on the outside access to functions inside our technology. In this sense, NetWeaver is a kind of composition platform for them to compose services.
We could stop with NetWeaver, but if customers really want to adapt more quickly to new business models and be more innovative with their use of business software in the future, then they also need to be able build new services faster and with greater flexibility. To achieve this, we will take what is generic enough in our technology, such as components, business objects and processes like billing, and put these into an application platform. So if a company wants to develop a new add-on application, it now has access to functionalities such as CRM (customer relationship management) and SCM (supply chain management) through open interfaces.
What all this means is that we want to create reusable processes at the application level and combine these with NetWeaver. This, in a nutshell, is the idea behind our new Business Process Platform. It's essentially an evolution of NetWeaver with the added capability to run ready-to-run processes.
IDGNS: Does this mean you ... give customers the choice between developing their own applications like CRM and SCM to run on your platform or buying these ready-built from you?
Kagermann: Exactly. Customers won't have to plug into our CRM application completely if they want to use our CRM technology. Instead, if they so choose, they can make use of reusable pieces -- available through the new Business Process Platform -- to compose their own application. A reusable part, for example, could be the order management function of our CRM application, which is the same in our ERP system. ... Now with the Business Process Platform, we're taking NetWeaver and melding it with a piece of the applications layer. This new platform, in turn, supports a higher services layer, which isn't hard-coded but model-driven. Here I can imagine consultants composing processes and building analytic tools. We will offer applications at this level but so will others in competition with us. ... Oracle still believes everything revolves around data. We say everything revolves around processes.
Subscribe to:
Posts (Atom)