Our lead example in this chapter is the open-a-new-market approach being developed by InterPro Global Partners. InterPro views itself as an IT consulting firm that specializes in providing advice to its clients on how to globalize products (translations, packaging, cultural modifications); how to perform application integration; and how to develop Web-based applications. The company has about 160 consultants located in the United States and Europe and has revenues of over $20 million annually. InterPro has its own application development framework and methodology that helps the company to understand business process flow (how work flows within organizations) and to develop corresponding technical solutions to improve flow efficiency.
Recent advances in Web technologies specifically the maturation of certain Web standards now enable InterPro to create applications that perform "Web services" for ad hoc communities of users in healthcare, insurance, financial services, real estate, and dozens of other industries. The company's self-image may be changing from that of an IT consulting firm to that of "a creator and builder of global communities."
Sidebar 6-1 |
The beauty (from a business perspective) of what InterPro has done for the healthcare community is that its model is replicable. InterPro understands how business processes work, how the Web service technologies work, and how to go about building ad hoc Web communities. Because InterPro and its partners have been able to identify a willing community of doctors who desire access to streamlined interactions with their business partners, and because the company understands business processes and the new Web services technologies, InterPro has been able to develop an approach that attracts laboratories and pharmacies as subscribers who underwrite the cost of running the ad hoc healthcare Web community. In essence, InterPro has birthed a new business model and this model is fully replicable to other professional communities.
By using its core skills in process flow, technology deployment, and application integration, the company believes that it is ideally positioned for success across these multiple markets.
This InterPro example illustrates how a company can create new services and bring those services to market using Web services technologies.
As pointed out in previous chapters, strict adherence to Web services standards is not required in order to build Web services applications. InterPro makes use of some Web services standards such as a private UDDI directory to help its business partners find out about each other, and the company uses SOAP to bind sessions. But notice how the company uses Microsoft's COM/DCOM APIs for program-to-program communications instead of WSDL (the reason could be the comparative immaturity of WSDL at this juncture or the fact that the company already had COM/DCOM code available, and using it was the quicker path to market). At most early-adopter sites this kind of mix-and-match approach to building Web services is common, but over time, as Web services directories and other protocols mature, expect Web services standards to dominate as the preferred method of building Web services enabled applications.
Note also how the company has focused on streamlining not only the communications among various business partners but on streamlining the business process itself. This streamlined workflow is where the biggest payback is delivered by this Web service customers ultimately buy into InterPro's service because it enables them to run their businesses more efficiently.