Skip to main content

OGF20 Registration is open

Much of the reason I haven't blogged here more frequently is that I am programme chair of OGF20 and this is taking much of my time. So I'm pleased to report that registration for OGF20 is now open. Here is the official announcement. Note that early registration rates are available until March 15th.

Some aspects of the programme have been confirmed; others are still being finalised. I'll post news here over the next few weeks.

Registration is now open for OGF20 and the EGEE 2nd User Forum being held May 7-11 in Manchester, UK. Register on-line by visiting

This event will feature:
• Keynote and Plenary presentations by leading grid luminaries
• Chartered Group Sessions including Standards Working Group Sessions and BoFs
• Enterprise Track including Requirements Alignment, Best Practices and Adoption Sessions
• e-Science Track featuring Community Workshops
• ‘Grids Means Business’ Industry Program showcasing business solutions and case studies
• Vendor Showcase and Exhibit Hall
• Demonstration and Poster Session Area
• Networking and Social Activities

About OGF20 and the EGEE User Forum
OGF20, presented by the Open Grid Forum and co-located with EGEE's 2nd User Forum, is the premier grid technologies event of 2007. At OGF20/EGEE UF, the global Grid community will gather to develop Grid standards, showcase real-world applications, workshop Enterprise and eSciences best practices and present business case studies and solutions. OGF20 is hosted by UK e-Science and the University of Manchester. Grids Means Business Program is sponsored by Grid Computing Now!


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…