OMS SafeHarbor

Connecting Software and Customers

What is in a name? ESD or ESD

with 2 comments

What is in a name?

Imagine a world where a rose at night meant something different from a rose during the day. Imagine a world where context makes the difference between night and day. Welcome to the world of ESD. No, ESD for me is not electrical static discharge however the definition on one web page starts out promisingly as “an ESD system comprises a user-accessible subsystem” however it continues on as “(for example, a first gasoline pump), a local ground …”. That comparison aside, ESD can mean different things to different companies and people its all in the context you see. For instance, OMS SafeHarbor and other companies have electronic software delivery (distribution) systems while Content Distribution Networks (CDNs) like our own partner Akamai have ESD services. So this blog explores how our ESD is different from a CDN’s ESD and how, in fact, they are complimentary.

Let’s start out with a broad definition of ESD; the kind that is shockingly fast not the kind with electrons leaping to a grounded source. Electronic Software Delivery at its very heart is about delivering software products to end users via the internet versus physical delivery. The basis for all software delivery is digital assets (electronic finished goods – the software and documentation). Digital assets refer to any files related to a product. Okay actually here is the first difference between us and CDNs; they are focused on files while we define products as a collection of files. In the end we both want to deliver the file(s) but where we start defines where we can go. In actual fact, CDNs are very much about networks, point-to-point delivery and file downloads while our ESD is about entitlements, products, users, and downloads.

Entitlements are simply the tangible obligations software vendors have to their customers. A customer purchases product A and therefore has an entitlement to the deliverables associated with product A. Entitlements can be shared between users through accounts or through other means, they allow company ABC to have a number of people access the digital assets associated with product A. Products are a collection of files (deliverables/digital assets) but have a structure, content and metadata associated with them. Files have attributes, a name and a size, and have a binary representation.

OMS SafeHarbor’s ESD provides controlled access to digital assets through entitlements. An Entitlement Center is dynamically constructed for each user based on their personal or account entitlements. It provides the list of products which have descriptions and other metadata along with a structure for the digital assets (release notes, CD1, install zip and user guide) and each of those digital assets have content (files). So here is why we are partners with CDNs like Akamai, because they make the delivery (point-to-point) for files go faster and more reliably across the internet. CDNs need web pages, emails or some other event driven process (like our entitlement center access) to make the link between a user or computer and the file to be downloaded. We provide the control center and they provide the network.

In the end, ESD is all about getting the software delivered but how you get started defines where you can go. For instance starting with an eCommerce system to purchase products and a CDN to deliver them you can effectively perform Initial Product Delivery (IPD). The customer can buy the product and download it as fast as the transaction is approved but what about subsequent support (updates, lost files and license management). Start with our ESD system, bolt on eCommerce and integrate with a CDN ESD and you have a complete vehicle. The customer buys his software online or through traditional sales channels, the orders flow into our ESD solution to create entitlement and notify the customer they can access the product now and again in the future. Release a fix or service pack use product chaining to identify those who have a base entitlement and then notify them they can come and get it now (or later) when they access the entitlement center. When they click on the file to download, we can have them accept the EULA (license agreement), we can validate them against government lists and verify by geolocational lookup that we are following export compliance regulations and your business practices and then we can call the CDN to delivery point-to-point through the internet. That’s the universe we live in, where ESD meets the complete needs of offering customer self-service for IPD and updates, where marketing intelligence can meet product registration and entitlement management, where integration, automation and digital product management can meet the challenge of replacing manual and physical processes to deliver software efficiently and cost- effectively.

Written by roger242

September 24, 2008 at 19:18 pm

2 Responses

Subscribe to comments with RSS.

  1. I find it ironic that your definition of ESD isn’t consistent even within your own blog. This article states, “Electronic Software Delivery at its very heart is about delivering software products…”

    Yet an article down the page writes, “Additionally, the service is integrated with our Electronic Software Distribution solution…”

    And your tag cloud on the right refers in big letters to “Electronic Software Distribution”. So when you ask “ESD or ESD?”, I think you need to tell us if it’s Delivery or Distribution! I’ve heard both used and the acronym can stand for either, but I would think your company would want to be consistent with its definition.

    (I’ve been doing ESD for 11 years and prefer “Distribution” myself.)

    Great to see a new blog on the subject!

    Thanks,
    Gary

    Gary Zellerbach

    September 25, 2008 at 15:50 pm

  2. Thanks for the feedback Gary. We’ve been following your blog for quite a few years now. Hopefully we can add to your contributions in this area.

    *NOTE* We’ve added Gary’s blog to our blogroll and we encourage any visitors here to read and subscribe Gary’s fine work.

    Jay Nash

    September 25, 2008 at 16:12 pm


Leave a Reply