Skip to main content

Progress on Grid licensing

One of the events on our SC06 stand was a vendors' round-table discussion on Grid licensing. Representatives from Platform, NAG, Visual Numerics, Allinea, among others, contributed their thoughts on how we can produce more flexible licensing schemes for Grid use cases. There are two levels of concern: technical and business.

At the technical level, some vendors expressed frustration that the licensing systems that are currently available are too restrictive. So even though they want to offer more flexible business models, the underlying technology prevents them from doing so. There was broad agreement that a usage-based monitoring technology would provide a more flexible substrate.

There were several scenarios offerred at the business level. One of the simplest is to charge directly based on use. Ohio State University want to do this for local SME's who are just setting out down the road to Grid adoption; these SMEs don't want to commit to a large upfront cost when they are just experimenting with the technology. More complex use cases were suggested that would give more predictable costs for users and more predictable revenue streams for vendors. These would take advantage of the usage tracking technology but would not be constrained by it.

What made this discussion rather different from similar panels before is that there is a plan to work towards possible solutions. A first step will be to produce sample use cases for Grid licensing, together with outlines of what licenses would be required for each. This should help to frame the discussion and set requirements on any usage monitoring system.

My thanks to David Wallom and Laura McGinnis for organising this event and choosing UK e-Science to host it. I look forward to observing developments. I am certain that we will develop the discussion further at OGF20 in Manchester next year.


Popular posts from this blog

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…