While at Adobe MAX this year, I had the chance to quiz a few people on what exactly “Enterprise RIA” is and, valuably, talk through how projects are done and then see a couple demos of such Enterprise RIAs in action.

What’s the point of Enterprise RIA? Ben Watson tells us

The discussion starts with Adobe’s Ben Watson who explains what this enterprise RIA concept is and why it matters to companies. The idea of having a compelling, engaging piece of software is normally cliché, but Ben does a good job of explaining why you want that, what the benefits are and how that kind of experience can help organizations:

You can also just download the video if you prefer that.

Mobile Kiosk

Next up, we talk with Universal Mind’s Chris Rogers who talks to us about the process and tactics of doing an enterprise RIA project. I tend to think that “has a good user experience” is a different requirement to push through a project, so I wanted to hear how Universal Mind manages to do it. Chris gives a good, quick overview based on their word in the field:

Overview:

After this project and process talk, Chris shows us an enterprise RIA prototype they’ve built that around cellphone users interacting with their account across different form factors, including a kiosk that we see on the show floor:

If you’d prefer to download the videos, the overview and demo are just a right click away.

Beyond the clip-board with medical records

There’s few enterprise-y scenarios more fraught with pit-falls than converting the medical industry over to paperless, getting rid off all those paper and pen forms doctors, nurses, and hospital staff seem to have a tragic romance with. Thanks to the sheer beauty of new form factors, like the iPad, the folks at Ensemble have been finding success using enterprise RIA as the way to digitize medical records.

First, Ensemble’s Vlad Ghelesel gives us an overview of the project and how enterprise RIA is being applied:

After this overview, Vlad shows us a demo of the product in action on, of course, an iPad:

You can download the overview and demo if you’d prefer that over the embeds above.

In addition to the videos above, you can subscribe to the RedMonk Media feed, for example, in iTunes, to have them automatically downloaded.

Transcript – Ben Watson on Enterprise RIA

Michael Coté: All right, well, here we are at Adobe MAX 2010. I mean we’ve seen a lot of consumer-based technologies and RIA use and things like Google TV and AIR on phones and things like that, but in the context of business users, like what is this, what is sort of this Enterprise RIA or Business RIA stuff?

Ben Watson: Enterprise RIA is a marketing term. It’s a group of technologies, a set of methodologies, a set of best practices, there are some patterns that we bring from SOA, from experienced design, from user experience. We are bringing them to bear in an application. So if I think about it from an enterprise perspective, it’s connected to the backend systems. It’s got audit and control mechanisms in place that are going to please IT, it’s going to make sure that that application gets delayed, and doesn’t just get ripped out kind of later on.

The bottom line is RIA is a term; it’s a yet another kind of technology acronym. It’s error backwards. I think it’s kind of about as passé as color TV and we’re going to have these applications at the edge; maybe we can call them edgeware or whatever we’re going to call it that ultimately integrate, talk to, manipulate data from, collect information and collect user interactions in a meaningful way and apply them against those underlying systems. I really mean everywhere because I see it yes, I see it in the consumer space, I see it on TVs, I see it running on hundreds of different kinds of devices, but I see that as B2B, as B2C, as within supply chain as a way of a doctor understanding a patient history, a way for a loss adjuster in the insurance market to understand and interact with a situation that’s taking place in the field.

We are replacing metaphors from our everyday life. We are replacing human interaction with a much more intuitive way than previous applications partners. We don’t go though our life in a page based metaphor, kind of clicking on next, next, next or navigating using a drop-down in order to organize our thoughts. That’s counterintuitive. But if you design something based on my goals, based on my motivations, if you use persuasion, some game theory, give me some beautiful, emotional, kind of graphics that are going to make me feel engaged and make me feel like I am part of something then that’s a rich experience. And this is really just about an experience at the end of the day. My experience happens to be with a business or with an enterprise and that comes with conditions and expectations that I have of that company, I have of that brand and that persistent brand needs to trickle and bleed through the interface in such a way that I feel compelled to keep using it that I feel compelled to share with other people what a great experience it is.

So you know I kind of push that terminology aside and say it’s an opportunity for designers and developers to work together. These two sumo wrestlers, they are used to be facing off against each other on the mat and banging their bellies into each other while seeing who yell the loudest that was kind of a pointless development, kind of waterfall exercise. And instead what we have is this great collaboration that can take place where I can use an agile methodology; I can shift ideas back and forth in the design and development process. I can prototype at high speed and I can take advantage of what I learn from that prototype, inject that back into my applications, use it in different and new and exciting ways, share components of what I’ve learned with my other developer friends, with my other designers.

Let that brand persist through the development and design process across everything that we are doing on top of the enterprise. So I am taking this clunky Siebel, highly complex SAP backend, I am not forcing you to self-select yourself into a database, make a bunch of the columns and rows, and I am not using a page or not clicking through life going next, next, next. You are going through completing a goal. You are going through following through in what you are motivated to do and you just happen to be doing it in the context of an application.

Michael Coté: Can you sort of explain in this context, what engagement or engaging user experience looks like in a business context?

Ben Watson: I think maybe it’s as base as the laws of attraction, it’s as common as feeling compelled to sit down in front of a piece of art and study for a few minutes. When you hear a piece of music for the first time and a shiver runs up the back of your spine, there’s some magic that happens in design and we persist that through the interface in such a way that people feel that compelling need to interact with it. I am sure I’m captured on your motivation, I didn’t happen to hear music because just out of the blue, I like music, I went and found music, I just happened to find a piece that I became really interested in. In this case, I needed to do something, I needed to get something done and a designer who understood that, understood my motivation, who spent time understanding what it was that I wanted took some additional time, some extra time to build in my motivation, to build in my need to that and I recognize that and that’s what’s engaging me.

I recognize my own needs being met, I recognize maybe in some cases intuitively that this is for me and it’s something I really want to do and in other cases, maybe really logically because I understand — I have a process in mind maybe, I want to go through and fill out my tax return, I want to purchase a complex service from an insurance company or a bank. I am not really thinking about bank and I am not thinking about brand and I am not thinking about application. I am thinking about driving my new car properly insured, I am thinking about making sure my family is safe and then my property is safe. I am thinking about how much that’s going to cost me maybe at the end of the day and how to factor that into my budget and maybe I have got some kind of thoughts or competitive quotes or all of those kind of things.

These little things that happen in my life that are motivating me to do that, are opportunities for design to recognize my situation, my own personal experience and kind of bleed that, persist that through the interface in such a way and that’s going to make me feel better about what I am doing. I am more likely to share that experience and less likely to have buyer remorse at the end of the cycle because I felt good through that, somebody was actually holding my hand but they were doing it in this invisible kind of untethered way and I felt okay about that.

Michael Coté: So in sort of like the Adobe ecosystem, I mean Adobe obviously sells the software that builds these kinds of experiences. Can you give us a sense for the kind of like ecosystem of other people out there who are building these kinds of applications?

Ben Watson: Sure! I think that’s a critically important factor. I would say the most important thing for Adobe to succeed in our new mission around customer experience management is to embrace our partner ecosystem to understand the new skill set, to put our arms around business analyst and usability analyst in a way that we haven’t in the past, to make sure that we can act as a catalyst to move a discussion back and forth between a business need and an IT need, to help each other understand what’s going to change, what’s culturally going to have to change, what’s going to change from a delivery point of view, where am I going to feel uncomfortable in this process, what’s going to make me feel, this isn’t how I’ve done things in the past. There is a new opportunity for user experience professionals.

I think it’s their time in the sun. I see the growth in the community, I see the growth of online dialog, I see the growth of the terms in social channels like Twitter, etcetera. The conversation around user experience is increasing and it’s an opportunity for us to not only continue to provide great tools from server platforms, things that help you get your job done, things that push products to market faster, things that ensure that services are secure and built in an enterprise way, but maybe even more importantly to have the right conversations with the right professionals and put them together with our customers, so that they can form the meaningful relationship that’s going to be required to get the stuff built.

Transcript – Chris Rogers on introducing the process of Enterprise RIA

Michael Coté: Well, here we are at MAX 2010 to hear about some people who’ve been doing Enterprise RIA and engagement and exciting stuff in the business world that doesn’t involve just streaming videos. Why don’t you introduce yourself real quick?

Chris Rogers: I’ll do that. I am Chris Rogers. I work with Universal Mind. I our VP of consulting which means I manage our core business, which is working with customers primarily in the enterprise and in the innovation space around RIA.

Michael Coté: We were talking with Adobe’s Ben Watson about what it means to sort of be in Enterprise RIA or to fit kind of the Adobe experience into a business context and what’s interesting about you guys is you actually go out and do the hard work of doing that with the tools that they provide and others. What’s interesting in that aspect is that people seem a lot of software projects are kind of dismissive of actually, this is going to sound corny, but studying what the users actually want and how they interact with their software. And how do you sort of convince people that they should take the time to actually figure out how their users are using the software versus just kind of satisfy a list of features that they should put into that, the software.

Chris Rogers: Yeah, so I’ll give you an equally geeky response which is we used to begin our user experience exercises with the discrete research fogures and if customers aren’t sort of convinced that that’s needed, often they are clients I should say, clients feel like they know their customers really well, we faked into more of an iterative design approach. So in short sprints, we go all the way through concepts of user research through prototyping, which is something a customer does understand in the user experience design sort of world. So we sort of snuck it in by making sure that we do it in an iterative fashion and we can go from user research, understating users to wire-framing and prototyping up those experiences so very often customers get to see what’s happening and why that’s important. So it’s a bit of an education process, but as long as they’re getting out of it at the end of these brief sprints, what they are looking for, they seem to get more about in and it becomes more part of the process with that client.

So there is a couple of different ways that this works. In some senses, an Enterprise RIA can refer to something that’s within the four walls of an enterprise and is used for a customer to interact in a business transaction. So there is a finite user group and for us that’s an easier way to interview folks, understand personas and understand their sort of interactions and workflows. Enterprise might also refer to applications that are business focused like something like a banking application, even though the target user is a consumer. That’s sort of an undefinable user group because it could be anyone who banks and that’s sort of all of us.

Michael Coté: And again, a lot of what you getting at is figuring out the touchpoints the user is having with the software, and then really polishing the crap out of those touchpoints.

Chris Rogers: Well, there maybe software and there may not be. There will be software once we are done with them, but in some cases, it might be a process that already exists in another fashion. So it might be interactive in multiple applications or physical things like calculators and calendars that are hanging on their wall. There is one example where we worked with financial services company where we went into a user’s cubical and found posted notes and calculators and calendars hanging around the wall.

We found out that those were just crutches that they were using in addition to the technology that they’d had in-house that they thought was just fine. By integrating a lot of sort of the crutches that they’re using in their day-to-day process into the application, we sort of made a much more relevant and usable application for our customer.

So a great user experience doesn’t have to be flashy and full of animation and sexy choreography; a great user experience means that the process is accomplished in as few steps and as elegantly and obviously as possible in most cases. So where a visual metaphor is more important with something potentially like a mapping application or something where you want to see the where and the when of the information and the data, I think we can go down that path.

But user experience for the sake of sizzle is really not the end game in Enterprise software. I think the Adobe toolset, things like Flex and LiveCycle Data Services, etcetera these are enterprise grade platforms that not only foster that user experience, but the IT professional on the backend understands and is not afraid of and can tie into existing data and services.

Michael Coté: When you sort of deliver this project or these kinds of
projects, what’s kind of — the sort of “leave behind” you do for management or whoever to kind of rate the success of it — like how do know their project is done and know to be happy with it?

Chris Rogers: There are a couple of answers there. One is if a customer is getting into sort of a crowded space and wants to enter that space and differentiate by innovating, then the answer to that is how we build something that takes them one step ahead of where the competitors are. So an example of that is working with, for instance, Kodak Gallery who self-admittedly kind of got behind the Shutterflies, and the Snapfishes of the world.

When we help them to build in innovative features and innovative experience to the new website, they can go off and then measure, are they having greater use of the features that are featured on the website and are they getting better adoption, things like that.

On the other hand, if it’s more of an enterprise focused application where market share and things like that aren’t as important, we sort of leave it to, are the customers using — are users getting more out of the data and using the existing enterprise applications in ways that they probably were afraid of doing before. Admittedly, we don’t do so much of that measurement. There has been a lot of discussion here around Omniture and some of the analytics tools that Adobe offers and it’s probably something we could do. But really, we’re in the business of making sure that we translate what a customer is either the problem that they are trying to fix or strategic objective that they trying to realize and making sure that at the end of the project, we’ve done that.

Michael Coté: Well, thanks for being on.

Chris Rogers: Thank you for having me.

Transcript – Vlad Ghelesel on Enterprise RIA

Michael Coté: Well, here we are at Adobe MAX 2010 and we have been talking about different Enterprise RIAs to use the term loosely or just fun RIA experiences in a business context. We’ve got someone else who is going to walk us through one project that they worked on that definitely fits into that context. Do you want to introduce yourself first?

Vlad Ghelesel: Sure, my name is Vlad Ghelesel, I am with Ensemble Systems and I am the VP of Business Development, and I essentially touch all of the projects that are ongoing on Ensemble and all of the relationships that we have with our partners like Adobe and our customers whoever they might be.

Michael Coté: There is a project in the healthcare sector for a hospital that you were working on and can you kind of lay out what the need was that they had, like what were they trying to accomplish by engaging with you guys?

Vlad Ghelesel: Sure. So, yeah, the need is more than just at the hospital level. So we are working with the National Health System basically in the UK and the need is to make the whole system more efficient and to deliver patient care in a more efficient way whereby access to the assets that belong to a patient as they are making their way in their lifetime through the medical system will live with that person all the way along. So if they see a physician at hospital X and then they go to hospital Y, there is a consistency of the information available to all the different clinicians that are working with that patient to deliver out services.

Michael Coté: It’s sort of like a portable file that’s electronic.

Vlad Ghelesel: It is. It’s more than just the mobile story. It’s the whole system behind having the ability to have all of these what are normally pieces of paper be put into this system that then allows mobile devices or workstations to access this information from a single source.

Michael Coté: I mean it seems like traditionally and currently, it’s very challenging to get, I think, the phrasing is always doctors to stop using paper or whatever. In this case, how did the client and yourselves and other people that you are working with, how did you get over that. We’re actually going to do this and electrify and digitize all this.

Vlad Ghelesel: Yeah, interesting question. So first off, the work is being done is a very strong partnership between ourselves, Cognizant and Adobe consulting in the UK and it’s being rolled out to some specific sites in the UK. But I think we got involved with this particular customer that the first instance is being rolled out at and we just had such great buy-in right from the beginning because they are looking for this wow factor and the way that that came out was particularly in showing them an iPad application. You walk into a room full of hospital executives and you hand them all an iPad and you show them this application and they absolutely fall out of their chairs basically because it just changes the game. It changes the space that they think about because everything is very much paper, everything is file folders and clipboards and writing stuff down and now you are imagining having a tablet based device that you can do digital dictation so you are doing your voice into a device and that’s being transcribed on the device.

You can do video collaboration to talk with a specialist at another hospital while you are seeing a patient in this hospital. You can do stuff like dash-boarding. I mean there are all sorts of things now that as you’re talking to these hospitals is just such a different way of thinking of how to solve the problem that it’s just — it’s led itself into them saying you know what, let’s go for this and we’ll do it.

Michael Coté: It sounds like, and correct me if I am wrong, but the way to appeal to that big change is not through functionality, but really just through engagement or even beautiful applications.

Vlad Ghelesel: So there are a couple of things. We all talk about software, we all talk about engagement and all that stuff, but at the end of the day, it’s a people thing. It’s you are building these great usable experiences and fantastic looking things, but unless you are spending time with the people that are going to use it, you can miss the mark. With the environment that we are working with this customer in the UK, we have great access to commissions in the hospital that are working with us on requirements, the same way that Universal Mind will spend time in a call center and look at someone working in a cubical and figuring out that these are these posted notes and calculators and all that kind of stuff, it’s the same kind of exercise you go through.

But in this case, you are talking about being in an environment where there are literally lives around you that are at stake. I heard an interesting quote from someone who I will not name. But basically the ROI for an application like this is in a life saved that’s what the ROI is.

And when you think about all these enterprise applications and RIAs and all the stuff that are being built, and you think about a dollar value that’s attached to it, we do business and consulting. We do business where it’s about Return On Investment in a dollar amount. But we’re in this new paradigm where well, how many lives have you saved, and that’s the ROI.

Disclosure: Adobe is a client and sponsored these videos.

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

If you’re interested in an overview of IPP, I suggest last week’s episode with Intuit architect Jeff Collins.

Show Notes

• Brian tells us about Alterity and their new offering, Easy Analytics for Inventory.
• I ask Brian to tell us how they started getting interested in using IPP and what the process was like getting up and running.
• We talk about the use of Flex and how the IPP platform integrates with the UI layer.
• Brian tells us about the ability to more closely track what users are actually using and doing (or not using) in a cloud-based application.
• While customers don’t seem to be overly concerned with cloud vs. desktop deployment – at this early point – Brain says the support and even install time on cloud seems much smaller than for traditional deployment options.
• This leads to a discussion about the other effects a PaaS, like IPP, has on a company’s structure: namely not having to worry so much about billing and other back-office concerns. And then there’s all the marketing Intuit does for them in the App Center.

Full Transcript

See the full transcript over on the RIA Weekly post.

Disclosure: Intuit is a client and sponsored this episode.

This week, Coté is joined by Intuit’s Jeff Collins to talk about the Intuit Partner Platform, or IPP, a ready-to-use PaaS for building on-top of QuickBase, including with Flex.

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

IPP is a very interested Platform-as-a-Service (PaaS) available from Intuit used for building on the existing QuickBase ecosystem. It uses Flex as the user-interface technology and there’s also a marketplace available to sell the applications in. More so than just using Flex, I think IPP and platforms like it are a space where RIAs will really start to shine.

As you may recall, we’ve discussed IPP before in the podcast, notable in episode #45 with guest Alex Barnett, also of Intuit.

Also, check out the full transcript over on the RIA Weekly post.

Disclosure: Intuit is a client, and sponsored this podcast.

This week, it’s Silverlight 4, Azure, Google Gears “death,” Flash with Salesforce and RIM, and more. The full roster of Coté, Ryan Stewart, and Mike Downey are back for this one:

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

See the full transcript over on the RIAWeekly.com post of this episode.

Show notes:

• RichPlatform.com – Downey’s new blog
• Microsoft PDC 2009 – Azure, Silverlight 4, a little bit of SharePoint.
• We then get into what Azure brings for RIA developers.
• Silverlight 4 – much more “plumbing,” etc. Mike talks about the Managed Extensibility Framework for doing components in Silverlight. And here’s the Silverlight and WPF merging reporting from Mary Jo Foley I mention.
• COM in Silverlight 4 – for Office integration, also looking for how to do it on the Mac.
• Silverlight muti-touch app – Ryan got an HP Compaq L2105 multi-touch screen. TechCrunch’s first multi-touch application post.
• Also, Bing’s new, Silverlight-based maps. Also, see MG Siegler’s (TechCrunch) more cautionary take on this vs. HTML 5.
• Google Gears shut-down – was used for local storage, multi-threaded apps; obviously means Google thinks HTML 5 momentum looks good.
• Then we call back to SharePoint at PDC – SharePoint 2010, a lot of Silverlight integration – “web parts,” which are widgets for SharePoint.
• Silverlight Facebook SDK – we go off on a small tangent about Facebook being the new Aol in the making
• Flash and Salesforce (Ryan’s post)
• Flash and RIM – Adobe support for doing HTML stuff on Blackberry.
• Betas for AIR 2 and Flash 10.1, Ryan’s post
• We wrap up by talking about Ryan’s recent HTML 5 post.

A little more

Here’s some items we didn’t get to in this episode:

• Best & Worst practices for RIAs, a presentation.
• There’s an updated Flex Builder 3 for Linux, that doesn’t expire.
• WaveMaker 6.0 Cloud Development Platform Features Automated Multi-Tenant Support
• Winter Olympics via Silverlight
• Upcoming RIA related conferences.

Disclosure: Microsoft and Adobe are clients. See the RedMonk client list for other clients mentioned.

This week, Ryan and I finally get Dion Almaer and Ben Galbraith on to talk about the Palm Developer Program. Tragically, my voice goes all robot-style pretty quickly due to some (obviously) bad equipment. Thankfully, I don’t yammer on too much this episode:

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

In this episode we discuss:

• What are you guys do over at Palm?
• The announced Palm Developer program.
• Freely accessible app downloads, and raw feeds to all catalogs so people can build their own app stores.
• What’s WebOS like?
• Ben speaks to spreading the web to all aspects of programming. As Ben says, “we believe in the web.”
• Then Dion tells us the technical break-up of WebOS. Mojo, Ajax, etc. accessing device services as URLs. Multi-window applications, notifications,
• Ryan asks how mobile will (or will not) drive HTML and Ajax (or “open web”) evolution. “For us, the web really is the platform,” -Ben “We don’t want to create our own weird APIs,” they want the APIs to be standard.
• Flash on the Pre.
• I ask Dion and Ben to tell us about the Pre – is it just an iPhone clone?
• We then talk about the different form factor of mobile development a tad.
• Getting ahold of the Pre for development – in December there’ll be a developer device program, but not you just got get the retail one.

Disclosure: Adobe and Microsoft are clients. See the RedMonk client list for other clients mentioned.

Interview

Demo

(As a side note, this is the first time we’ve used VideoPress to host videos. What do you think?)

Disclosure: Adobe is a client.

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

While at SAP TechEd this week, I snagged Matthias Zeller of Adobe for a leisurely discussion about enterprise RIAs. First, we talk about the freshly announced LiveCycle Mosaic, the RIA mashup/composite application/portal-ish product Matthias and team have been working on (previously under the name “Project Genesis“). As we note in the recording, this was the product he’d been doing a lot of field research around that we discussed in episode #55. Being at SAP, we then talk about the notion of “timeless software” that SAP had been talking about and what that means for RIAs: namely, layering client RIA’s on-top of SOA-faced back-ends.

(Update, Dec 4th, 2009: I’ve added a transcript for the interview portion.)

Interview

Adam first tells us what FedEx Custom Critical does, and then we jump into a discussion of how they came to select the Adobe stack for implementation of their shipment tracking console. They not only chose Flex and LiveCycle for the rich interface, but also for the high-speed data transfer between front-end and back-end. Adam really likes the data management that comes with the stack, esp. being able to use “true push” to the client.

Transcript

Michael Coté: Hello, everybody here we at Adobe MAX 2009 in the lovely Los Angeles. Not Los Vegas and this is Michael Coté of course, with RedMonk and we’ve got a guest with ourselves. Would you like to introduce yourself?

Adam MollenKopf: Hi, I’m Adam MollenKopf. I work for FedEx Custom Critical and glad to be here today.

Michael Coté: I was talking with you little bit before the filming and we were going through the pretty interesting demo that we are going to see in a little bit, but for the first thing I’ve never actually heard of FedEx Critical, so could you tell people what exactly FedEx Critical is?

Adam MollenKopf: Absolutely; most of you are probably familiar with FedEx, the express, the ground, and the freight. Custom Critical is a unique part of FedEx that specializes in shipping things that are very time sensitive. So things that need to move from New York to Miami they would expedite it. So somebody has got an assembly line down or something we can move a part to fix that appropriately. We also do special care and handling. We do a lot of sensitive shipments for perishable goods and other items of that nature.

Michael Coté: So essentially you have — I forget the agent; you have an agent and they are kind of looking at a console and then all the various trucks are feeding into the agents view of something and then I guess you have customers calling in every 5 minutes, you know, to check on their shipment and wanting to know where it is or something. Is that the kind of typical scenario for a shipment that might be going around?

Adam MollenKopf: Exactly, so the things we ship are very high value. We need to know to the minute the location and what is happening on it at any given point in time and then intent of the application that we’ll show in just a minute is basically to detect abnormal events and present those to somebody to take proactive action on it before it becomes a bad situation, and to automate all the normal events. So when we get a position fix on a vehicle I am still going to meet the expected time of arrival. We don’t really want to nuisance an agent with that, because we have in the past, so we just want them to look at the abnormal situations expectation management.

Michael Coté: The system that we’d been talking about earlier was basically tracking a truck or whatever as it is moving along and I’m curios when you are looking at the requirements for what you were going to build, like, how did you come to the Adobe stuff? How did you make, like, an RIA essentially?

Adam MollenKopf: It was actually quite a long process to get to the Adobe solution and we finally found a good solution with Adobe. So we experimented with a number of other technologies for the last few years honestly. We tried this with [Java] Swing, we tried this with Ajax component vendors and had miserable performance and scalability issues with it in the past.

And just due to the sheer volume of the thousands of trucks that we are trying to ship and the thousands of trucks that we are trying to track and the shipments that are trying to track as well just the amount of volume was too much for those frameworks to handle.

Data services, LifeCycle, and a lot of the other Adobe technologies, Flex in specific, allowed for us to have a nice visualization of that, that was effective.

Michael Coté: Given those requirements what was it about LifeCycle Data Services, and Flex that, that fitted better than say, like, Swing or Ajax or something like that?

Adam MollenKopf: Well, data management was a big part of LifeCycle Data Services when we selected that. So being able to bind automatically to the client and bind automatically to other clients. So if you are an agent at Custom Critical and I am an agent at Custom Critical and we are looking at the same shipment and you modify something or something in field modifies it – the truck does something that causes a new state; being able to see that in near real time with very little latency was very important.

So both from a data management and from a push, having a true push technology which is something that has been absent in the past. So the RTPM, the Real Time Messaging Protocol is provided and a true push protocol that’s socket based up to the client.

Michael Coté: Right, right versus, like, HTTP or something like that, yeah.

Adam MollenKopf: The server, and the amount of data going back to the server is minimized, so it’s like an observer pattern. So the client just has an open socket and we push something he wants to observe as it changes. So we’re not killing our servers, and we have a lot less server requirements as far as the number of servers to support those.

Michael Coté: What was the development process like for when you — you said your went through several alternatives and then when you did settle on using parts of the Adobe stack for it. How long did that take and what was the process for doing it?

Adam MollenKopf: It was fairly quick with the Adobe stuff. So I got hooked up a couple of folks at Adobe and we basically did a couple of proof of concepts and it was fairly quick and actually we did most of the work on our own, it didn’t require a lot of Adobe assistance because it was pretty well documented and we were able to go in there and test out the two major features of that we were looking for. So the data management and push technology and honestly we had lots of experience trying it with other –

Michael Coté: Right, your requirements all fitted that, right.

Adam MollenKopf: Right, so it was pretty well defined and it was kind of like, well, we don’t have a solution. We still don’t have a solution and we came across Adobe and now we do have a solution.

Michael Coté: You guys are using this now and it’s finished and, like, what are your plans for it in the future?

Adam MollenKopf: To extend it, so — what we’ll show you here is just the start of what we are going to do. So there’s a lot of other areas that we are going to apply this to not only just shipment tracking but also how we price things to the customer, how do we analyze history, how do we analyze things over geography and time. Being able to reason both over space and time, add micro and macro views.

Michael Coté: So, I guess there is sort of new information about things you could sell your customers to put it one way; but you have a new understanding of things that — business practices that you were doing in the past that you can fine-tune and make up new products and things to sell to them.

Adam MollenKopf: Right, so actually some new revenue generating things that came out of this is our security surveillance. So being able to show our customer that we have almost like a Network Operation Center, but we have Security Operation Center that is basically tracking these things to this detail that puts a lot of ease to the customer’s minds when they’re shipping something very high value or something extremely sensitive, which is our specialty.

Michael Coté: Having talked about the demo so much let’s check it out.

Demo

In addition to the general RIA-ness, the special thing to note is the rules engine backing all of the predictions and analyzing sensor and geo data. Those create an interesting (and for FedEx useful) stream of real-time data to console of realtime data to churn over, expose in the RIA, and start making business decisions around.

Disclosure: Adobe is a client and sponsored these videos.

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

In this episode, I’m at SAP TechEd 2009 and jointed by SAP’s Thomas Jung and Colgate-Palmolive’s Ed Herrmann. Both, more importantly, are the the hosts of Enterprise Geeks. While this isn’t strictly an RIA themed episode, our guests Thomas Jung and Ed Hermann hit on many of the favored topics for RIA Weekly, including enterprise applications and HTML 5. We get into some HTML 5 talk as well. We discuss:

• The Enterprise Geek show – topics they’ve sussed out in the SAP, enterprise, and tech world and the emerging role the podcast plays in the SAP community.
• What they think of Google Wave: business uses for Wave and some theoretic thinking on what you’d have to do to start using it at a “normal” enterprise like, say, Colgate-Palmolive.
• What’s up with HTML 5? Does the <canvas/> tag make these two excited about dancing charts in HTML?

Disclosure: SAP is a client and paid T&E to TechEd.

You can download this episode directly directly and it’ll also show up in the RIA Weekly feed for iTunes and other podcatchers. Or, just use the controls below to listen to it right here:

With the special numbering of 9,000, we kick off Ryan and I’s highlights of Adobe MAX 2009:

• Quick rundown of Adobe MAX 2009 announcements such as: Flash 10.1 with much focus on mobile, LiveCycle ES and mobile access.
• Check out PNC’s Virtual Wallet.
• Ryan having just given a talk on the Adobe Collaboration Services, I ask him to give us an overview.
• Of the services and announcements, I like Shibuya which is Adobe’s service for doing an App Store. This brings up our favorite topic of small development shops – even of one – having a viable revenue pipe.
• Experimental code using putting FXG into the canvas tag and other sneak previews. (Check out some more HTML 5 vs. Adobe “fun” over on Apple Insider.)
• iPhone app development with the Adobe tool-chain. Be sure to check out the “iPhone in a blender” video which is sure to further win over Apple’s hearts. And, see the PhoneGap approval we reference.

Disclosure: Adobe is a client and paid travel and hotel for Adobe MAX. See the RedMonk client list for other clients mentioned.