You are currently browsing the category archive for the 'Internet Commerce' category.

It was interesting to visit the Web 2.0 conference last week and see the progress and trends compared to my last year impressions.
Here are some of my thoughts:
- SharePoint is the de-facto standard for Enterprise 2.0 While other vendors have compelling products and features, a CIO that is looking for an internal, comprehensive, secure and maintainable solution has almost only one choice (unless you are on an IBM stack..). Other tools focus on providing point solutions, hosted environments, plugging current SharePoint holes and extending functionality. Microsoft had the biggest and most impressive presence and were heavily promoting the next version SharePoint 2010 that will be launched in the SharePoint conference in October. (Some preliminary details here).
- The field has definitely matured over the last year. There are more case studies and research about usage, benefits and trends although most companies are not sharing explicit ROI numbers. Some vendors have disappeared while others are growing and establishing themselves at a level where they may be considered long term players and safe for the enterprise.
- The experts are still frustrated with the slow rate of adoption and the seeming growing gap between the prevalence of social tools and technologies used by marketing and sales to communicate externally Vs. they almost complete absence internally. The rapid adoption of tools like Facebook and Twitter for customer communication not just in retail but in Healthcare and other industries creates glaring discrepancies where the same companies have no tools internally and sometimes even block their own marketing teams from external use of these tools under some outdated IT policy.
-
IT is still not part of the discussion. That is unfortunate because as Steve Wylie, the conference director expressed in a guest post at ZDNET last week, large scale adoptions will not happen without IT.
“While we could argue that this is a very new market and that businesses take time to change, I also believe that Enterprise 2.0 will be challenged by large-scale adoption until corporate IT is fully on board. Early adoption has been largely driven by business users and department-level managers. They had a problem to solve and were fed up waiting for IT to provide the solutions they needed. They took matters into their own hands by finding workable, web-based solutions and even celebrated this new found freedom from IT. With a few exceptions, IT took a reactive posture to Enterprise 2.0 and viewed it as a threat to be managed, secured and even blocked in some cases.”
- Tactical view. One of the most frequently asked questions was “what is the best way to get started?”. The pretty universal answer for vendors and corporate users was to approach it in a tactical manner and find a specific business problem you can solve using collaboration tools. Be it an HR portal to boost morale, tools to help virtual project teams work more efficiently, sales best practices portal or any of many other ideas. Define a narrow business case and implement. So far, trying to approach this in a strategic manner makes finding ROI a herculean task and as noted above, puts IT on the defensive. I hope that this trend will start to change as these tactical solutions rarely provide long term sustainable benefits.
- Rise of the Community Manager. The most active forum was the one where the newly created function – community managers shared their challenges and tricks for getting people to take part in the social activity. First, It is great to see that many leading organizations have realized the importance of such a task although many had it as a secondary responsibility they volunteered to do rather than a full time position. Creating and maintaining a vibrant and active internal community requires skill, passion and process and the focus should rightfully be as much on that as on the tools that enable the community.
Additional impressions:
What is co-browsing?
Co-browsing lets multiple users work together in their respective browsers through what look like shared screens and communicate via telepresence including video and audio. The impact of this technology is enormous as companies become more virtual and the need for serious collaboration increases to be competitive in tough times. To be able to share, interact and see the body language of your collaborator in real-time without extraordinary downloads to your PC or expensive third party solutions could simply change the way we work. This innovation comes from not Google, or Yahoo but from IBM in a proof of concept project called Blue Spruce, a Web browser application platform that IBM is working on to allow simultaneous multiuser interactions enabled by AJAX and other standard technologies through the Web browser.

The Blue Spruce project is IBM’s solution to the classic one-window, one-user limitation of current Web browsers. The application is a mash-up that combines Web conferencing with voice and video and other data forms to let people share content including existing Web widgets – at the same time. Two different users, possibly anywhere, are able to move their respective mouse pointers around the screen in the browser to click and make changes on the shared application, with the platform enabling concurrent interactions through the browser without disruptions. Despite the appearance, the co-browsers aren’t actually sharing content. Both collaborators obtained a Web page through the Blue Spruce client, but the “events” enabled by the mouse are what is being sent to the Blue Spruce Co-Web Server. The idea is that no matter where the two users are in the Internet world, they pick up the general data caches on both personal computers and react to the events.
The applications for co-browsing collaboration are numerous, especially for knowledge workers. In healthcare, IBM has used Blue Spruce to create an online “radiology theatre” product, currently at the prototype stage, which allows teams of medical experts to “simultaneously discuss and review patients’ medical test data using a Web browser.” The project is being run in collaboration with the Brigham and Women’s Hospital of Boston. According to IBM, it has created a secure Web site that allows select medical experts at Brigham and Women’s Hospital to access and collaborate on data such as CT scans, MRIs, EKGs and other medical tests. Each medical expert can “talk and be seen through live streaming audio/video through their standard web connection, and have the ability to whiteboard over the Web page as well as input information to the patient’s record.” Basically it is a secure multimedia experience running inside a single browser window, using Blue Spruce as the platform.
It is important to note that Blue Spruce is not your typical “fat client” or downloaded application, but it is a fully browser-based application development platform, currently in development, which is being built on open Web standards. The main feature of Blue Spruce is that it allows for a combination of different Web components – data mashups, high-definition video, audio and graphics – to run simultaneously on the same browser page. It’s important to note that the Radiology Theatre app only requires a standard Web browser – so there’s nothing to download for the end user, in this case, doctors.
This is how IBM described how the new online radiology theatre will work:
”A group of doctors can log into a secure Web site at the same time to review and analyze a patient’s recent battery of tests. For instance, a radiologist could use her mouse to circle an area on the CT scan of a lung that needs a closer look. Then using the mouse she could zoom into that scan to enlarge the view for all to see. An expert on lung cancer could use his mouse to show how the spot had changed from the last scan. And then, a pathologist could talk about patient treatments based on spots of that size depending on age and prior health history, paging through clinical data accessible on the site.”
“The theatre allows all these experts to discuss, tag and share information simultaneously, rather than paging through stacks of papers, calling physicians to discuss scan results and then charting the results. This collaborative consultation brings together the personal data, the experts and the clinical data in one physical, visual theatre.”
The impact on rural medicine and the need for telemedicine for key healthcare experts is significantly advanced with this technology.
Perhaps the biggest potential benefit of the online radiology theatre is that it will enable experts from all over the world to consult on cases. The ability for multiple users to “co-browse” means they can interact in the browser in real-time and see each other’s changes. Of course, since this is medical data, there are significant privacy implications involved in using the Internet to collaborate. The time and cost savings from collaboration is important, but better and faster decision making is the key.
The need for inexpensive and minimally invasive techniques for real collaboration over the Internet is real and the backlog of potential applications is fun to consider. Imagine reviewing your health care or insurance claims with a live person (and their reactions) at the insurance company to reduce cycle time, or collaborating on new product engineering drawings from the U.S. with your Chinese manufacturer. Imagine the potential for teaching or training with key experts and a worldwide audience using a live whiteboard. Finally, imagine not paying big monthly fees for basic meeting collaboration needs on a daily basis. Blue Spruce is really a technology to keep an eye on.
We’ve all dealt with requirements that were written by well-meaning, but
technology-confused procurement departments, or business users who believe that people still use the Mosaic Browser (my first graphical browser!). Few authors of quasi-technical requirements put much thought to the actual cost of implementing a modern, rich, dynamic web application on decade-old technology.
A purposely over-the-top hypothetical quote :
The application must support Microsoft Internet Explorer 5.0+, Netscape 4+ at a minimum graphical resolution of 800×600 pixels.
While you may at first chuckle at this obvious bit of anachronism, think back to the last system requirements you spec’ed out for a web application.
What browsers did you ask to support? Were you shocked when the development team told you you couldn’t have that cool AJAX drop-down because your browsers didn’t support it? Were you suprised when compromises had to be made to the look and feel, or flow of the application? How many users really use those old browsers, anyway? How many of your users do?
“They shoot browsers, don’t they?” — Jeremy Keith
Don’t know the answer? Don’t worry, it’s pretty common. A lot of businesses make requests for web-based applications without first doing internal due diligence to understand their target market. Sure, you can build a web application that settles for the lowest common denominator — but why sacrifice when you might not have to?
Understanding your users’ browsing platform should be one of the first steps to building requirements for projects that involve a significant IT spend on web application development, whether it be enhancements to existing applications, or greenfield development.
Here’s 4 reasons why skipping this important step of due diligence will cost you more money, or users, or attention:
- You’ll Be Too Conservative. Fearing that you’ll lose the 0.5% of users who may be on Internet Explorer 5.0, you’ll insist (against your CTO’s recommendation) that all users are important, and if it means sacrificing a few bells and whistles, so be it.
- You’ll Be Too Boring. You’ve heard about rich internet applications, Web 2.0, AJAX? If you’re trying to support these new technologies on browsers that are 5+ years old, forget it.
- You’ll Spend Too Much. The 80/20 rule will be in full effect when you realize late in the development cycle that no one tested with Netscape 7.2. “But it’s in the requirements document!” cries the project sponsor. Frantic testing will unveil the fact that half the functionality is broken or visually skewed. You fire the designer, and the project goes into a death march to the lowest common denominator.
- You’ll Be Unhappy with the Final Product. You’re building the web application to replace your mainframe claims processing system. Or your billing system. Or your financial forecasting package. And the final, boring mess will look exactly like what you had on your old green-screen system, except it’s different. Users are complaining that it’s not easy to use, and your CFO is now revisiting your ROI projections. Projects aren’t supposed to end like this… are they?
Fortunately, judicious use of web analytics and good old fashioned business analysis can provide you with concrete data to build a solid foundation of business cases and technical requirements. The chart below illustrates browser market share over the past 9 months:

Source: StatCounter Global Stats, April 2009
You can see that the bulk of market share goes to a very small percentage of very modern and powerful browsers. How can this information help you? In Part 2 of this series, we’ll explore how up-front legwork in web application development can lead to a happy outcome for all.
Thanks for all those who attended our webinar on implementing web 2.0 strategies last week. If you missed it, the recorded webinar is available on our site. Enjoy.
As I promised, here are some of the questions asked during the session that I have not had time to address:
Q1: Using Facebook and Twitter – how do I get started? How can we monitor it?
Getting started is ridiculously easy. Facebook has a good starter guide . Setting up Twitter is even simpler as there is not much to do other than selecting a name. You have only 15 characters so it is not always an easy task. Twitip has a good guide to best practices in twitting and a list of useful services to track and monitor twitter conversations.
Q2: Why would people want to follow a healthcare organization? How do I promote it without spending money? is it really worth the effort and Investment?
So setting up profiles and pages is easy. The hard part is getting people to follow you on a regular basis. The good news is that you just need to get users to act once and add you to their friends list or follow you on twitter. From that point forward you are just one in a stream of many others.
Spreading the word is done in every way possible, but not through direct advertising. Put it on your website, emails, blog and any other marketing communication form. The best promotion methods are viral. If you have something interesting to say, people will spread the word.
Social media communication tools are just one more way to reach an audience in a fragmented media world but health is something people really care about. If you are a regional hospital, publish daily information your community will want to know. Allergy report, flu alerts, flu vaccine reminders, etc. The cost is usually limited to a resource that will write and maintain all these social media properties. We’ll go into ROI in the next answer but first and foremost the benefit is relevancy. Hospitals that will engage and communicate will be relevant and top of mind. Others will be there when the appendix burst.
Q3: What type of investment is required? What is the ROI
We usually see 2 main areas of investment. The first is Strategy. With so many options, tools, opportunities and risks large organization usually do not just jump in but take some time to look at the landscape, their audience, their revenue centers and their media assets and capabilities to form a cohesive strategy. This is the main area we help clients in as they often lack internal expertise. We usually recommend forming a broader web strategy as these social activities are not isolated from the needs to have an attractive and interactive website than engages users and effective e-marketing programs. The strategy part also looks at the organizational ability to support these types of programs, the skills required and can help in building a cost and ROI structure. The cost of a comprehensive web strategy can range from five to low six figure depending on the size of the organization and scope.
The second area of investment is in the program operations. This usually translates to people who dedicate some of their time to writing content and managing user interactions. It can range from a few hours a week for a small program to a full time position.
The returns: like in any marketing program, these activities are judged by their ability to generate increase in profitable patients and donations. Since they provide a great way to reach an audience without a cost per unit (as you have in email, banners or paid search) the ROI increases as the size of your audience.
Mashable.com has a good overview for the qualitative and qualitative measurements for ROI. I think it goes back to relevancy and the need to be part of your audience daily life.
Illustration: Monica Parra / Newsweek
One of the strongest and most misguided arguments expressed online and in many companies we speak with about Enterprise 2.0 is that it is not strategic.
That this collection of tools, technologies and ideas is not yet mature enough, lacks proven ROI, introduces a myriad of security and governance issues and even if successful is not a priority in today’s soft economy. It is too often delegated to IT managers to experiment with and report back in a few years.
Here’s where the difference is: Enterprise 2.0 is not a technology. It represents first and foremost a new way of thinking, interacting and communicating that includes attitude and cultural changes, empowered by IT. Is there anything more strategic than that and more important to a business future success?
It is arguably the biggest opportunity for IT driven cultural change facing organizations since the introduction of PC networks more than 2 decades ago.
One of the C suite most important tasks is to shape an organizational culture that will make their company innovative, competitive, efficient and successful not just now but in the future. Embracing Enterprise 2.0 now and guiding their employees through this transitional period should be one of their top priorities.
While in a few cases adoption started from the bottom up, a change of this magnitude usually needs to come from the top accompanied by the matching set of values and actions that prove the seriousness and commitment to change.
It requires leadership that is able to see that transparency and increased visibility into activities throughout the company will finally enable them to know what is really happening and will create a culture of trust. That openness and exchange of ideas will lead to innovation and efficiency. That collaboration will enable a diverse workforce to work together in emergent ways while being physically and geographically dispersed.
In short, it requires vision that will set a future path and will ask managers to overcome the obstacles in the way. The type of vision CEO’s need to provide and not delegate to IT managers.
The challenge and opportunity is that not many chief executives have realized yet that embracing Enterprise 2.0 is a strategic imperative and are focusing the discussion around short term ROI.
Dion Hinchcliffe at ZDNET provides a comprehensive review of the evidence and opinions regarding ROI and adoption challenges, and adds his own interesting model of collaboration cause and effect chains that while clearly provide benefits, make them harder to pinpoint and measure.

He also concludes that
“… an accumulating body of knowledge is pointing to potentially dramatic business returns with Enterprise 2.0. If these continue to be borne out, it will affect the competitive and financial positions of the companies that are proactive and therefore their long-term marketplace success“
And wonders what it will take to break the current status quo?
His colleague Dennis Howlett on the other end thinks the ROI is still years off and concludes
“As always, the secret to long term success depends on management’s ability to maintain a sustained commitment and all that goes with it. The difficulty today is that same management is wondering where the next sale comes from or how cash will be generated.”
The good news is that Enterprise 2.0 does not require large capital expenditures but mostly thorough organizational commitment. There has rarely been an opportunity for businesses to gain so much competitive edge by investing so little.
As in many cultural revolutions, by the time Enterprise 2.0 related changes start translating into business differentiators, organizations that have not made the transition will look as outdated as an organization resisting getting these useless PC boxes or adopting email.
While inexpensively built and operated mom and pop e-commerce websites are as common as snow in New England in January, is it possible to build and operate an enterprise grade e-commerce site on a shoe string budget? E-commerce at an enterprise level is not simply slapping a shopping cart to your website and calling it e-commerce enabled. The demands of an enterprise solution may require:
- Integration with legacy systems
- Integration with supply-chain systems
- Support for multiple currencies and tax codes
- Multiple store-fronts
- Profile and history driven offer management
- Integration with a content management system
- Business user control over promotions and pricing
- …and more
Challenges of integration with existing systems alone are daunting enough never mind the fancy e-commerce functionality that is often considered vital for competitive differentiation. No wonder why starting an e-commerce venture or an upgrade is considered a seven figure expense. The cost of an enterprise grade e-commerce product alone can easily account for twenty to forty percent of the budget. The other option is to go with a hosted or SaaS based approach and avoid capital expense for software and infrastructure – not a bad approach for testing the waters but in the long run, charges and fees can really add up.
A well executed e-commerce site can provide great returns on the investment by generating new revenue streams, enhancing existing ones, or reducing operational expenses – and that can’t be too bad for the budget or your career. However, in tough economic times the challenge becomes harder as getting approval for large complex projects becomes difficult and even the approved budgets can get slashed. If your budget gets cut, is there a way to still implement enterprise grade e-commerce? Can an open source e-commerce solution be the answer to the “do more with less” mantra? Is open source e-commerce ready to play with the big boys in the enterprise domain? Let’s explore these questions and the capabilities of the open source e-commerce solutions.
Let’s start with a common misconception that an open source e-commerce product requires significant customizations and the cost of customizations more than offsets any savings from not having to pay license fees. Implicit in this assumption is the notion that a commercial product requires little or no customizations. However, the real-world experience shows us that this is not the case. Even the best commercial products cannot be used out-of-the-box unless you decide to adopt their look and feel and their model of e-commerce. The cost of customizations can add up just as rapidly in a commercial product as they can in an open source one. Therefore a prudent approach would be to adhere to the industry standards and best practices and use out-of-the-box functionality in areas which are not competitive differentiators. Heavy customizations should be limited to the aspects of the website that are true differentiators and result in a unique user experience. This guiding principle applies regardless of the decision to use an open source or a commercial product.
There are a lot of inexpensive and open source e-commerce products out there; however, most of them are nothing more than a simple shopping cart. They are only suitable for the most basic needs of a simple web site. However, Apache OFBiz and Magento are two promising contenders that break from the pack and compete in the enterprise space. In this article we will primarily focus on OFBiz.
Apache OFBiz is actually an integrated suite of products that does not only include e-commerce capabilities but also provides support for accounting, order management, warehouse management, content management and more. An enterprise e-commerce implementation cannot exist as a point solution. It has to integrate and work well with other back office processes and applications. OFBiz’s integrated suite can be used to automate and integrate most back office functions. Even if you decide not to use the built-in functionality it can still be integrated with other existing systems albeit with more effort and cost. It provides enough e-commerce functionality out of the box to match most enterprise needs and the rest can be customized if needed. Here is a summary of our assessment of OFBiz:
Technical Capabilities
| # | Criteria | Rating | Comments |
| 1. | E-commerce capabilities | B+ | Provides Robust e-commerce capabilities OFBiz e-commerce capabilities include: catalog management, promotion & pricing management, order management, customer management, warehouse management, fulfillment, accounting, content management, and more. |
| 2. | Sign-on and Security | B | Granular and robust security framework The OFBiz security framework provides fine grain control of the security including multiple security roles and privileges. Roles can be used to control access to screens, business methods, web requests (URLs), and/or entire applications. |
| 3. | Technical flexibility & ease of use | B | Very flexible but complex OFBiz is an application development platform that can be used to build applications and as such provides a tremendous amount of flexibility. The use of the entire framework (which includes the database, an Object Relational Mapping (ORM) layer, business object layer, scripting support, and UI tools) is optional. |
| 4. | Integration with other apps and locations | A | Multiple integration methods OFBiz business services can be exposed as services and accessed by multiple methods including Remote Method Invocation (RMI) and XML Web Services. Integration directly with the OFBiz Relational Database is also possible. |
| 5. | Scalability | A | Highly Scalable Java systems are highly scalable provided a production architecture that is designed to support heavy load. A load balancing device and redundancy at the web, application and database servers can redundancy and scalability. |
| 6. | Relational database integration | A | Support for all major database platforms The most popular OFBiz database platforms are PostgreSQL and MySQL (both of which are open source). OFBiz has also been tested with Oracle, DB2, Sybase, and MS SQL Server. The default installation uses an Apache Derby database which is not recommended for production use. Our research indicates some problems with MS SQL Server database – this should be investigated further prior to selecting that database platform. |
| 7. | Skill Set to support | NA | OFBiz framework and application are based in the following technology components:
Long term support of the application would require knowledge and familiarity in each of these technology sets. While these technologies are mainstream and skills should be readily available in the future, skills and experience with the OFBiz framework that is built upon these technologies may not be. |
Business Position
| # | Criteria | Rating | Comments |
| 1. | Financial stability | B | OFBiz is a “top level” project in the Apache Software Foundation. The Apache Software Foundation provides support for the Apache community of open-source software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. |
| 2. | Maturity of product suite | B | Open For Business (OFBiz) was initially launched in 2001. In early 2006, the project went through the Apache Foundation’s “Incubation” process to review projects for quality and open source commitment. OFBiz was promoted to a top level Apache project in December 2006.The community for OFBiz is very active. The major web posting board receives between 20-40 postings per day relating to OFBiz. The original contributors are very active in monitoring these sites and sharing knowledge. |
| 3. | Reference Accounts | B- | Total number of installations is unknown due to the nature of open source software. The OFBiz websites lists more than 70 companies that use their software. However, there are very few marquee names. |
Implementing an enterprise e-commerce solution can be expensive and complex process that requires analysis and investment in people, processes, and technology. While it would be insincere to say that an enterprise e-commerce solution can be implemented on a budget in the ballpark of a mom and pop e-commerce store, the budget can be significantly reduced by:
- Carefully crafting business requirements
- Adapting the business model to match industry’s best practices
- Reducing and carefully planning data migration and application integration
- Keeping the customizations to a minimum
- And using an open source e-commerce platform
OFBiz provides a viable open source e-commerce stack that can be used to implement enterprise grade e-commerce. When combined with good implementation practices and solid execution the combination can result in slashing costs by twenty to forty percent — which sometimes can make the difference between getting funded or getting shelved.

Many companies that sell products or services internationally are finding themselves in a familiar dilemma, should their web presence be global or local?
While a global site is easy to control and maintain and can ensure consistency in branding and content quality, it can not address local culture, interests and variation.
I’ve come across an interesting view on the site of the Localization Industry Standards Association www.lisa.org
They see Globalization as a process with 2 parts
- Internationalization which is the process for defining applications and sites to work in every market
- Localization which is the adaptation of the International framework to local needs and
And the process as:

I agree that the best approach in most cases is to plan for the site and application to work anywhere and then build in enough flexibility for local control and adjustments.
The challenge in this approach is that defining international requirements and anticipating all local variations is very expensive and time consuming. So what should a company that is expanding internationally do? Here are a few questions and guidelines to consider:
- Scope of localization: how are you products or services different around the world? Is it exactly the same product (jewelry tableware for example) or does a local audience may have preferences that will impact selection and availability of products (fashion and cosmetics). If the products need to meet local regulations, standards or laws (220V or 110V for consumer electronics, Material Safety or FDA approvals for Chemicals and Drugs) or if products include attributes like language that will make them market specific (Books and CD’s). In each case, a single catalog for all products will provide the easiest way to maintain master product data but sites level of granularity may be determined by the variance in offering. It may be truly global, regional, country or language specific.
- Centralized or Distributed management. Who will maintain content, details, specs etc. in local languages? Do you assume that a product is not released until all languages have been updated? Do you allow a default language to remain until a local language become available? Is this the responsibility of a central translation group of does it goes downstream to the local group to translate? (If you are thinking about machine translation, don’t. This technology is still not ready for prime time and will drive off disappointed customers)
- How local should you go? to create a true sense of local site and service, certain adjustments may be needed to the site so it does not look like the translated version of the global template. Does the site has local news and events? Is there editorial content from local sources? Are reviews and communities local? Does the interface adapt to local language without cutting words or providing headers in English? Are local conventions like time format, date format, calendar, currency, address, name formats etc. are specific or generic?
-
Build from scratch or retrofit? While substantial amounts have been invested in current web and e-commerce infrastructure, allowing for globalization and localization is not an easy retrofit and in many cases it will be faster and cheaper in the long term to build a technology foundation that is designed to support these issues. Technology issues to consider:
- Separation of content from the display. There should be no text or images in pages and no parameters in queries. Many CMS systems support localization and handle pages this way by default but custom build CMS systems rarely do.
- Support for UTF-8: databases and management tools as well as search engines must support UTF-8
- Caching and Performance: a system must be designed with advanced caching to avoid extensive load on the database for rendering local editions
- Support for variable length and right to left interfaces. Different languages have very different word length and even orientation. How will interfaces that were designed for exact size look?
While these are not simple questions to answer and resolve, creating a global experience with local flavors and details can substantially impact the ability of a company to succeed internationally.













