Lotus and fuels for the future

exige270e

Being a fan of all things Lotus, I’ve been following news about their tri-fuel Exige 270E technology demo with some interest.  It’s essentially a standard Exige that has been modified to run on either Petrol, Ethanol or Methanol – or any combination of the three.  Sensors tell the ECU what fuel is being used and it then adjusts the engines combustion appropriately. 

Although there has been a lot of focus on hydrogen as a fuel for the future, Lotus is arguing that due to the inherent problems and costs involved with hydrogen, synthetic methanol may be a better choice. From my layman’s perspective Lotus arguments seem pretty sensible.

Simply storing hydrogen is difficult, you can either compress it to 700psi, or liquefy it at -230 degrees centigrade, neither of which are best suited for transport in vehicles.  It’s also not very energy dense, I understand it’s something like a fifth the density of petrol, and once you add in the energy spent creating and storing if the well-to-wheel efficiency drops even further.

One of the biggest problems though is that hydrogen will mean a complete change in engine design and use, a hard change that will cost manufactures and support services like petrol stations huge amounts to implement.

Methanol, whilst not a panacea, does offer some advantages.  It’s a liquid at room temperature for a start.  It’s also more energy dense than hydrogen, though not as dense as petrol.  It does however have a higher octane rating – something that allow the 270E to produce more power than the regular petrol based version.

In my view though the biggest advantage has to be that a move over to methanol can be gradual.  The chaps from Lotus reckon most modern engines should be able to run methanol with very few changes.  The main physical obstacles seem to be around the fact that methanol is more corrosive so seals, pipes, tanks etc need to be changed.

That being the case, a change over to methanol would be much simpler for manufacturers.  Potentially they can future proof their cars against future ethanol or methanol fuels now, or at least within a few years.

If new cars were able to use these fuels in various mixes, fuel producers would be able to add synthetic methanol into their fuels and phase out petrol over a period of time.

Of course, methanol still produces CO2, but as it can be synthetically produced from carbon dioxide and hydrogen the potential exists to recover these from the atmosphere or existing industrial waste collection.  The idea being that CO2 emissions at the exhaust will be balanced to a neutral point.

It seems like an interesting technology challenge, and I’m glad to see Lotus taking a lead in it.  What I’d love to see though is Lotus taking a lead in delivering tri-fuel cars to customers.  It would seem like most of the development for their current Elise and Exige range has been done for this project.  If the costs per car weren’t too great it would be a hell of a marketing tool, and would certainly set them apart from their competitors.  Would the other manufacturers follow?  Who knows, but it’s a Toyota unit that Lotus have been working with, so it would be easy for at least one major company to follow.

Windows 7 and Virtualisation

Yesterday I left a comment on a post over on istartedsomthing.  The post was about a job advert for developers to work on virtual hard disks, and it’s implications for Windows 7 functionality.

There seems to be quite a bit of focus on this line from the advert:

"Consider the simplicity of backup using a VHD, or the portability of a virtual disk backed by a single file."

Whilst that’s all very nice, for me the real interesting quote is this:

"Imagine being able to mount a VHD on any Windows machine, do some offline servicing and then boot from that same VHD. Or perhaps, taking an existing VHD you currently use within Virtual Server and boost performance by booting natively from it."

Specifically the last bit. 

If the intention is to include the ability to boot from a VHD, this implies that the platform will be built around, or at least support, a hypervisor like Hyper-V.

Of course this may be a focus for a future server version of Windows 7, but if included in the desktop as well it could make virtual desktops (VDI) and blade workstations a much more appealing prospect for the future. 

Imagine running an office full of desktop machines.  The low end requirements could be met using VM’s hosted on large servers, say 20-30 per server, presented to the user by a thin client.  If a user has a more complex requirement, you could simply move that VM to a dedicated blade workstation.  Hopefully that would use the same thin client and be pretty transparent to the end user – perhaps even VMotion style transparent.  If the user then needs to move office or go mobile just copy their VM to a remote server/blade, or to a standard desktop or laptop. 

It would need some good management tools but it could be quite a nice solution.

What might Mesh mean for Office and businesses?

I’ve been playing about with the Mesh preview for a week or so now and overall I’m pretty impressed.  Unfortunately I’ve not had time to look at the dev side of things (or it could be that I couldn’t code my way out of a paper bag…) but its clear from talking to developer buddies that they’re equally interested. 

Anyway, I was chatting about Mesh earlier and the subject of Office and other ‘business’ apps came up.  Or more specifically what, if anything, Mesh would mean to them.

I guess the most obvious place that Mesh could integrated is Groove.  It’s one of Ray Ozzies former projects and has more than a little in common with Mesh – or at least the functionality provided in the preview. 

The most common use  of Groove is peer to peer, you’d create a workspace or share a folder with a number of people, but there’d be no central point where the data was kept waiting for other people to come online when you were away. 

There is however the option to use Groove Enterprise Services to provide the equivalent of the cloud Mesh, a centralised service that clients could sync with which would then be available to pass on changes to other users as they came online.  Using Mesh as the sync provider for new iterations of Groove would seem to make sense.  The question to my mind is quite how that might work. 

One option would be to allow clients to sync directly with the Mesh cloud.  Although that would be the obvious and easiest solution it may not always suit enterprises.  Clients would all be syncing directly to the Internet over the corporate network, not ideal unless you have huge bandwidth.  Some companies may also be unhappy about having a copy of all their synced data sat outside of their network.

One way to provide enterprises with some additional flexibility might be to provide some form of internal Mesh – an internal Mesh cloud that clients can sync with privately.  Potentially this cloud could then sync with the main Mesh cloud in a controlled way to allow a company to better manage the bandwidth over it’s Internet connection.

How would such a Mesh cloud be delivered?  Maybe as part of Exchange or SharePoint?

One of the examples Ori Amiga gave in his Channel 9 video showed how updates made to data in an application could be synced in near real-time to other Mesh clients.  In his example he used a family tree application, but for some reason it reminded me of the Excel Calculation services in SharePoint 2007. 

ECS allows you to maintain a central version of an Excel worksheet and show updates in real-time via a SharePoint webpart (that’s a huge simplification I know).  Presumably if Excel was able to use Mesh, changes to shared workbooks could be synced with other users of that workbook.  How useful that might be I’m not sure – I’m not a huge Excel user – but the same could apply to PowerPoint or Word.

The other day I read a blog post about using Mesh as a messaging platform, unfortunately I can’t find it now to reference it.  The gist of the post was that Mesh and Feedsync provide the basis for simple IM and email tools. 

Thinking it through a bit more though surely Mesh would make a great platform for an enterprise Twitter style messaging platform?  This could be a component for Outlook or Communicator that connects directly to Live Mesh or possibly connect the notional local cloud I mentioned up above. 

Of course this all just speculation, but given the obvious investment MS has made in Mesh it would seem sensible to use the framework in some of its other products.