VenChar

Solar-powered wireless-enabled parking stations

Daily Wireless writes about wireless parking stations being rolled out in Montreal to replace traditional parking meters. You would pull in to a parking spot, walk over to the parking station, enter the parking spot identification code and pay with cash or credit. Meter maids would be able to query the parking station using a wireless handheld and determine which (if any) of the spots are illegally parked.

Benefits to the city:
* fewer parking stations required (each parking station replaces 12 parking meters)
* more convenient for the meter maids - they don't even have to get out of their vehicles to check the meters
* stations are solar-powered, so no access to regular power is required
* parking rates can actually be altered from a central location, allowing the city to charge a higher rate during sporting events, concerts, etc.

The parking stations are being developed by 8D Technologies in partnership with Cale Systems. The system runs Linux and uses GPRS for connectivity. Daily Wireless makes the point that when you tally up the access fees for GPRS, this begins to look like a pretty expensive solution. Yet another good application for ubiquitous WiFi coverage.

Access to source code

In the years to come, people will identify ways in which the software business changed fundamentally post-Linux. One of the ways it will be seen to have changed is that (non-end-user) buyers will increasingly demand access to source code for modules/components of the product that are purchased from other vendors. One example would be requiring embedded OS vendors to release or at least share their source code.

Anecdotal example: one company I know was considering migrating from an open source-based module that had been under internal development to an externally-supplied substitute. The main reason they rejected the substitute was that it wasn’t open source (or even shared source). What happened was that they started out with an open source version. Over time, they invested effort and resources in improving it to the point where they had it doing what they wanted it to do (in the process improving the set of core competencies that they had in-house). At some point, when the requirements evolved, they were faced with a make-vs-buy decision between staffing to add the new functionality versus buying a third-party software product. The one third-party product that met nearly all the feature requirements was a closed-source, binary-only, application. Having had experience with the open-source version and having had to debug the issues that arose with it, they felt that they really needed to have to have access to the source code for any module they would purchase from a 3rd party – if you have certain competencies in-house, it is much more efficient to identify and remove the software defect yourself than to have to wait for your supplier to fix the problem.

This is just one example. Having access to source code is very powerful:
* greater transparency
* better ability to debug and troubleshoot issues
* ability to make application-specific tweaks to the software module (as an example, a router vendor might value the ability to tweak the OS to improve packet forwarding performance)
* ability to make continual improvements in terms of features and functionality.

While end-user buyers of software are unlikely to care as much about the availability of source code (how many people are really going to want to tinker with their desktop OS or their spreadsheet tool? A vanishingly small fraction), I can see a good justification for systems vendors desiring or even requiring source code from their software suppliers. I would guess that this is the direction in which the embedded software space is going to evolve, which is one reason why WindRiver’s old model (proprietary, closed-source OS) is becoming obsolete and why their recent statements re: Linux are signs of a good move.

Linux in embedded devices

I've been noticing Linux's takeoff in the embedded software space for a while now. Key drivers:
(1) Linux is free
(2) it's good enough (hard real-time capabilities are inessential for many applications, given improvements in processing speeds)
(3) it's open source, which means
(a) adopters of embedded Linux have the freedom/ability to make performance tweaks, etc.
(b) problems/issues are easier to debug and fix
(c) open source developer community is an asset in resolving issues
(4) high level of features and functionality, esp. with regard to the networking stack, for instance.
These were some of the reasons we went with Linux as the embedded OS in our product at my company. Anecdotal evidence, from speaking to other vendors, has confirmed that many are thinking about migrating their products to an embedded Linux base.

Looks like WindRiver (maker of VxWorks) has seen the tide turning and is making a strategic bet on Linux.

Wind River is by far the world's largest embedded software company, and the company does about 30 percent of its business in the telecom and networking markets.

"We have been very aggressive in speaking out against Linux in the past -- in a mode of fighting Linux, saying Linux was bad," says Genard. "That was the wrong fight. We now realize that Linux has a lot of benefit, and has a lot of traction, and can benefit customers. This announcement is about our commitment in recognizing that Linux and VxWorks are both relevant [in the telecom and networking infrastructure markets]," he adds. "Linux is making headway, and we are committed to see how we will support Carrier Grade Linux customers."

Novell to buy SUSE

This just in. Novell is acquiring SUSE Linux in a $210MM deal. This follows on the heels of their recent acquisition of Ximian (Linux desktop solution). More on this later.

Linux desktop migration challenges

Via Slashdot, an interesting study by Paul Murphy at Ace's Hardware on the costs of migrating from Windows to Linux. Murphy discusses the architectural issues around the adoption of Linux on the desktop and the challenges it will pose for IT staff trained at and accustomed to administering Wintel systems.

What does the arrival of Lintel mean in terms of the organisation's need for the Microsoft gurus who currently support the organisation's Wintel ([Microsoft] Windows on Intel) desktops? How does the typical MCSE skill set map to what will be needed to cope with an environment in which perhaps 20% of the servers and 80% of the desktops run Linux while the remainder continue to run Microsoft suites?"

Telstra switch to Linux

Further to recent remarks about Linux on the desktop, news today that Telstra, Australia's largest technology company, aims to switch 85% of its desktops to Linux + thin clients.

'Telstra chief information officer Jeff Smith said he was determined to end a history of internal duplication and technology incompatibility by deploying open-source software right across the telecoms giant, which spends $1.5 billion each year on information technology. He aims to slice this cost in half within three years. "I would see a big movement from Windows and Unix to Linux," Mr Smith said... On desktop trial are Sun's Star Office on Linux, native Linux applications such as the Gnome graphical user interface, and the Mozilla browser. Telstra is also testing a Wyse thin-client terminal with XP-on-a-chip using Citrix. Mr Smith said the savings could be huge, with a total cost of ownership reduction of about 40 per cent.'

Performance Oversupply and Linux on the desktop

During my two week vacation in India I got to read Clayton Christensen’s ‘The Innovator’s Dilemma’. One of the key concepts I picked up from the book is the idea of performance oversupply: In their efforts to provide better products than their competitors, suppliers often ‘overshoot’ their market: they give customers more than they need or ultimately are willing to pay for. Christensen argues that when performance oversupply occurs, it creates an opportunity for a disruptive technology to emerge and subsequently to invade established markets from below (by offering less functionality at a lower price). He also argues that performance oversupply tends to trigger a change in the basis of competition within a particular market.

Christensen argues that existing technologies or products have a tendency to migrate in a “north-easterly” direction (on the performance vs time graph) and steadily acquire more features and functionality in an effort to cater to the higher value (higher margin) customers. In doing so, they will tend to create performance oversupply scenarios that are ripe for exploitation by cheaper, simpler substitutes that have a reduced functionality set and can profitably cater to the lower end of the market. Complementary (and similar) to this notion of performance oversupply is the idea or principle of "good enough", that has been written about elsewhere recently.

An interesting example, discussed in detail in the book, is Intuit’s introduction of an accounting software package targeted at the SMB segment. Scott Cook, the founder of Intuit, made the following 3 observations about the state of the accounting software market for SMB: (1) previously available small business accounting packages had been created under the close guidance of CPAs and required users to have a basic knowledge of accounting (debits/credits, assets/liabilities, etc.) and double-entry bookkeeping. (2) most existing packages offered a comprehensive and sophisticated array of reports and analyses, an array that grew ever more complicated and specialized with each new release as developers sought to differentiate their product by offering greater functionality. (3) 85% of all companies in the US were too small to employ an accountant. Books were kept by proprietors or family members who had no need for or understanding of most of the entries and reports available from the mainstream accounting software. Cook decided that the makers of accounting software for SMB had overshot the functionality required by that market, thus creating the opportunity for a disruptive software technology that provided adequate, not superior, functionality and was simple and more convenient to use. Intuit’s disruptive Quickbooks changed the basis of product competition from functionality to convenience and captured 70% of the market within 2 years of introduction.

Christensen speculates that if one examined how people use Microsoft Excel, one might find that this is a case of performance oversupply, where the degree of functionality and the number of features provided far exceed what the average user (or even the power user) utilizes. He suggests that an opportunity might exist for a disruptive technology to invade this market from below. I would go further and suggest that there are broad classes of commercial software packages that are bloated, have way more features and functionality than the average user cares about or uses and that there exist open source alternatives that would qualify as “good enough” for large classes of users. One example that is beginning to get talked about is Linux-on-the-desktop as a good-enough substitute for Windows.

Now, performance oversupply can only be diagnosed relative to a specific class of users or market segment: what might be overkill from the perspective of one class of users might be minimal functional requirements from the point of view of another group of users or market segment. Which begs the question, what are the classes of users for whom the Linux desktop is already a good-enough substitute? This is one of the questions addressed by the excellent report Desktop Linux Technology and Market Overview that I read recently.

The report examines the state of the Linux desktop in terms off maturity, existence of core applications, developer support, etc.. In particular, it identifies a few classes of users for whom the Linux desktop is already a compelling alternative to Windows: (1) transactional workers, (2) small- and medium-sized businesses, and (3) public sector organizations internationally. For instance, the requirements for transactional workers (customer support staff, call center employees, bank tellers, sales reps, admin staff) are very different from those for knowledge workers in that (1) they spend most of their time using just a few apps, (2) they don't need the ability to run arbitrary third-party apps on their desktop, (3) costs savings (from using Linux as well as from other open source apps) are important. The primary weaknesses of Linux as a desktop environment namely: (1) broad application support, (2) ability to natively run office productivity apps like Office, etc. are not as important for this class of users and Linux, possibly in conjunction with thin clients such as Citrix, would be a good fit for this segment.

Christensen also argues that performance oversupply tends to trigger a change in the basis of competition - once the market’s demands along one axis of performance have been sated, other product attributes, whose performance have not yet satisfied market demand, come to be more highly valued and to constitute the dimensions along which vendors differentiate their products. As noted above, the disruptive introduction of Quickbooks into the SMB segment changed the basis of product competition from functionality to convenience. How is the Linux desktop going to redefine the desktop playing field? What are the new product attributes or measures of performance that will constitute the bases of product competition?

One tentative answer is "openness of source and formats". For instance, the Oregon bill that would require the state government to consider using open source software when doing procurements states: "It is necessary to the functioning of the state that computer data owned by the state be permanently available to the state throughout its useful life. To guarantee the succession and permanence of public data, it is necessary that the state's accessibility to that data be independent of the goodwill of the state's computer systems suppliers and the monopoly conditions imposed by these suppliers" (this is an interesting point that is also made in passing in the Desktop Linux Overview and it seems to refer to the perpetuity licenses of open source software as well as to open, standards-based formats for data storage that break the dependence on software from a single vendor)

Interview with Jim Ready of MontaVista Linux

Jim Ready of MontaVista Linux offers an interesting set of perspectives on embedded systems and the drivers for Linux adoption in that segment.

Ready makes the point that one of the distinguishing characteristics of the embedded market is the diversity of underlying microprocessor architectures - PowerPC, MIPS, ARM, etc. - compared to the desktop where the Intel architecture dominates. On the surface this presents a challenge to a vendor like MontaVista in terms of developing versions of the OS for each of these architectures. However, he argues that Linux is flexible enough to be easily adapted to all these environments.

An interesting observation, that resonates with some of my recent thinking, is that there is a trend towards highly networked devices that signals a move away from the traditional RTOSes that did one or two things really efficiently towards a more general purpose, powerful OS like Linux with a lot of networking capability built in. For instance, Nikon recently announced a digital camera with WiFi enabled. What this implies is that the device now needs to have (minimally) a WiFi driver and a TCP/IP stack - enter Linux. Quote: "A combination of factors has moved the center of gravity and design techniques toward a more sophisticated, more modern OS, such as Linux, and away from the traditional, dedicated RTOS-style architecture. It’s just that the average design is now more complex and has a higher networking requirement. That’s what’s shaping the market...It’s not that realtime requirements have completely gone away but that, in general, the trend is toward more high performance in silicon and softer realtime requirements for the application and embedded OS."

Sony, Matsushita and others recently announced the creation of the Consumer Electronics Linux Forum aimed at driving the advancement of Linux as an open source platform for embedded devices.