Some of the earliest posts on this blog were about how powerful location aware services could be.  I spoke about Mobile Mashups and SOA, as well as Location Based Services (LBS) and AGPS and finally the value of Location (and how I thought it was relevant, but not quite sure what to do with it).  You’ll notice this is “so long ago” in Internet History (last year) that I refer to Touchstone, now called Particls.

So it’s with great interest that I can see some of the things I was blogging and thinking about beginning to become a reality.  I was a user of Plazes for a while, but ultimately gave it up because to some extent I just didn’t get it and I think having seen BrightKite now, it was missing the fine-grained access I needed to feel comfortable at that time (it may have it now I haven’t re-checked).

BrightKite is a very compelling and interesting service, provides reasonable privacy settings, but also links in to Twitter by default to set either your location or tweet it.  I’m going to see how it evolves, but I can see BrightKite becoming part of my tweeting in the future (especially when I get a new phone in the next couple of months).  It will potentially be my photo-log of where and what I’m doing, auto-feeding this in to Twitter as appropriate, while I’ll use Twitter directly through it’s various other clients for my 140 character tweets on the world and the community.

Another interesting feature of BrightKite is FireEagle. FireEagle sounds like it’s the DataPortability answer to Location Based Services, an open exchange for location information and the fact that a player like Yahoo is making a move in this space suggests we are at the cusp of big things to come.

Dopplr also adds to the picture of location based services, although in this case Dopplr fulfills a “Where am I going” rather than a “Where am I” feature.

I speculated early on, that LBS would potentially be of use for the Enterprise, but I couldn’t quite touch on the use.  The big area I could see is staying in touch with the people who are part of your Enterprise as they move around, with BrightKite and it’s GEORSS feeds, Dopplr and it’s “where am I going to be” and services like FireEagle, I can see that in the next 6 - 12 months, this will start to become a reality.

To paraphrase myself from over twelve months ago:

As Architects, understanding how location works and what location information is needed to tie the system together will be critical steps that can be taken now to ensure early mover advantage when it finally becomes a reality.

I’ve had my Nokia 6233 phone for about 6 months now.  Recently I’ve been wanting to buy an iPOD, but couldn’t really justify the extra gadget just for heading to work and back.  Anyway, in conversation with someone at work, they mentioned they’d been using their Nokia phone as a music player. 

I should point out that we all have the same model of phone here, they get upgraded with our laptops every two year, so there is some excuse (it’s not like I reviewed the feature set it just landed on me), but it struck me that after 6 months there was a whole set of features in the phone I’d never explored, even when the phone could address a need I had.

Sitting down with another person with the same phone today, I was telling them how excited I was about this (I bought a 2Gb micro SD card and now have some 20 cds worth of music or more loaded up).  Sure it’s not quite the iPOD experience, but it’s a big step up from where I was at.  They didn’t know how to do it, and pulled out their phone only to find they’d configured theirs using yet another set of options I didn’t know about.

It got me thinking about how yet again, tools and software are so feature rich that it’s just difficult for one person to know how to use all aspects of it.  I once heard a quote something along the lines that each person only uses 10% of the features available to them in Microsoft Word or Excel.  The problem is that everyone uses a different 10%.

What this leads to is tools which do many things — they are feature rich, but they don’t do all of them well — leading to them being both feature rich and poor at the same time.  I call them the Rich - Poor.

The Nokia is a perfect example of this — I really love having my music on the go with me, but for listening to music, an iPOD, with its navigation features built into the device is vastly superior.  With the Nokia, I get 150 tracks in sequential or random order.  I can build play lists, but I have to do them manually on my PC first and can’t just choose to listen to “jazz” or a specific album on the go.

Another story I was reminded about was the Firefly.  This is a great example of a Poor - Rich product.  What’s fascinating about this is that the product designed for 8 - 12 year olds became popular with senior citizens in the US, because of it’s limited (and therefore easy to understand and access) feature set.  Catching on to this trend the Jitterbug quickly followed.  A simple set of features, but a depth and richness in the market because it does them well and htis one need in a clear, specific way.

In the software world, we also see this becoming clearer with the move to services and WEB 2.0.   Instead of Rich - Poor applications, we are now getting Poor - Rich services, services that a feature poor in terms of the diversity within the one application, but rich because of the complexity and ability that the service provides.

Of course it’s no suprise this trend has already started, but the next two years is going to be a facsinating time as instead of Rich - Poor apps, we get a true diversity on the Internet with Poor - Rich apps to meet every niche popping up faster and faster as services become more prolific and the tools to plug them together move to new levels of maturity. 

I saw an article in the local free-paper on the train (MX), which spoke briefly about AGPS being launched by carriers in Australia in 2007.  There is some support for this in The Age which also suggests in an article there are plans for AGPS in  2007.  

If you are wondering about what AGPS, or Assisted GPS is, it’s essentially a better GPS service for mobile phones which takes advantage of the base station network to remove some processing power from the phone and provide GPS service even where you cannot get line of sight to the GPS sattelites.  iMobile has a great summary article here as well as coverage of some phones coming out with AGPS capability and more support that AGPS is on its way.

Stepping away from innovation and invention for a moment and back to the “true-purpose” of this blog (if it even has such a thing), I wanted to consider what some of the implications of AGPS might be in an office based business, if any.

It’s obvious that companies with traditional GPS based applications, like transport or logistics companies could benefit from AGPS, and from a consumer perspective, I think it may well be the next “killer app” on the mobile for any number of reasons, but what about corporate office users?

 No doubt, AGPS phones will eventually become the corporate norm, in the same way that despite limited business use and initial opposition, camera phones are more or less the standard corporate hand piece these days even when there are limited business applications for your average office worker.  This is a very legitimate strategy, even if only as a value add to your staff who will find “normal” uses for these things as the phone crosses equally between the boundary of personal and business use.

So what are some of the uses of AGPS technologies for different business sectors?  I’m going to ignore privacy concerns at the moment as undoubtably these would need to be resolved, or may in fact be prohibited.  Additionally I’m looking for applications where a “mobile” location is key — static information like “where is my store / customer” on a map can already be achieved.

1. Manufacturing: Potentially a use in occupational health and safety situations.  Personal GPS devices could identify where staff are located and act as an additional safety check to traditional tagging mechanisms.  While interesting, I doubt there is much in here to drive this use and phone have other distractions and use issues which should see them kept off the shop floor.
2. Retail: For retailers, there may be some usage in tracking store locations, shipments and other logistics type operations.  The biggest growth area here will be in sophisticated customer loyalty programs tied to stock control systems that can work magic like “a known customer is within 200 metres of my store, they have purchased x in the past, this top will match well and I’m over-stocked here — send them an SMS voucher to be redeemed in next 60 minutes”.  This is an area that I believe savvy retailers will look at very seriously.
3. Sales / Relationship businesses: I could envision a version of LinkedIn on steroids but I’m not sure how practical this would be — I don’t particular want my sales rep to know I’m walking down the street!  However, from a sales persons perspective, something linked to the CRM system that can alert them when they are within a set distance of customers, according to parameters, may be of use.
4. General Office use:  No killer apps that I can think off, but some location services may be of use.

Some of  the general location services that I think all types of users could use might include things like — who from my company is in this location?  Now this may seem a strange idea, but as someone who travels a fair bit back and forward to Sydney, it’s a reasonable bet that there is at least one other (and possibly many more) from my work in the queue for a cab at the airport.  If I could easily locate them, we could share a cab, reduce some green-house gas, save some money and more importantly network.

Similarly, I’m often in a hotel where I know there are other people staying — it might be nice to share dinner or something similar.

Touchstone has got me thinking a lot about attention based services as well, and I think that there is some merit in considering location as part of an attention profile.  This might mean that when I’m travelling for example, I get some local news.  If I could locate you to a floor in a building then I could SMS you as you enter the floor about things that need your attention now.  In effect an event trigger system, better known as Location Based Services (LBS).

LBS uses could be very wide ranging, from letting people know I’m at my PC (because I’m in my office), on my mobile, or just triggering a notification at a time I can do something about it, LBS offers opportunities for managing attention that broadcasting information may not.

From an architectural point of view, the best place to start would be with JSR179 which is implemented by both Nokia and Blackberry as well as a host of others.  This lengthy standard gives a great deal of information about what a LBS is capable of providing to a phone based application.

In researching this, I found an excellent summary here which talks about several different types of location services:

1) Location blind services – users manually enter their location.
2) Location aware services – location determined automatically.
3) Location precise services – accurate location, and a proactive system.
Geoff Hendrey. Managing the wireless internet. RF Design, March 2001.

We are now entering the first generation of level 3, with AGPS enabling accurate location.  I’m still searching for information on how the pro-active nature will work — while a system based of a JSR179  application on your phone might work, it’s not pro-active enough for real event based LBS which need to work without an application required to be useful.  Once I find some more I’ll post it here.

In summary, AGPS is coming, it’s not here yet, but there for some businesses it will bring significant advantage if implemented well.  For others, namely office based businesses, it may provide some interesting niche applications, but no real business drivers yet.  This isn’t to say something won’t happen, I believe in the war for talent that business is increasingly driven by the expectations of it’s staff, not just ROI in the traditional sense.

As Architects, particularly in retail businesses understanding how AGPS works, what location information is needed to tie the system together (is it just a mobile number) will be critical steps that can be taken now to ensure early mover advantage when it is launched for consumers later this year.

I found this Wall Street Journal video here at The Lost Remote.  One of the things I’ve been working on at the moment is a retail sector publication on trends and issues for 2007.  This video sums up succinctly the message I’ve been trying (like many others) to get across - the world of communication (as in Internet and Mobile Phones) is fundamentally changing.

Apart from being an entertaining little video, it issues some real challenges which is to get our heads around some of these types of features.  Particularly for retail (ie consumer focussed sectors) understanding where the internet and mobile technology is going will be key to early mover advantage and future success.  Taking advantage of the application driven nature of the Web 2.0 and plugging services together with proprietary systems is the compelling challenge for companies today — even if they don’t realise it!

From an Enterprise Architecture point of view, an SOA view of the world is becoming even more critical.  It’s all a service, wether it’s an internal or external application, the boundaries are changing.  With a strong services focus internally, then mashups between internal and external apps become compelling value adds for consumers and the companies that serve them.

Here’s a simple example, using Plazes, another interesting startup I’ve come across recently.    There’s a similar service shown in the video.

Plazes is at first glance locating you on a map. Kind of neat, but when you explore it under the hood a bit you realise it’s also a locater service for friends and others in your area.  For a retailer, the scenario could play out like this.  Set up Plazes, place your retail outlets, let your customers hook up as friends then use the Plazers service to let you know when your friends (ie. customers) are near your location.  This kind of location mashup could be put together quickly with a prior investment in SOA internally, enabling you to then link the friends to your backend systems, work out what they’ve purchased recently then contact them to tell them that there is a special offer available now if they come into the store.

What the Web 2.0 evolution is doing is removing the requirement for us to wait for big vendors or vertical applications.  Enterprises should be acting now to ensure that they are ready to grab the best of the web and put it together in innovative ways for their customers. 

That means sound SOA strategy so that agile developers can pull together the systems they need to create compelling applications.