Enterprise Architecture
Next: Canada, US, and Iceland
0As indicated in a 140 char note on Twitter, I’m leaving Europe. For a month, that is. I am going on a flight/roadtrip, part work, part vacation. Locationwise roughly as follows:
- Toronto from July 17th to 25th.
- Washington, DC from July 26th to 31st.
- Ottawa from July 31st to August 6th.
- Boston from August 7th to 14th.
oh, and then a stopover in Iceland: - ReykjavÃk from August 14th to 18th.
Along the way I will attend The Open Group’s 23rd Enterprise Architecture Practitioners Conference in Toronto, where I have three contributions: Particapant in Panel Discussion and podcast on Architecture’s Scope Extends Beyond the Enterprise, my lecture Coherency Management and the Future of Enterprise Architecture, and participant in Panel Discussion: Enterprise-Centric Architecture and the Role of “Businessâ€.
I will probably sneak in a bunch of meetings around the Coherency Management book, which is now with the printer, and with a bit of luck, will be able to announce a few events around the book as I travel on. And then I’m planning some meetings around a new book project I plan to announce shortly. Which reminds me: allow me to introduce two new tags: Government 2.0 and Open Government.
If you are located – or happen to be – in one of the locations I visit, and are interested in any of the tags to this post, and want to meet, get in touch.
Next Generation EA
0Come join us for Architecture Friday in Antwerp on 26 June about next generation enterprise architecture, as seen by two Australians and a Dane: Peter Bernus (wp) and Pat Turner, and me. If you want to participate, get in touch (you may get a discount code!).
Peter Bernus chairs IFIP WG5.12 Architectures for Enterprise Integration, and arranges the ICEIMT Workshop Next Generation Enterprise Architecture on 23-24 June in Leiden, which I have just registred for (unfortunately only last day). Themes on the agenda:
- Next Generation Enterprise Architecture (NextGenEA): what is it, what does it need to succeed and what does it include: Interoperability, ‘Cloud Computing’, new ways of Visualization, Enterprise Integration, Enterprise Resource Management, Enterprise Data Consolidation
- Role of the senior Decision Maker: What is the role of the senior decision maker? What types of information and tools do they require to be effective? Can NextGen EA make a difference or indeed add any value to the day to day activities and key decisions made by senior business managers within a modern Organization?
- Decision Support Tools: What are the current EA tools on the market? What are the current management decision support tools available to senior decision makers? Is there a gap or a cross over point between the two or is the current marketplace effectively being served by existing product offerings?
- Enterprise Architecture Frameworks (practice and theory): What do existing EA frameworks say about the role of senior decision makers in the architectural process and what is the role of architecture in the making of critical business decisions within the modern Organization?
- Interoperability: Â present and future trends & standardization across Organizations? How do these trends support or refute the case for NextGen EA as a tool for senior decision makers within the modern Organization?
- NextGen EA: New theories and techniques, interdisciplinary approaches for combining Management Theory and traditional EA topics, such as Enterprise Modelling / Enterprise Engineering / Enterprise Integration
- Which Research Frameworks are appropriate for the investigation of the above questions? Â Human understanding and communication as a condition of interoperability. Suitable social and organisational structures that create the motivation and the opportunity to achieve common understanding and consensus and the potential need for new organisational forms and cultural change
Being a ICEIMT workshop means it is part of the International Conference on Enterprise Integration and Modelling Technology, a series of landmark conferences held since 1992. ICEIMT originally started as a strategic initiative of NIST and the European Union to review the state of the art in Enterprise Integration (EI) and to make recommendations to industry and research, creating roadmaps for EI research and product development. I’m proud to say that I have just joined the ICEIMT’2010 Steering Committee.
Before the actual ICEIMT’2010, which is not yet scheduled/placed, the will be another workshop, on 14-16 December in Bled in Slovenia. The main objective of this workshop is to bring together management scientists, engineers and enterprise architects to hold an open discussion on the future synergies of these disciplines.
- business design and business management — the use of enterprise architecture practice in various transformations
- coherency of decision making — from senior management to low level control
- whole of life and complete life cycle approaches to enterprise engineering — the systems science of EA and management
- decision support tools — enterprise modelling, business process management & analysis, and business intelligence
- the fusion of the management and engineering disciplines
- the enterprise architect as a profession: skills, education, training and accreditation
- unifying theories and enterprise ontologies
- architecture frameworks and their use in managing projects, programmes, enterprises and networks of enterprises
- case studies
- open research questions
- etc.
The Leiden-workshop is part of ICE2009 conference on “Collaborative Innovation: Emerging Technologies, Environments and Communitiesâ€. ICE stands for International Conference on Concurrent Enterprising. The term Concurrent Enterprising is
an amalgam which brings together the paradigms of Concurrent Engineering and Extended/Virtual Enterprising: The Concurrent Enterprise is a distributed, temporary alliance of independent, co-operating manufacturers, customers and suppliers using systematic approaches, methods and advanced technologies for increasing efficiency in the design and manufacturing of products and services by means of concurrency, parallelism, integration, standardisation, team work and more for achieving common goals on global markets.
Sounds interesting, but I only have time to attend the NextGenEA workshop. Actually, only half of it.
Counting Down to Book Launch
1This has been a great week, for several reason, but most notably because our book, Coherency Management: Architecting the Enterprise for Alignment, Agility and Assurance, is now in AuthorHouse’s hands and should be ready for ordering very soon. On the book’s website, we have published the Table of Contents and a chapter overview, and also some endorsements. And some background interviews with the editors (here’s the interview with me).
The book introduces the idea of Coherency Management, and asserts that this is the primary outcome goal of an enterprise’s architecture.
Editors of the book are Gary Doucet, John Gøtze, Pallab Saha, and Scott Bernard. With submissions from over 30 authors and co-authors, the book reinforces the idea that EA is being practiced in an ever-increasing variety of circumstances – from the tactical to the strategic, from the technical to the political, and with governance that ranges from sell to tell. The characteristics, usages, value statements, frameworks, rules, tools and countless other attributes of EA seem to be anything but orderly, definable, classifiable, and understandable as might be hoped given heritage of EA and the famous framework and seminal article on the subject by John Zachman over two decades ago. Notably, EA is viewed as an Enterprise Design and Management approach, adopted to build better enterprises, rather than a IT Design and Management approach limited to build better systems.
We will use the coherencymanagement.org website not just to promote the book, but also to be a platform for continued dialogues about coherency management and for publishing further studies. We’re especially interested in relevant case studies, and have published one such: Neil Kemp’s interesting case study about Winnipeg Fleet Management.
More Book Reviews
1Overall: I recommend the following three books.
In Advances in Government Enterprise Architecture, my good friend Pallab Saha over in Singapore has made a seminal compilation of 18 chapters on government enterprise architecture written by practitioners and practicing academics from Australia, Germany, Greece, Ireland, The Netherlands, Singapore, South Korea, United Kingdom, and United States of America. Several of the contributing authors also have chapters in the Coherency Management book that Pallab and I, together with Gary Doucet and Scott Bernard, are releasing very soon.
If I should emphasise one chapter from the book, it has to be Pallab Saha’s own chapter about Singapore’s e-government initiative and the Methodology for AGency ENTerprise Architecture (MAGENTA), “a rigorous, disciplined and structured methodology for development of agency enterprise architectures that enables agencies to align to and fully support the government’s transformation objectives and outcomes”. Very interesting read.
With its 502 pages, Advances provides a very solid view on governmental EA. It is a perfect book for students and researchers of e-government and governmental EA, alas its cost ($195 at Amazon) means that the students have to wait for their libraries to get the book. This is without doubt the reference book for government EA.
In Enterprise Governance and Enterprise Engineering, Dr. Ir. Jan A.P. Hoogervorst from Sogeti in the Netherlands presents a competence-based perspective on governance, where “employees are viewed as the crucial core for effectively addressing the complex, dynamic and uncertain enterprise reality, as well as for successfully defining and operationalizing strategic choices”. Hoogervorst sees enterprise engineering as “the formal conceptual framework and methodology for arranging a unified and integrated enterprise design, which is a necessary condition for enterprise success”.
Hoogervorst defines Enterprise architecture as “a coherent and consistent set of principles and standards that guides enterprise design,” and he argues that EA is a communicative bridge between the functional and constructional perspectives, that is between a functional, requirements-oriented, black-box system perspective and a constructional, realization-oriented, white-box perspective. I like Hoogervorst’s approach to EA. It’s neither IT-centric nor business-centric; if anything, it’s enterprise-centric.
The last chapter is about a fictitios case, an energy company. While this certainly helps in understanding enterprise governance and enterprise design in practice, it is in my opinion still leaving the reader with unanswered questions about enterprise engineering. As if Hoogervorst or Springer ‘forgot’ some additional chapters of the book. Or maybe it’s just a ‘cliffhanger’ to forthcoming books? Hoogervorst’s book is the second to be published in Springer’s Enterprise Engineering Series (I reviewed the first book in the series back in December). This series is aimed at academic students and advanced professionals. I’ll certainly recommend Hoogervorst’s book to my students.
The third book I’ll talk about here has been on my book shelf for a while, as it was published in November 2007, and I bought it right away, but must admit that it didn’t really catch me on the first reading back then. Recently, I was prompted to pick it up again, and am actually happy I did.
In Lost in Translation (book’s site), Nigel Green and Carl Bate from CapGemini describe a simplified ‘language’ for preventing loss in translation from business needs to IT solutions. This language is called ‘VPEC-T after the five dimensions it focuses on: Values, Policies, Events, Content and Trust. VPEC-T is presented as a common language that is natural for both business and IT, and is “straightforward enough to use, yet sophisticated enough to work in today’s connected world.”
Subtitled “A handbook for information systems in the 21st century”, the authors do not hide their interests: They provide a tool (‘language’) for how IT-people can become better at capturing what the business wants from IT. In this sense, it’s classic Information Systems thinking (chapter 2), and VPEC-T does indeed come across as, yes, yet another IS-approach. But also, as one that may well take some IS-territory, perhaps especially from IS-practitioners. I will certainly follow VPEC-T. I follow @taoofit on Twitter. I’ve also joined the VPEC-T Google Group. Also, google the acronym and you’ll find a few good things by adopters of it, for example the VPEC-T mindmap which seems quite useful.


