Writes Line56.com: “Forrester predicts market comeback; cross-channel integration, verticalization, Web services, new pricing models weigh in; Microsoft to ascend”.
Category: Enterprise Software
Enterprise Enabling Technologies
Line56.com: Line56.com lists the enabling technologies, as identified by AMR:
– application servers
– business-to-business (B2B) exchange platforms
– business intelligence (BI)/analytics
– enterprise security
– integration, business process management (BPM)
– systems management
– wireless application platforms
Had read in a separate article in BCR about the four building blocks for corporate networks: VPNs, VoIP, Wireless and Web Services.
Slate on Web Services
Writes Slates, in an introductory article:
A Web service is just a special type of Web page, but instead of being formatted prettily for the human eye, the page is formatted for a computer to read. The technology makes it easy for some Web site developers (like Amazon’s) to produce such a page and for other developers (like me) to retrieve the information therein. Suddenly any Web site (including yours) can display up-to-the-minute information from Amazon or Google, whether it be “people who bought my book also bought ….” or “the top 10 news stories on the Web.”
Web services are like LEGOs: They snap together in almost limitless combinations. As the big sites bring their Web services on board it’s easy to imagine your home page summarizing the items you have for sale on eBay, displaying whether you’re available to chat via AOL or Yahoo!, and mapping the current location of the airplane you’re on via Expedia.
For the Web consumer, it will quickly become unremarkable to see information and services from many providers combined in imaginative and useful ways. Suddenly no Web site is an island, and maybe no toaster either.
Web Services for EAI and B2BAI
John Radko writes on the why Web Services will become one of IT’s most significant innovations:
One reason is that Web services allow managers to start with the technologies they already have on hand.
Also, Web services offer IT a way to finally resolve the painful problem of application integration. That makes it a supremely valuable tool for businesses implementing Web services in areas like order management, shared forecasts, or connection of internal systems.
For example, consider the hypothetical case of a buyer wanting to inquire about the status of an order. The seller’s manufacturing system would need a SOAP interface. Then the buyer’s purchasing system could “call” the seller’s system over the Internet using Extensible Markup Language (XML) and ask, “When will my order ship?”
His conclusion: the true promise of Web services is in reducing costs, not eliminating them.
Web Services Adoption Timeline
From a white paper by IDC on “IBM and the Strategic Potential of Web Services”:
2002: Within the Firewall
– simplified application integration
– increased developer productivity2004: Contained External Users
– simplified business partner connectivity
– richer application functionality
– subscription-based services2006: Fully Dynamic Search and Use
– casual ad-hoc use of services
– new business models possible
– commoditisation of software
– pervasive use in non-traditional devices
This seems to be too slow a deployment – perhaps, it is applicable to the larger enterprises. Increasingly, I feel that web services area great opportunity for the have-nots in the world of software. By combining software standards and business process standards, they can do cost-effectively what the bigger companies will take years to do. The smaller enterprises have little legacy. If they have a framework which can be implemented by using shareable business process components (so that each business does not have to go through the same learning), they can be closer to the dream of a real-time enterprise.
EDI to Web Services
VANs shift EDI layer, writes InfoWorld:
In the long term, according to Stefan Overtfeldt, program director of WebSphere technical marketing at IBM, companies will switch to Web services because they are based on the simple concept of requests that incorporate XML and wait for results, and because EDI has an extensive vocabulary.
If companies can convert smaller suppliers to Web services as opposed to more manual, paper-based methods, the savings could be substantial, said Kimberly Knickle, an analyst at AMR Research in Boston. Typically, a company that has EDI in place is using it with 20 percent of its supplier base, she said. However, the company often purchases the lion’s share of its goods from those remaining 80 percent of its supply base, she added.
Ingram Micro, a global IT distribution company based in Santa Ana, Calif., is finding that more smaller solutions partners want to use Web services for connectivity, said Guy Abramo, chief strategy and information officer.
Today, Ingram connects mostly via FTP, Excel spreadsheets, and Word documents.
“We’re start to look at things like wrapping XML-translated messages that might communicate with standard accounting packages … that a small company may use,” Abramo said. “These are small businesses that typically have a back office function of three people. They will want acknowledgement of the order and acknowledge[ment] of shipment. That is a large part of what we may be doing in the next couple of years.”
Enterprise Systems’ Top100
A look at the top influencers, forces, technologies and products in large enterprise computing.
Top 4 Technologies: Web Services, Data Warehousing, Linux, CRM
Top 5 Technologies which have lived up to expectations: Java, Linux, XML, Linux on Mainframe, Web Services
Top 5 Technologies which have failed to match to their hype: Windows 2000 Datacenter, ASPs, ERP II, Bluetooth, CRM
Enterprise Software: Way Forward
There are two aspects to what we are doing in our vision to create enterprise software applications for the mass market: within the enterprise, and between enterprises.
Within the enterprise, we want to build (a) the software components, (b) the business process framework – what I’ve called Visual Biz-ic, and (c) the business process libraries from different organisations. The layers of the solution will look like this:
Digital Dashboard
Web Browser
Customised Enterprise Modules
Enterprise Components
Basic Software Components
Application Server (JBoss)
Database (PostgreSQL)
The three layers in the middle are what we will need to develop. The Digital Dashboard (comprising an RSS Aggregator and a Blogging tool) comes from the other project that we are doing . All that the enterprise software modules will need to dois to put out events in RSS format.
We need to create the building blocks, and then work with Independent Software Vendors (ISVs) who can take this platform and customise for different verticals. It is possible that to jumpstart this process, we ourselves may need to create the enterprise modules for some verticals.
Across enterprises, we want to use RosettaNet Basics as the business process standards for exchanging documents. While RosettaNet has only been made for certain industries, it is generic enough to be usable by most SMEs. What is needed is for one of the bigger enterprises (which interacts with a lot of SMEs) to mandate the use of RosettaNet for its interactions.
To make this happen, the three areas that we will need to understand well are:
– Web Services: all software we develop should have XML/SOAP interfaces, so the components can be re-used. (An idea here is to take existing open source software components on the Web, and provide them withan XML/SOAP interface.)
– J2EE/EJB: We will use Java as the building platform, with an Application Server (JBoss). Also look at some of the IDEs like NetBeans and Eclipse.
– RosettaNet: for inter-business communications
In the near-term, we need to:
– build an Accouting+CRM module which integrates with Tally, but is architected using the component structure described above. Later, add additional modules for HR, Payroll, etc.
– implement RosettaNet for our interactions with our channel/support partners
Basically, we need to think of “edge services” as we attempt to make inroads into enterprises.
Two ideas which require more thought:
– Enterprise Emulator
– Slashdot for SMEs
Will get to them sometime later.
Amazon and Web Services – Tim O’Reilly
Tim O’Reilly writes provides a wider perspective on web services: “So much of the industry emphasis in web services has turned to EAI and B2B type applications that a lot of people miss the real transformation that is happening. Once they have SOAP or XML-RPC (or even REST-style) APIs, web-facing databases become program components.”
A few other points Tim makes:
– Web sites like Amazon and Google are applications. And Microsoft has demonstrated over and over again that a platform strategy beats an applications strategy every time. Once you have other companies building added value that relies on you, you have a kind of benign industry lock in that’s a real competitive advantage. [See my earlier post on Platform Leadership]
– A mistake a lot of companies make when entering new markets (especially ones that are discontinuous with the current ones) is to think too hard about where the money is coming from. Disruptive innovations often don’t work all that well at first, so you have to give them room to grow before you try to harvest them. The lesson of the dot-com boom is actually the opposite of the one that people are taking. It’s not “figure out your business model first,” it’s “don’t get greedy; give the market time to mature before you rush to cash out.” (Aside: This is also part of the secret of open source. People do cool things for reasons other than money, because they solve small scale, specific problems that wouldn’t be touched by commercial vendors. (These problem spaces sometimes grow into big markets, but they don’t look that way at first.))
– Companies need to think not just what they can get for themselves from new technologies, but how they can enable others. A marketplace is like an ecosystem. The more life there is, the more there is for everyone.
Also see my earlier post on Tim O’Reilly on Web Services, where he takes of the Internet OS, and Tim’s article on “Inventing the Future“.
Enterprise Computing Weblog
Phillip J. Windley is Chief Information Officer (CIO) for the State of Utah, serving on the Governor’s Cabinet and as a member of his Senior Staff. [via John Robb]
You must be logged in to post a comment.