Organization Structure, Roles, & Responsibilities for IBM PureApplication

On Tuesday at IBM Impact, Mr. Kyle Brown, Distinguished Engineer IBM Software Group Services for WebSphere, and Mr. Rajeev Gandhi Senior Technical Software Manager, hosted a session on Organization Structure, Roles, & Responsibilities for IBM PureApplication System Session. In this session the two of them turned the massive pile of IBM PureApplication System related knowledge derived from uncountable customer engagements into valuable feedback. They discussed everything from best practices to automation scripts, new roles and responsibilities, and even discussed a detailed scenario on how to funnel IBM PureApplication System adoption into an organization.

The key word in Kyle’s pitch was most likely “transient.” Doing IT the traditional way has you focused on keeping whatever you have: doing backups, maintaining environments and so on. Numerous customers have confirmed that this is where most of their IT budgets have been spent on. In the future, the IBM PureApplication System pattern-based approach allows for a more intelligent way to deal with resources, IT budget and people. Let’s list a few things I brain-picked from Kyle:

  • Environments are transient: You should consider trashing what you no longer need if there are better alternatives available and the patterns support this. Create a pattern, deploy it, rework it if necessary, redeploy it, test it and finally scratch the old instance. The “rework it” step requires some further expansion, but reworking a pattern is meaningful if you have for example an change or an update to the underlying operating system or middleware because your application or your organizational standards requires it. Just a small footnote on this though: some resources are still shared, such as the pattern, the parts, shared services.
  • Separate content from ‘infrastructure’: The application is your content, the infrastructure is whatever your application needs to run. Simply put: do not include an ear-file in the deployment script as the version of the application might change over time or be different from one environment to the other. Kyle and Rajeev call this workload = pattern instance + configuration + application.
  • Automation: Just like non-IBM PureApplication System environments, customers should have certain components in place: a version control system to store your application source code or artifacts in general, a shared storage where these artifacts can be picked from, holding different versions of the application’s ear-file to deploy in different environments and of course automation tooling such as AMC or uDeploy.

Combining all of the above you can very dynamically maintain and deploy patterns, parts, application code in every environment your organization requires. Just give it some thoughts. There are many more valuable sound bites Kyle shared so make sure you check out the presentation material.


Organizational change

Without doubt, every organization introducing an IBM PureApplication System into its existing IT ecosystem is subject to some change. Rajeev calls this evolutionary change, as it should start from what you have and evolve according to the needs which will appear with the introduction of this IBM on-premise cloud solution.

And of course, not every company is the same so most unfortunately there’s no golden cook book how to drive organizational change through your organization.

However, over the years ISSW discovered a pattern, some bits and pieces which are (nearly) always there.


Too much information to share here so again, I urge you to check out the below materials and Kyle’s video on this subject below:

And don’t forget to catch up on all our latest IBM Impact blogs here:


Comments: 1
Tom Bal

About Tom Bal

Tom Bal is a Senior Certified IT Specialist in the Software Group. Tom joined IBM Belgium through the Lotus acquisition in early 2000. For several years, he was part of the services team, assisting clients and Business Partners with different Lotus products, including IBM Lotus Notes and Lotus Workplace. He then became the technical presales representative for IBM WebSphere portal. In 2012, after two years as a client IT architect for the telecommunications industry, Tom rejoined Software Group to cover PureApplication System for the region of Europe known as Benelux, which includes Belgium, the Netherlands, and Luxembourg. Tom holds a Master of Arts degree in Translation.

One Response to Organization Structure, Roles, & Responsibilities for IBM PureApplication

  1. Anne Richard says:

    Great Information!


Comments are closed.