The Open Group, the vendor-neutral technology standards consortium, is hosting its upcoming event in Dublin, April 29 – May 2, 2019. The Open Group Dublin 2019 will bring together vendors and end-user organizations to discuss digital in practice and the Digital Enterprise. The event will host attendees from throughout the globe, including decision-makers, Enterprise Architects, engineers, technologists and end-users representing many businesses and governments.
For many of us, each new year is an occasion to look back at the previous year’s accomplishments, as well as look forward to what’s to come over the course of the next year. For the past three years since I took over the reins as CEO of The Open Group, I’ve made it a tradition to take advantage of the new year to do just this, as I’m sure many of you do both in your professional and personal lives.
With the passing of each year, I’m always struck not only by how quickly it goes by, but how many new opportunities arise throughout the year for The Open Group that none of us ever could have predicted. What’s nice for me, from where I sit, is that there is no shortage of new opportunities for us as an organization to do what we’ve always done—to help organizations come together to solve their business problems through open standards.
When I think of an “executable standard”, I think of a standard that is capable of being fulfilled (i.e. a standard that can readily impact real world things, whether those things are people, processes, or technology). Regardless of what I think, it isn’t easy to define an executable standard – however I think the following will help everyone understand the essence of an executable standard.
In two prior blogs, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing and what it might look like.
Why? Because a properly implemented service delivery model would put the emphasis in more appropriate places:
Production and use value versus EA as a deliverable
Timely value along the way versus at the end
Clear expectations versus vague promise
Support and enablement versus ivory tower compliance
What? A portfolio of services provided on demand in service categories:
Planning Services to scope based on need
Buy-in/collaboration Services to ensure the right people in the organization are engaged
Development Services to build the right parts of an EA at the right time
Management Services to ensure that the EA efforts delivers value consistently
Usage Services to derive value from the EA
Decision Support Services to support Portfolio Governance decisions
In my previous blog, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing. Fundamentally because a properly implemented service delivery model would put the emphasis in more appropriate places:
– Production and use value versus EA as a deliverable
– Timely value along the way versus at the end
– Clear expectations versus vague promise
– Support and enablement versus ivory tower compliance
In April 2018, I had the privilege of attending The Open Group conference in London with the theme: The TOGAF® Standard in 2018. After seven years, we see the release of the latest version TOGAF Standard 9.2. As a member of the English translation team for the TOGAF Standard Version 9.1, I have learned the difference in the new version and had a lot of thoughts. On the one hand, many improvements in the new version are highly consistent with the knowledge and practical experience of the Aviation Industry Group in the field of architecture method. On the other hand, the active development and continuous improvement of the knowledge system reflect that the architecture method has huge demands and driving force at the practice level. There is still a big gap between Chinese and international applications in this respect. This article attempts to understand and share this updated version from the perspective of application. In addition, I hope that Chinese practitioners can get inspiration and confidence from these changes.