Author Archives: The Open Group Blog

The Open Group San Diego Panel Explores Synergy Among Major Frameworks in Enterprise Architecture

Following is a transcript of part of the proceedings from The Open Group San Diego event in February – a panel discussion on The Synergy of Enterprise Architecture frameworks.

The following panel, which examines the synergy among the major Enterprise Architecture frameworks, consists of moderator Allen Brown, President and Chief Executive Officer, The Open Group; Iver Bank, an Enterprise Architect at Cambia Health Solutions; Dr. Beryl Bellman, Academic Director, FEAC Institute; John Zachman, Chairman and CEO of Zachman International, and originator of the Zachman Framework; and Chris Forde, General Manager, Asia and Pacific Region and Vice President, Enterprise Architecture, The Open Group.

Here are some excerpts:

By The Open GroupIver Band: As an Enterprise Architect at Cambia Health Solutions, I have been working with the ArchiMate® Language for over four years now, both working with and on it in the ArchiMate® Forum. As soon as I discovered it in late 2010, I could immediately see, as an Enterprise Architect, how it filled an important gap.

It’s very interesting to see the perspective of John Zachman. I will briefly present how the ArchiMate Language allows you to fully support enterprise architecture using The Zachman Framework. So I am going to very briefly talk about enterprise architecture with the ArchiMate Language and The Zachman Framework.

What is the ArchiMate Language? Well, it’s a language we use for building understanding across disciplines in an organization and communicating and managing change.  It’s a graphical notation with formal semantics. It’s a language.

It’s a framework that describes and relates the business, application, and technology layers of an enterprise, and it has extensions for modelling motivation, which includes business strategy, external factors affecting the organization, requirements for putting them altogether and for showing them from different stakeholder perspectives.

You can show conflicting stakeholder perspectives, and even politics. I’ve used it to model organizational politics that were preventing a project from going forward.

It has a rich set of techniques in its viewpoint mechanism for visualizing and analyzing what’s going on in your enterprise. Those viewpoints are tailored to different stakeholders.  And, of course, ArchiMate®, like TOGAF®, is an open standard managed by The Open Group.

Taste of Archimate

This is just a taste of ArchiMate for people who haven’t seen it before. This is actually excerpted from the presentation my colleague Chris McCurdy and I are doing at this conference on Guiding Agile Solution Delivery with the ArchiMate Language.

What this shows is the Business and Application Layers of ArchiMate. It shows a business process at the top. Each process is represented by a symbol. It shows a data model of business objects, then, at the next layer, in yellow.

Below that, it shows a data model actually realized by the application, the actual data that’s being processed.

Below that, it shows an application collaboration, a set of applications working together, that reads and writes that data and realizes the business data model that our business processes use.

All in all, it presents a vision of an integrated project management toolset for a particular SDLC that uses the phases that you see across the top.

We are going to dissect this model, how you would build it, and how you would develop it in an agile environment in our presentation tomorrow.

I have done some analysis of The Zachman Framework, comparing it to the ArchiMate Language. What’s really clear is that ArchiMate supports enterprise architecture with The Zachman Framework. You see a rendering of The Zachman Framework and then you see a rendering of the components of the ArchiMate Language. You see the Business Layer, the Application Layer, the Technology Layer, its ability to express information, behavior, and structure, and then the Motivation and Implementation and Migration extensions.

So how does it support it? Well, there are two key things here. The first is that ArchiMate models answer the questions that are posed by The Zachman Framework columns.

For what: for Inventory. We are basically talking about what is in the organization. There are Business and Data Objects, Products, Contracts, Value, and Meaning.

For how: for process. We can model Business Processes and Functions. We can model Flow and Triggering Relationships between them.

Where: for the Distribution of our assets. We can model Locations, we can model Devices, and we can model Networks, depending on how you define Location within a network or within a geography.

For who: We can model Responsibility, with Business Actors, Collaborations, and Roles.

When: for Timing. We have Business Events, Plateaus of System Evolution, relatively stable systems states, and we have Triggering Relationships.

Why: We have a rich Motivation extension, Stakeholders, Drivers, Assessments, Principles, Goals, Requirements, etc., and we show how those different components influence and realize each other.

Zachman perspectives

Finally, ArchiMate models express The Zachman Row Perspectives. For the contextual or boundary perspective, where Scope Lists are required, we can make catalogs of ArchiMate Concepts. ArchiMate has broad tool support, and in a repository-based tool, while ArchiMate is a graphical language, you can very easily take list of concepts, as I do regularly, and put them in catalog or metrics form. So it’s easy to come up with those Scope Lists.

Secondly, for the Conceptual area, the Business Model, we have a rich set of Business Layer Viewpoints. Like the top of the — that focus on the top of the diagram that I showed you; Business Processes, Actors, Collaborations, Interfaces, Business Services that are brought to market.

Then at the Logical Layer we have System. We have a rich set of Application Layer Viewpoints and Viewpoints that show how Applications use Infrastructure.

For Physical, we have an Infrastructure Layer, which can be used to model any type of Infrastructure: Hosting, Network, Storage, Virtualization, Distribution, and Failover. All those types of things can be modeled.

And for Configuration and Instantiation, the Application and Technology Layer Viewpoints are available, particularly more detailed ones, but are also important is the Mappings to standard design languages such as BPMN, UML and ERD. Those are straightforward for experienced modelers. We also have a white paper on using the ArchiMate language with UML. Thank you.

By The Open GroupDr. Beryl Bellman: I have been doing enterprise architecture for quite a long time, for what you call pre-enterprise architecture work, probably about 30 years, and I first met John Zachman well over 20 years ago.

In addition to being an enterprise architect I am also a University Professor at California State University, Los Angeles. My focus there is on Organizational Communications. While being a professor, I always have been involved in doing contract consulting for companies like Digital Equipment Corporation, ASK, AT&T, NCR, then Ptech.

About 15 years ago, a colleague of mine and I founded the FEAC Institute. The initial name for that was the Federal Enterprise Architecture Certification Institute, and then we changed it to Federated. It actually goes by both names.

The business driver of that was the Clinger–Cohen Bill in 1996 when it was mandated by government that all federal agencies must have an enterprise architecture.

And then around 2000, they began to enforce that regulation. My business partner at that time, Felix Rausch, and I felt that we need some certification in how to go about doing and meeting those requirements, both for the federal agencies and the Department of Defense. And so that’s when we created the FEAC Institute.

Beginning of FEAC

In our first course, we had the Executive Office of the President, US Department of Fed, which I believe was the first Department of the Federal Government that was hit by OMB which held up their budget for not having an enterprise architecture on file. So they were pretty desperate, and that began the first of the beginning of the FEAC.

Since that time, a lot of people have come in from the commercial world and from international areas. And the idea of FEAC was that you start off with learning how to do enterprise architecture. In a lot of programs, including TOGAF, you sort of have to already know a little bit about enterprise architecture, the hermeneutical circle. You have to know what it is to know.

In FEAC we had a position that you want to provide training and educating in how to do enterprise architecture that will get you from a beginning state to be able to take full responsibility for work doing enterprise architecture in a matter of three months. It’s associated with the California State University System, and you can get, if you so desire, 12 graduate academic units in Engineering Management that can be applied toward a degree or you can get continuing education units.

So that’s how we began that. Then, a couple of years ago, my business partner decided he wanted to retire, and fortunately there was this guy named John Zachman, who will never retire. He’s a lot younger than all of us in this room, right? So he purchased the FEAC Institute.

I still maintain a relationship with it as Academic Director, in which primarily my responsibilities are as a liaison to the universities. My colleague, Cort Coghill, is sort of the Academic Coordinator of the FEAC Institute.

FEAC is an organization that also incorporates a lot of the training and education programs of Zachman International, which includes managing the FEAC TOGAF courses, as well as the Zachman certified courses, which we will tell you more about.

‘m just a little bit surprised by this idea, the panel, the way we are constructed here, because I didn’t have a presentation. I’m doing it off the top, as you can see. I was told we are supposed to have a panel discussion about the synergies of enterprise architecture. So I prepared in my mind the synergies between the different enterprise architectures that are out there.

For that, I just wanted to make a strong point. I wanted to talk about synergy like a bifurcation between on the one hand, “TOGAF and Zachman” as being standing on one side, whereas the statement has been made earlier this morning and throughout the meeting is “TOGAF and.”

Likewise, we have Zachman, and it’s not “Zachman or, but it’s ‘Zachman and.” Zachman provides that ontology, as John talks about it in his periodic table of basic elements of primitives through which we can constitute any enterprise architecture. To attempt to build an architecture out of composites and then venting composites and just modeling  you’re just getting a snapshot in time and you’re really not having an enterprise architecture that is able to adapt and change. You might be able to have a picture of it, but that’s all you really have.

That’s the power of The Zachman Framework. Hopefully, most of you will attend our demonstration this afternoon and a workshop where we are actually going to have people work with building primitives and looking at the relationship of primitives, the composites with a case study.

Getting lost

On the other side of that, Schekkerman wrote something about the forest of architectural frameworks and getting lost in that. There are a lot of enterprise architectural frameworks out there.

I’m not counting TOGAF, because TOGAF has its own architectural content metamodel, with its own artifacts, but those does not require one to use the artifacts in the architectural content metamodel. They suggest that you can use DoDAF. You can use MODAF. You can use commercial ones like NCR’s GITP. You can use any one.

Those are basically the competing models. Some of them are commercial-based, where organizations have their own proprietary stamps and the names of the artifacts, and the wrong names for it, and others want to give it its own take.

I’m more familiar nowadays with the governmental sectors. For example, FEAF, Federal Enterprise Architecture Framework Version 2. Are you familiar with that? Just go on the Internet, type in FEAF v2. Since Scott Bernard has been the head, he is the Chief Architect for the US Government at the OMB, he has developed a model of enterprise architecture, what he calls the Architecture Cube Model, which is an iteration off of John’s, but he is pursuing a cube form rather than a triangle form.

Also, for him the FEAF-II, as enterprise architecture, fits into his FEAF-II, because at the top level he has the strategic plans of an organization.

It goes down to different layers, but then, at one point, it drops off and becomes not only a solution, but it gets into the manufacturing of the solution. He has these whole series of artifacts that pertain to these different layers, but at the lower levels, you have a computer wiring closet diagram model, which is a little bit more detailed than what we would consider to be at a level of enterprise architecture.

Then you have the MODAF, the DoDAF, and all of these other ones, where a lot of those compete with each other more on the basis of political choices.

With the MODAF, the British obviously don’t want to use DoDAF, they have their own, but they are very similar to each other. One view, the acquisition view, differs from the project view, but they do the same things. You can define them in terms of each other.

Then there is the Canadian, NAF, and all that, and they are very similar. Now, we’re trying to develop the unified MODAF, DoDAF, and NAF architecture, UPDM, which is still in its planning stages. So we are moving toward a more integrated system.

BrownAllen Brown: Let’s move on to some of the questions that folks are interested in. Moving away from what the frameworks are, there is a question here. How does enterprise architecture take advantage of the impact of new emerging technologies like social, mobile, analytics, cloud, and so on?

Bidirectional change

John A Zachman: The change can take place in the enterprise either from the top, where we change the context of the enterprise, or from the bottom, where we change the technologies.

So technology is expressed in the context of the enterprise, what I would call Rule 4, and that’s the physical domain. And it’s the same way in any other — the building architecture, the airplane architecture, or anything. You can implement the logic, the as-designed logic, in different technologies.

Whatever the technology is, I made an observation that you want to engineer for flexibility. You separate the independent variables. So you separate the logic at Rule 3 from the physics of Rule 4, and then you can change Rule 4 without changing Rule 3. Basically that’s the idea, so you can accommodate whatever the emerging technologies are.

Bellman: I would just continue with that. I agree with John. Thinking about the synergy between the different architectures, basically every enterprise architecture contains, or should contain, considerations of those primitives. Then, it’s a matter of which a customer wants, which a customer feels comfortable with? Basically as long as you have those primitives defined, then you essentially can use any architecture. That constitute the synergy between the architectures.

Band: I agree with what’s been said. It’s also true that I think that one of the jobs of an enterprise architect is to establish a view of the organization that can be used to promote understanding and communicate and manage change. With cloud-based systems, they are generally based on metadata, and the major platforms, like Salesforce.com as an example. They publish their data models and their APIs.

So I think that there’s going to be a new generation of systems that provide a continuously synchronized, real-time view of what’s going on in the enterprise. So the architectural model will model this in the future, where things need to go, and they will do analyses, but we will be using cloud, big data, and even sensor technologies to understand the state of the enterprise.

Bellman: In the DoDaF 2.0, when that initially came out, I think it was six years ago or so, they have services architecture, a services view, and a systems view. And one of the points they make within the context, not as a footnote, is that they expect the systems view to sort of disappear and there will be a cloud view that will take its place. So I think you are right on that.

Chris Forde: The way I interpreted the question was, how does EA or architecture approach the things help you manage disruptive things? And if you accept the idea that enterprise architecture actually is a management discipline, it’s going to help you ask the right questions to understand what you are dealing with, where it should be positioned, what the risks and value proposition is around those particular things, whether that’s the Internet of Things, cloud computing, or all of these types of activities.

So going back to the core of what Terry’s presentation was about is a decision making framework with informed questions to help you understand what you should be doing to either mitigate the risk, take advantage of the innovation, and deploy the particular thing in a way that’s useful to your business. That’s the way I read the question.

Impact of sensors

Band: Just to reinforce what Chris says, as an enterprise architect in healthcare, one of the things that I am looking at very closely is the evaluation of the impact of health sensor technology. Gartner Group says that by 2020, the average lifespan in a developed country will be increased by six months due to mobile health monitoring.

And so there are vast changes in the whole healthcare delivery system, of which my company is at the center as a major healthcare payer and investor in all sorts of healthcare companies. I use enterprise architecture techniques to begin to understand the impact of that and show the opportunities to our health insurance business.

Brown: If you think about social and mobile and you look at the entire enterprise architecture, now you are starting to expand that beyond the limits of the organization, aren’t you? You’re starting to look at, not just the organization and the ecosystem, your business partners, but you are also looking at the impact of bringing mobile devices into the organization, of managers doing things on their own with cloud that wasn’t part of the architecture. You have got the relationship with consumers out there that are using social and mobile. How do you capture all of that in enterprise architecture?

Forde: Allen, if I had the answer to that question I would form my own business and I would go sell it.

Back in the day, when I was working in large organizations, we were talking about the extended enterprise, that kind of ecosystem view of things. And at that time the issue was more problematic. We knew we were in an extended ecosystem, but we didn’t really have the technologies that effectively supported it.

The types of technologies that are available today, the ones that The Open Group has white papers about — cloud computing, the Internet of Things, this sort of stuff — architectures can help you classify those things. And the technologies that are being deployed can help you track them, and they can help you track them not as documents of the instance, but of the thing in real time that is talking to you about what its state is, and what its future state will be, and then you have to manage that information in vast quantities.

So an architecture can help you within your enterprise understand those things and it can help you connect to other enterprises or other information sources to allow you to make sense of all those things. But again, it’s a question of scoping, filtering, making sense, and abstracting — that key phrase that John pointed out earlier, of abstracting this stuff up to a level that is comprehensible and not overwhelming.

Brown: So Iver, at Cambia Health, you must have this kind of problem now, mustn’t you?

Provide value

Band: That’s exactly what I am doing. I am figuring out what will be the impact of certain technologies and how our businesses can use them to differentiate and provide value.

In fact, I was just on a call this morning with JeffSTAT, because the whole ecosystem is changing, and we know that healthcare is really changing. The current model is not financially sustainable, and there is also tremendous amount of waste in our healthcare system today. The executives of our company say that about a third of the $2.7 trillion and rising spent on healthcare in the US doesn’t do anyone any good.

There’s a tremendous amount of IT investment in that, and that requires architecture to tie it altogether. It has to do with all the things ranging from the logic with which we edit claims, to the follow-up we provide people with particularly dangerous and consequently expensive diseases. So there is just a tremendous amount going through an enterprise architecture. It’s necessary to have a coherent narrative of what the organization needs to do.

Bellman: One thing we all need to keep in mind is even more dynamic than that, if you believe even a little bit of Kurzweil’s possibilities is that — are people familiar with Ray Kurzweil’s ‘The Singularity Is Near’ — 2037 will be around the singularly between computers and human beings.

So I think that the wrap where he argues that the amount of change is not linear but exponential, and so in a sense you will never catch up, but you need an architecture to manage that.

By The Open GroupZachman: The way we deal with complexity is through classification. I suggest that there is more than one way to classify things. One is one-dimensional classification, taxonomy, or hierarchy, in effect, decompositions, one-dimensional classification, and that’s really helpful for manufacturing. From an engineering standpoint of a two-dimensional classification, where we have classified things so that they are normalized, one effect in one place.

Then if you have the problems identified, you can postulate several technology changes or several changes and simulate the various implications of it.

The whole reason why I do architecture has to do with change. You deal with extreme complexity and then you have to accommodate extreme change. There is no other way to deal with it. Humanity, for thousands of years, has not been able to figure out a better way to deal with complexity and change other than architecture.

Forde: Maybe we shouldn’t apply architecture to some things.

For example, maybe the technologies or the opportunity is so new, we need to have the decision-making framework that says, you know what, let’s not try and figure out all this, just to self-control their stuff in advance, okay? Let’s let it run and see what happens, and then when it’s at the appropriate point for architecture, let’s apply it, this is a more organic view of the way nature and life works than the enterprise view of it.

So what I am saying is that architecture is not irrelevant in that context. It’s actually there is a part of the decision-making framework to not architect something at this point in time because it’s inappropriate to do so.

Funding and budgeting

Band: Yeah, I agree that wholeheartedly. If it can’t be health solutions, we are a completely agile shop. All the technology development is on the same sprint cycle, and we have three-week sprints, but we also have certain things that are still annual and wonderful like funding and budgeting.

We live in a tension. People say, well, what are you going to do, what budget do you need, but at the same time, I haven’t figured everything out. So I am constantly living in that gap of what do I need to meet a certain milestone to get my project funded, and what do I need to do to go forward? Obviously, in a fully agile organization, all those things would be fluid. But then there’s financial reporting, and we would also have to be fluid too. So there are barriers to that.

For instance, the Scaled Agile Framework, which I think is a fascinating thing, has a very clear place for enterprise architecture. As Chris said, you don’t want to do too much of it in advance.  I am constantly getting the gap between how can I visualize what’s going to happen a year out and how can I give the development teams what they need for the sprint. So I am always living in that paradox.

Bellman: The Gartner Group, not too long ago, came up with the concept of emerging enterprise architecture and what we are dealing with. Enterprises don’t exist like buildings. A building is an object, but an enterprise is a group of human beings communicating with one another.

As a very famous organizational psychologist Karl Weick once pointed out, “The effective organization is garrulous, clumsy, superstitious, hypocritical, mostrous, octopoid, wandering, and grouchy.” Why? Because an organization is continually adapting, continually changing, and continually adapting to the changing business and technological landscape.

To expect anything other than that is not having a realistic view of the enterprise. It is emerging and it is a continually emerging phenomena. So in a sense, having an architecture concept I would not contest, but architecting is always worthwhile. It’s like it’s an organic phenomena, and that in order to deal with that what we can also understand and have an architecture for organic phenomena that change and rapidly adapt.

Brown: Chris, where you were going follows the lines of what great companies do, right?

There is a great book published about 30 years ago called ‘In Search of Excellence.’ If you haven’t read it, I suggest that people do. Written by Peters and Waterman, and Tom Peters has tried for ever since to try and recreate something with that magic, but one of the lessons learned was what great companies do, is something that goes simultaneous loose-tight properties. So you let somethings be very tightly controlled, and other things as are suggesting, let them flourish and see where they go before I actually box them in. So that’s a good thought.

So what do we think, as a panel, about evolving TOGAF to become an engineering methodology as well as a manufacturing methodology?

Zachman: I really think it’s a good idea.

Brown: Chris, do you have any thoughts on that?

Interesting proposal

Forde: I think it’s an interesting proposal and I think we need to look at it fairly seriously. The Open Group approach to things is, don’t lock people into a specific way of thinking, but we also advocate disciplined approach to doing things. So I would susspect that we are going to be exploring John’s proposal pretty seriously.

Brown: You mentioned in your talk that decision-making process is a precondition, the decision-making process to govern IT investments, and the question that comes in is how about other types of investments including facilities, inventory and acquisitions?

By The Open GroupForde: The wording of the presentation was very specific. Most organizations have a process or decision-making framework on an annual basis or quarterly whatever the cycles are for allocation of funding to do X, Y or Z. So the implication wasn’t that IT was the only space that it would be applied.

However, the question is how effective is that decision-making framework? In many organizations, or in a lot of organizations, the IT function is essentially an enterprise-wide activity that’s supporting the financial activities, the plant activities, these sorts of things. So you have the P&Ls from those things flowing in some way into the funding that comes to the IT organization.

The question is, when there are multiple complexities in an organization, multiple departments with independent P&Ls, they are funding IT activities in a way that may not be optimized, may or may not be optimized. For the architects, in my view, one of the avenues for success is in inserting yourself into that planning cycle and influencing,  because normally the architecture team does not have direct control over the spend, but influencing how that spend goes.

Over time gradually improving the enterprise’s ability to optimize and make effective the funding it applies for IT to support the rest of the business.

Zachman: Yeah, I was just wondering, you’ve got to make observation.

Band: I agree, I think that the battle to control shadow IT has been permanently lost. We are in a technology obsessed society. Every department wants to control some technology and even develop it to their needs. There are some controls that you do have, and we do have some, but we have core health insurance businesses that are nearly a 100 years old.

Cambia is constantly investing and acquiring new companies that are transforming healthcare. Cambia has over a 100 million customers all across the country even though our original business was a set of regional health plans.

Build relationships

You can’t possibly rationalize all of everything I want you to pay for on that thing. It is incumbent upon the architects, especially the senior ones, to build relationships with the people in these organizations and make sure everything is synergetic.

Many years ago, there was a senior architect. I asked him what he did, and he said, “Well, I’m just the glue. I go to a lot of meetings.” There are deliverables and deadlines too, but there is a part of consistently building the relationships and noticing things, so that when there is time to make a decision or someone needs something, it gets done right.

Zachman: I was in London when Bank of America got bought by NationsBank, and it was touted as the biggest banking merger in the history of the banking industry.

Actually it wasn’t a merger, it was an acquisition NationsBank acquired Bank of America and then changed the name to Bank of America. There was a London paper that was  observing that the headline you always see is, “The biggest merger in the history of the industry.” The headline you never see is, “This merger didn’t work.”

The cost of integrating the two enterprises exceeded the value of the acquisition. Therefore, we’re going to have to break this thing up in pieces and sell off the pieces as surreptitiously as possible, so nobody will notice that we buried any accounting notes someplace or other. You never see that article. You’ll only see the one about the biggest merger.

If I was the CEO and my strategy was to grow by acquisition, I would get really interested in enterprise architecture. Because you have to be able to anticipate the integration of the cost, if you want to merge two enterprises. In fact, you’re changing the scope of the enterprise. I have talked a little bit about the role on models, but you are changing the scope. As soon as you change a scope, you’re now going to be faced with an integration issue.

Therefore you have to make a choice, scrap and rework. There is no way, after the fact, to integrate parts that don’t fit together. So you’re gong to be faced a decision whether you want to scrap and rework or not. I would get really interested in enterprise architecture, because that’s what you really want to know before you make the expenditure. You acquire and obviously you’ve already blown out all the money. So now you’ve got a problem.

Once again, if I was the CEO and I want to grow by acquisition or merger acquisition, I would get really interested in enterprise architecture.

Cultural issues

Beryl Bellman: One of the big problems we are addressing here is also the cultural and political problems of organizations or enterprises. You could have the best design type of system, and if people and politics don’t agree, there are going to be these kind of conflicts.

I was involved in my favorite projects at consulting. I was involved in consulting with NCR, who was dealing with Hyundai and Samsung and trying to get them together at a conjoint project. They kept fighting with each other in terms of knowledge management, technology transfer, and knowledge transfer. My role of it was to do an architecture of that whole process.

It was called RIAC Research Institute in Computer Technology. On one side of the table, you had Hyundai and Samsung. On the other side of the table, you had NCR. They were throwing PowerPoint slides back and forth at each other. I brought up that the software we used at that time was METIS, and METIS modeled all the processes, everything that was involved.

Samsung said you just hit it with a 2×4. I used to be demonstrating it, rather than tossing out slides, here are the relationships, and be able to show that it really works. To me that was a real demonstration that I can even overcome some of the politics and cultural differences within enterprises.

Brown: I want to give one more question. I think this is more of a concern that we have raised in some people’s minds today, which is, we are talking about all these different frameworks and ontologies, and so there is a first question.

The second one is probably the key one that we are looking at, but it asks what does each of the frameworks lack, what are the key elements that are missing, because that leads on to the second question that says, isn’t needing to understand old enterprise architecture frameworks is not a complex exercise for a practitioner?

Band: My job is not about understanding frameworks. I have been doing enterprises solution architecture in HP at a standard and diversified financial services company and now at health insurance and health solutions company out for quite a while, and it’s really about communicating and understanding in a way that’s useful to your stakeholders.

The frameworks about creating shared understanding of what we have and where are we going to go, and the frameworks are just a set of tools that you have in your toolbox that most people don’t understand.

So the idea is not to understand everything but to get a set of tools, just like a mechanic would, that you carry around that you use all the time. For instance, there are certain types of ArchiMate views that I use when I am in a group. I will draw an ArchiMate business process view with application service use of the same. What are the business processes you need to be and what are the exposed application behaviors that they need to consume?

I had that discussion with people on the business who are in IT, and we drove those diagrams. That’s a useful tool, it works for me, it works for the people around me, it works in my culture, but there is no understanding over frameworks unless that’s your field of study. They are all missing the exact thing you need for a particular interaction, but most likely there is something in there that you can base the next critical interaction on.

Six questions

Zachman: I spent most of my life thinking about my frameworks. There are six questions you have to answer to have a complete description of whatever it is, what I will describe, what, how, where, who, and why. So that’s complete.

The philosophers have established six transformations interestingly enough, the transfer of idea into an instantiation, so that’s a complete set, and I did not invent either one of these, so the six interrogatives. They have the six stages of transformation and that framework has to, by definition, accommodate any factor that’s relevant to the existence of the object of the enterprise.  Therefore any fact has to be classifiable in that structure.

My framework is complete in that regard. For many years, I would have been reluctant to make a categorical statement, but we exercised this, and there is no anomaly. I can’t find an anomaly. Therefore I have a high level of confidence that you can classify any fact in that context.

There is one periodic table. There are n different compound manufacturing processes. You can manufacture anything out of the periodic table. That metaphor is really helpful. There’s one enterprise architecture framework ontology. I happened to stumble across, by accident, the ontology for classifying all of the facts relevant to an enterprise.

I wish I could tell you that I was so smart and understood all of these things at the beginning, but I knew nothing about this, I just happened to stumble across it. The framework fell on my desk one day and I saw the pattern. All I did was I put enterprise names on the same pattern for descriptive representation of anything. You’ve heard me tell quite a bit of the story this afternoon. In terms of completeness I think my framework is complete. I can find no anomalies and you can classify anything relative to that framework.

And I agree with Iver, that there are n different tools you might want to use. You don’t have to know everything about every framework. One thing is, whatever the tool is that you need to deal with and out of the context of the periodic table metaphor, the ontological construct of The Zachman Framework, you can accommodate whatever artifacts the tool creates.

You don’t have to analyze every tool, whatever tool is necessary, if you want to do with business architecture, you can create whatever the business architecture manifestation is. If you want to know what DoDAF is, you can create the DoDAF artifacts. You can create any composite, and you can create any compound from the periodic table. It’s the same idea.

I wouldn’t spend my life trying to understand all these frameworks. You have to operate the enterprise, you have to manage the enterprise and whatever the tool is, it’s required to do whatever it is that you need to do and there is something good about everything and nothing necessarily does everything.

So use the tool that’s appropriate and then you can create whatever the composite constructs are required by that tool out of the primitive components of the framework. I wouldn’t try to understand all the frameworks.

What’s missing

Forde: On a daily basis there is a line of people at these conferences coming to tell me what’s missing from TOGAF. Recently we conducted a survey through the Association of Enterprise Architects about what people needed to see. Basically the stuff came back pretty much, please give us more guidance that’s specific to my situation, a recipe for how to solve world hunger, or something like that. We are not in the role of providing that level of prescriptive detail.

The value side of the equation is the flexibility of the framework to a certain degree to allow many different industries and many different practitioners drive value for their business out of using that particular tool.

So some people will find value in the content metamodel in the TOGAF Framework and the other components of it, but if you are not happy with that, if it doesn’t meet your need, flip over to The Zachman Framework or vice versa.

John made it very clear earlier that the value in the framework that he has built throughout his career and has been used repeatedly around the world is its rigor, it’s comprehensiveness, but he made very clear, it’s not a method. There is nothing in there to tell you how to go do it.

So you could criticize The Zachman Framework for a lack of method or you could spend your time talking about the value of it as a very useful tool to get X, Y, and Z done.

From a practitioner’s standpoint, what one practitioner does is interesting in a value, but if you have a practice between 200 and 400 architects, you don’t want everybody running around like a loose cannon doing it their way, in my opinion. As a practice manager or leader you need something that makes those resources very, very effective. And when you are in a practice of that size, you probably have a handful of people trying to figure out how the frameworks come together, but most of the practitioners are tasked with taking what the organization says is their best practice and executing on it.

We are looking at improving the level of guidance provided by the TOGAF material, the standard and guidance about how to do specific scenarios.

For example, how to jumpstart an architecture practice, how to build a secure architecture, how to do business architecture well? Those are the kinds of things that we have had feedback on and we are working on around that particular specification.

Brown: So if you are employed by the US Department of Defense you would be required to use DoDAF, if you are an enterprise architect, because of the views it provides. But people like Terri Blevins that did work in the DoD many years, used TOGAF to populate DoDAF. It’s a method, and the method is the great strength.

If you want to have more information on that, there are a number of white papers on our website about using TOGAF with DoDAF, TOGAF with COBIT, TOGAF with Zachman, TOGAF with everything else.

Forde: TOGAF with frameworks, TOGAF with buy in, the thing to look at is the ecosystem of information around these frameworks is where the value proposition really is. If you are trying to bootstrap your standards practice inside, the framework is of interest, but applied use, driving to the value proposition for your business function is the critical area to focus on.

The panel, which examined the synergy among the major EA frameworks, consists of moderator Allen Brown, President and Chief Executive Officer, The Open Group; Iver Bank, an Enterprise Architect, Cambia Health Solutions; Dr. Beryl Bellman, Academic Director, FEAC Institute; John Zachman, Chairman and CEO of Zachman International, and originator of the Zachman Framework; and Chris Forde, General Manager, Asia and Pacific Region and Vice President, Enterprise Architecture, The Open Group.

Transcript available here.

Join the conversation @theopengroup #ogchat

You may also be interested in:

 

Leave a comment

Filed under ArchiMate®, big data, Business Architecture, Cloud, Data management, Enterprise Architecture, Enterprise Transformation, Standards, TOGAF®, Uncategorized

A World Without IT4IT: Why It’s Time to Run IT Like a Business

By Dave Lounsbury, CTO, The Open Group

IT departments today are under enormous pressure. In the digital world, businesses have become dependent on IT to help them remain competitive. However, traditional IT departments have their roots in skills such as development or operations and have not been set up to handle a business and technology environment that is trying to rapidly adapt to a constantly changing marketplace. As a result, many IT departments today may be headed for a crisis.

At one time, IT departments led technology adoption in support of business. Once a new technology was created—departmental servers, for instance—it took a relatively long time before businesses took advantage of it and even longer before they became dependent on the technology. But once a business did adopt the technology, it became subject to business rules—expectations and parameters for reliability, maintenance and upgrades that kept the technology up to date and allowed the business it supported to keep up with the market.

As IT became more entrenched in organizations throughout the 1980s and 1990s, IT systems increased in size and scope as technology companies fought to keep pace with market forces. In large enterprises, in particular, IT’s function became to maintain large infrastructures, requiring small armies of IT workers to sustain them.

A number of forces have combined to change all that. Today, most businesses do their business operations digitally—what Constellation Research analyst Andy Mulholland calls “Front Office Digital Business.” Technology-as-a-service models have changed how the technologies and applications are delivered and supported, with support and upgrades coming from outsourced vendors, not in-house staff. With Cloud models, an IT department may not even be necessary. Entrepreneurs can spin up a company with a swipe of a credit card and have all the technology they need at their fingertips, hosted remotely in the Cloud.

The Gulf between IT and Business

Although the gap between IT and business is closing, the gulf in how IT is run still remains. In structure, most IT departments today remain close to their technology roots. This is, in part, because IT departments are still run by technologists and engineers whose primary skills lie in the challenge (and excitement) of creating new technologies. Not every skilled engineer makes a good businessperson, but in most organizations, people who are good at their jobs often get promoted into management whether or not they are ready to manage. The Peter Principle is a problem that hinders many organizations, not just IT departments.

What has happened is that IT departments have not traditionally been run as if they were a business. Good business models for how IT should be run have been piecemeal or slow to develop—despite IT’s role in how the rest of the business is run. Although some standards have been developed as guides for how different parts of IT should be run (COBIT for governance, ITIL for service management, TOGAF®, an Open Group standard, for architecture), no overarching standard has been developed that encompasses how to holistically manage all of IT, from systems administration to development to management through governance and, of course, staffing. For all its advances, IT has yet to become a well-oiled business machine.

The business—and technological—climate today is not the same as it was when companies took three years to do a software upgrade. Everything in today’s climate happens nearly instantaneously. “Convergence” technologies like Cloud Computing, Big Data, social media, mobile and the Internet of Things are changing the nature of IT. New technical skills and methodologies are emerging every day, as well. Although languages such as Java or C may remain the top programming languages, new languages like Pig or Hive are emerging everyday, as are new approaches to development, such as Scrum, Agile or DevOps.

The Consequences of IT Business as Usual

With these various forces facing IT, departments will either need to change and adopt a model where IT is managed more effectively or departments may face some impending chaos that ends up hindering their organizations.

Without an effective management model for IT, companies won’t be able to mobilize quickly for a digital age. Even something as simple as an inability to utilize data could result in problems such as investing in a product prototype that customers aren’t interested in. Those are mistakes most companies can’t afford to make these days.

Having an umbrella view of what all of IT does also allows the department to make better decisions. With technology and development trends changing so quickly, how do you know what will fit your organization’s business goals? You want to take advantage of the trends or technologies that make sense for the company and leave behind those that don’t.

For example, in DevOps, one of the core concepts is to bring the development phase into closer alignment with releasing and operating the software. You need to know your business’s operating model to determine whether this approach will actually work or not. Having a sense of that also allows IT to make decisions about whether it’s wise to invest in training or hiring staff skilled in those methods or buying new technologies that will allow you to adopt the model.

Not having that management view can leave companies subject to the whims of technological evolution and also to current IT fads. If you don’t know what’s valuable to your business, you run the risk of chasing every new fad that comes along. There’s nothing worse—as the IT guy—than being the person who comes to the management meeting each month saying you’re trying yet another new approach to solve a problem that never seems to get solved. Business people won’t respond to that and will wonder if you know what you’re doing. IT needs to be decisive and choose wisely.

These issues not only affect the IT department but to trickle up to business operations. Ineffective IT shops will not know when to invest in the correct technologies, and they may miss out on working with new technologies that could benefit the business. Without a framework to plan how technology fits into the business, you could end up in the position of having great IT bows and arrows but when you walk out into the competitive world, you get machine-gunned.

The other side is cost and efficiency—if the entire IT shop isn’t running smoothly throughout then you end up spending too much money on problems, which in turn takes money away from other parts of the business that can keep the organization competitive. Failing to manage IT can lead to competitive loss across numerous areas within a business.

A New Business Model

To help prevent the consequences that may result if IT isn’t run more like a business, industry leaders such as Accenture; Achmea; AT&T; HP IT; ING Bank; Munich RE; PwC; Royal Dutch Shell; and University of South Florida, recently formed a consortium to address how to better run the business of IT. With billions of dollars invested in IT each year, these companies realized their investments must be made wisely and show governable results in order succeed.

The result of their efforts is The Open Group IT4IT™ Forum, which released a Snapshot of its proposed Reference Architecture for running IT more like a business this past November. The Reference Architecture is meant to serve as an operating model for IT, providing the “missing link” that previous IT-function specific models have failed to address. The model allows IT to achieve the same level of business, discipline, predictability and efficiency as other business functions.

The Snapshot includes a four-phase Value Chain for IT that provides both an operating model for an IT business and outlines how value can be added at every stage of the IT process. In addition to providing suggested best practices for delivery, the Snapshot includes technical models for the IT tools that organizations can use, whether for systems monitoring, release monitoring or IT point solutions. Providing guidance around IT tools will allow these tools to become more interoperable so that they can exchange information at the right place at the right time. In addition, it will allow for better control of information flow between various parts of the business through the IT shop, thus saving IT departments the time and hassle of aggregating tools or cobbling together their own tools and solutions. Staffing guidance models are also included in the Reference Architecture.

Why IT4IT now? Digitalization cannot be held back, particularly in an era of Cloud, Big Data and an impending Internet of Things. An IT4IT Reference Architecture provides more than just best practices for IT—it puts IT in the context of a business model that allows IT to be a contributing part of an enterprise, providing a roadmap for digital businesses to compete and thrive for years to come.

Join the conversation! @theopengroup #ogchat

By The Open GroupDavid is Chief Technical Officer (CTO) and Vice President, Services for The Open Group. As CTO, he ensures that The Open Group’s people and IT resources are effectively used to implement the organization’s strategy and mission.  As VP of Services, David leads the delivery of The Open Group’s proven collaboration processes for collaboration and certification both within the organization and in support of third-party consortia.

David holds a degree in Electrical Engineering from Worcester Polytechnic Institute, and is holder of three U.S. patents.

1 Comment

Filed under Cloud, digital technologies, Enterprise Transformation, Internet of Things, IT, IT4IT, TOGAF, TOGAF®

Using the ArchiMate® Language to Model TOGAF® Architectures

By William Estrem, President, Metaplexity Associates LLC, Serge Thorn, Associate, Metaplexity Associates LLC, and Sonia Gonzalez, Architecture and ArchiMate® Forums Director, The Open Group

If you are using the TOGAF® standard in your organization to guide the process of developing Enterprise Architectures, you could consider using the ArchiMate® language. ArchiMate, an Open Group standard, is a modeling language that is designed from the ground up to support modeling Enterprise Architectures and that can be very successfully applied for developing architecture descriptions that are well aligned with your organization’s strategy

The TOGAF standard is a framework for creating an Enterprise Architecture capability in your organization. The TOGAF Architecture Development Method (ADM) is a central feature of the TOGAF standard. The ADM cycle describes an incremental and iterative method for designing Business, Data, Applications, and Technology architectures. It progresses from high-level concept diagrams, to detailed domain architectures, all the way to the development of solution architectures, architecture roadmaps and implementation plans.

The ArchiMate® language is an Open Group standard that provides an Enterprise Architecture modeling language. The Archimate® language views the model as a set of layers (Business, Application, and Technology) as well as some specialized extensions (Motivation, and Implementation and Migration).

The Open Group Architecture and ArchiMate Forums have established a joint project known as Project Harmony that is focused on improving how the TOGAF and ArchiMate standards can be used together to create effective architecture descriptions.

Project Harmony has now published its first deliverables, a series of white papers that deliver guidance on the combined use of the TOGAF® Enterprise Architecture (EA) framework and the ArchiMate® EA modeling language. A Practitioner’s Guide summarizes the key findings of three in-depth white papers, which analyze the standards in terms of terminology, viewpoints, and metamodels, and provide recommendations on how they can be best used together.

The full series is entitled TOGAF® Framework and ArchiMate® Modeling Language Harmonization. The four white papers are:

  • A Practitioner’s Guide to Using the TOGAF® Framework and the ArchiMate® Language (W14C)
  • Content Metamodel Harmonization: Entitles and Relationships (W14D)
  • Glossaries Comparison (W14A)
  • Viewpoints Mapping (W14B)

All four can be downloaded from here (select the ZIP file link).

The Open Group has recently hosted a webinar highlighting how you can use TOGAF and ArchiMate together more effectively, to view the webinar visit: https://www2.opengroup.org/ogsys/catalog/D120

By William Estrem, Serge Thorn and Sonia GonzalezWilliam Estrem, President of Metaplexity Associates LLC, is currently serving as the chairman of Project Harmony. He has been involved with the development of the TOGAF standard since 1994. He is a former chairman of the Architecture Forum and served a two year term on the Open Group Board of Governors. Metaplexity Associates is a Gold Level member of The Open Group. It is a U.S. based education and consulting firm that offers services related to Enterprise Architecture. Metaplexity Associates offers accredited TOGAF courses.

 

By William Estrem, Serge Thorn and Sonia GonzalezSerge Thorn was CIO of Architecting the Enterprise, now an Associate of Metaplexity Associates LLC. He has worked in the IT Industry and Consultancy (Banking-Finance, Biotechnology-Pharma/Chemical, Telcos), for over 30 years, in a variety of roles, which include: Development and Systems Design, Project Management, Business Analysis, IT Operations, IT Management, IT Strategy, Research and Innovation, IT Governance, Project and Portfolio Management, Enterprise Architecture and Service Management (ITIL), Products Development, Coaching-Mentoring. For 10 years, he has been Chairman of the itSMF (IT Service Management Forum) Swiss chapter, involved with The Open Group Architecture and ArchiMate Forums.

 

By William Estrem, Serge Thorn and Sonia GonzalezSonia Gonzalez is The Open Group Forum Director for the Architecture and ArchiMate® Forums. Sonia has been also a trainer and consultant in the areas of business innovation, business process modeling, and Enterprise Architecture applying TOGAF® and ArchiMate. In this position, she is involved in the development and evolution of current and future EA standards. She is TOGAF® 9 Certified and ArchiMate® 2 Certified, and has been a trainer for an accredited training course provider and developed workshops and EA consultancy projects using the TOGAF standard as a reference framework and the ArchiMate standard as a modeling language.

 

 

Leave a comment

Filed under ArchiMate®, Enterprise Architecture, Professional Development, Standards, TOGAF®, Uncategorized

“Lean” Enterprise Architecture powered by TOGAF® 9.1

By Krish Ayyar, Managing Principal, Martin-McDougall Technologies

Enterprise Architecture is there to solve Enterprise level problems. A typical problem scenario could be something like “A large Mining and Resources company uses many sensors to collect and feed engineering data back to the central control room for monitoring their assets. These sensors are from multiple vendors and they use proprietary networking technologies and also data formats. There are interoperability issues. The company would like to improve the manageability and availability of these systems by exploring solutions around the emerging Internet Of Things (IoT) technology”.

There are many ways to solve Enterprise level problems. A typical approach might be to purchase a packaged software or develop bespoke solutions and sponsor an IT project to implement it.

So, what is special about Enterprise Architecture? EA is the only approach that puts you in the driver seat when it comes to orderly evolution of your enterprise’s business and information systems landscape.

How do we go about doing this?

The best way is to develop Enterprise Architecture in a short engagement cycle of say 4 to 6 weeks through the use of TOGAF® 9.1 method. If you think about it, the TOGAF® ADM basically covers 4 “Meta” phases. They are namely: Preparing and Setting the Architecture Vision, Blueprinting the Target State, Solutioning & Road Mapping, Governance and Change Management. The key to a short engagement cycle is in not doing those activities which are already done elsewhere in the organisation but linking with them. This includes Business Strategy, IT Strategy, Detailed Implementation Planning and Governance. This might mean “Piggy Backing” on PMO processes and extending them to include Enterprise Architecture.

As part of “Preparing and Setting the Architecture Vision”, we identify the Business Goals, Objectives and Drivers related to this problem scenario. For instance in this case, let us say we ran business scenario workshops and documented the CFO’s statement that the overall cost of remotely monitoring and supporting Engineering Systems must come down. We now elicit the concerns and requirements related to business and information systems from the stakeholders. In this case, the CEO has felt that the company needs new capabilities for monitoring devices anytime, anywhere.

As part of the “Governance and Change Management”, we look at emerging Business and Technology trends. Internet of Things or “IoT” is trending as the technology which has the ability to connect sensors to the internet for effective control. At this juncture, we should do some research and collect information about the Product and Technology Solutions that could deliver the new or enhanced capabilities. Major vendors such as SAP, Cisco and Microsoft have IoT Solutions in their offerings. These solutions are capable of enabling remote support using mobile devices streaming data in the cloud, network infrastructure for transporting the data using open standards, Cloud Computing, sensor connectivity to Wifi / Internet etc.,

Next, as part of “Blueprinting the Target State””, we model the Current and Target state Business Capabilities and Information System Services and Functionalities. We can do this very quickly by selecting the relevant TOGAF® 9.1 Artifacts to address the concerns and requirements. These are grouped by Architecture Domains within the TOGAF® 9.1 document. We then identify the Gaps. In our example, these could be new support capabilities using IoT.

Now as part of “Solutioning and Road Mapping”, we roadmap the gaps in a practical way to deliver business value. We could effectively use the TOGAF® 9.1 “Business Value Assessment” technique to achieve this. This will help us to realise the business goals and objectives as per business priorities delivered by the solution components. For example, reducing the cost of remotely monitoring and supporting engineering systems could be realised by solutions that enable remote monitoring and support using mobile devices streaming data in the cloud.

Of course, architecture work is not complete until the solution is architected from a design perspective to manage the product and technology complexities during implementation. There is also the need for Architecture Governance to ensure that it does not go pear-shaped during implementation and operation.

This does not seem to be a lot of effort, does it? In fact, some sort of conceptualisation happens in all major projects prior to the business case leading up to funding approval. When it is done by people who do not have the right mix of strategy, project management, solutioning and consulting skills, it becomes a mere “tick in the box” exercise. Why not adopt this structured approach of Enterprise Architecture powered by TOGAF® 9.1 and reap the rewards?

By Krish Ayyar, Martin-McDougall TechnologiesKrish Ayyar is an accomplished Enterprise Architecture Practitioner with well over 10 years consulting and teaching Enterprise Architecture internationally. He is a sought after Trainer of TOGAF® 9.1 Level 2 and Archimate® 2.1 Level 2 Certification Courses with teaching experience for over 5 years in Australia, New Zealand, China, Japan, India, USA and Canada.  His experience includes a background in management consulting with Strategy and Business Transformation consulting, Enterprise Architecture consulting and Enterprise Architect functional roles in Australia, Singapore, Malaysia and USA for over 15 years. Krish is an active contributor to The Open Group Architecture Forum activities through membership of his own consulting company based in Sydney, Australia.  Krish has been a presenter in Open Group conferences at Boston, Washington D.C and Sydney. He is currently Vice Chair of the Certification Standing Committee of the Architecture Forum.

 

 

Leave a comment

Filed under ArchiMate®, Business Architecture, Certifications, Enterprise Architecture, Professional Development, Standards, TOGAF®, Uncategorized

The Open Group San Diego 2015 – Day Two Highlights

By Loren K. Baynes, Director, Global Marketing Communications, The Open Group

Day two, February 3, kicked off with a presentation by Allen Brown, President and CEO of The Open Group, “What I Don’t Need from Business Architecture… and What I Do”.

Allen began with a brief history of The Open Group vision of Boundaryless Information Flow™, which enables the break down of barriers to cross-functional organization when information is held in siloed parts. Allen and team used the word “boundaryless” that was started by Jack Welch in 2002 with the phrase “Boundaryless Organization”. This approach focused on thinking and acting, not technical. “Boundaryless” does not mean there are no boundaries, it means that boundaries are permeable to enable business.

Allen also discussed brand actualization, and that organizations wishing to achieve brand recognition such as Nike and Apple must be aware of the customer journey. The journey entails awareness, evaluation, joining, participation, renewal and advocacy. The organization needs to learn more about the people so as not to segment, since people are not “one size fits all”. Business Architecture helps with understanding the customer journey.

By Loren K. Baynes

Business Architecture is part of Enterprise Architecture, he continued. A greater focus on the “what”, including strategic themes, capabilities and interdependencies, can add a lot of value. It is applicable to the business of government as well as to the business of “businesses” and non-profit organizations.

John Zachman, Founder & Chairman, Zachman International and Executive Director of FEAC Institute, presented “The Zachman Framework and How It Complements TOGAF® and Other Frameworks”. John stated the biggest problem is change. The two reasons to do architecture are complexity and change. A person or organization needs to understand and describe the problem before solving it.

“All I did was, I saw the pattern of the structure of the descriptive representations for airplanes, buildings, locomotives and computers, and I put enterprise names on the same patterns,” he said. “Now you have the Zachman Framework, which basically is Architecture for Enterprises. It is Architecture for every other object known to human kind.” Thus the Zachman Framework was born.

According to John, what his Framework is ultimately intended for is describing a complex object, an Enterprise. In that sense, the Zachman Framework is the ontology for Enterprise Architecture, he stated. What it doesn’t do is tell you how to do Enterprise Architecture.

“My framework is just the definition and structure of the descriptive representation for enterprises,” he said. That’s where methodologies, such as TOGAF®, an Open Group standard, or other methodological frameworks come in. It’s not Zachman OR TOGAF®, it’s TOGAF® AND Zachman.

By Loren K. BaynesJohn Zachman

Allen and John then participated in a Q&A session. Both are very passionate about professionalizing the architecture profession. Allen and John agreed there should be a sense of urgency for architecture to keep up with the rapid evolution of technology.

The plenary continued with Chris Forde, GM APAC Region and VP, Enterprise Architecture, The Open Group on “The Value of TOGAF® Architecture Development Method (ADM) and Open Systems Architecture”. Chris was presenting on behalf of Terry Blevins, Fellow of The Open Group, who could not attend.

Chris said, “Enterprise Architecture is a constant journey.” The degree of complexity of organizations or objects (such as airplanes) is enormous. Architecture is a means to an end. ADM is the core of TOGAF.

Enterprise Architecture (EA) is nothing but a paperweight if there are no plans in place to use it to make decisions. Supporting decision-making is the key reason to produce an Enterprise Architecture. Chris noted sound decisions sometimes need to be made without all of the information required. EA is a management tool, not a technology tool.

Allen Brown chaired a panel, “Synergy of EA Frameworks”, with panelists Chris Forde, John Zachman, Dr. Beryl Bellman, Academic Director, FEAC Institute, and Iver Band, Enterprise Architect, Cambia Health Solutions.

Iver began the panel session by discussing ArchiMate®, an Open Group standard, which is a language for building understanding and communicating and managing change.

One of the questions the panel addressed was how does EA take advantage of emerging technologies such as mobile, big data and cloud? The “as designed” logic can be implemented in any technology. Consideration should also be given to synergy among the different architectures. EA as a management discipline helps people to ask the right questions about activities and technologies to mitigate risk, take advantage of the situation and/or decide whether or not to deploy the strategies and tactics. The idea is not to understand everything and every framework, but to get the right set of tools for interaction and navigation.

In the afternoon, tracks consisted of Risk, Dependability and Trusted Technology, Open Platform 3.0™, Architecture Frameworks and EA and Business Transformation. Presenters were from a wide range of organizations including HP, Tata Consulting Services (India), Wipro, IBM, Symantic and Arca Success Group.

A networking reception was held at the Birch Aquarium, Scripps Institution of Oceanography. Attendees enjoyed a scrumptious dinner and experienced the wonders of ocean and marine life.

A very special thank you goes to our San Diego 2015 sponsors and exhibitors: BiZZdesign, Corso, FEAC Institute, AEA, Good E-learning, SimpliLearn and Van Haren Publishing.

Most of our plenary proceedings are available at Livestream.com/opengroup

Please join the conversation – @theopengroup #ogSAN

By Loren K. BaynesLoren K. Baynes, Director, Global Marketing Communications, joined The Open Group in 2013 and spearheads corporate marketing initiatives, primarily the website, blog and media relations. Loren has over 20 years experience in brand marketing and public relations and, prior to The Open Group, was with The Walt Disney Company for over 10 years. Loren holds a Bachelor of Business Administration from Texas A&M University. She is based in the US.

 

Leave a comment

Filed under Business Architecture, Conference, Enterprise Architecture, Enterprise Transformation, Internet of Things, Interoperability, Open Platform 3.0, Professional Development, Standards, TOGAF®, Value Chain

The Open Group San Diego 2015 – Day One Highlights

By Loren K. Baynes, Director, Global Marketing Communications, The Open Group

The Open Group San Diego 2015, with over 200 guests in attendance, had a powerful start on Monday, February 2 with a presentation by Dawn Meyerriecks, CIA Deputy Director for Science and Technology and Emeritus of The Open Group.

Dawn’s presentation, entitled “Emerging Tech Trends: The Role of Government”, focused on the US government, but she emphasized that global reach is necessary as are international relationships. US investment in R&D and basic research is accelerating. She continued, the government is great at R&D but not necessarily bringing it to market. Furthermore, as physical and virtual converge (i.e. Internet of Things), this fuels the state of IT. The US is well ahead of other countries in R&D, but China and Japan are increasing their spend, along with other markets. Discussions about supply chain, dependability, platforms, mobility and architectural framework are also required.

Big data analytics are key as is the access to analytics and the ability to exploit it to have market growth. The government works with partners on many levels. Leading experts from academia, governments, and industry collaborate to solve hard problems in big data analytics, including the impacts on life such as trying to predict societal unrest. The complex technologies focus must utilize incisive analysis, safe and secure operations and smart collection.

By The Open GroupDawn Meyerriecks

When Allen Brown, President and CEO of The Open Group, introduced Dawn, he mentioned her integral role in launching the Association of Enterprise Architects (AEA), formerly AOGEA, in 2007 which initially had 700 members. AEA now has over 40,000 members and is recognized worldwide as a professional association.

Dawn’s presentation was followed by a Q&A session with Allen who further addressed supply chain, ethical use of data, cloud systems and investment in cybersecurity. Allen emphasized that The Open Trusted Technology Provider™ Standard (O-TTPS) Accreditation Program is in place but there needs to be a greater demand.

Next on the agenda was the The Open Group overview and Forum Highlights presented by Allen Brown. The Open Group has 488 member organizations signed in 40 countries such as Australia, Czech Republic, Japan, Nigeria, Philippines and United Arab Emirates. In 2014, The Open Group signed 93 new membership agreements in 22 countries.

Allen presented updates on all The Open Group Forums: ArchiMate®, Architecture, DirectNet®, EMMM, Enterprise Management, FACE®, Healthcare, IT4IT™, Open Platform 3.0™, Open Trusted Technology, Security. Highlights included:

  • ArchiMate® Forum – The Open Group now sponsors the Archi tool, a free open source tool; recently published TOGAF® Framework/ArchiMate® Modeling Language Harmonization guide
  • Architecture Forum – TOGAF® 9 reached 40,000 certifications; 75,000 TOGAF publications download in 166 countries; TOGAF books sales reached 11,000
  • Healthcare Forum – first round analysis submission for Federal Health Information Model (FHIM) was very well-accepted; white paper in development
  • The Open Group IT4IT™ Forum – launched in October 2014
  • Open Platform 3.0™ Forum – snapshot 2 in development; produced two Internet of Things (IoT) standards in 2014; relaunching UDEF in 2015
  • Security Forum – increasing activities with organizations in India

The plenary continued with a joint presentation by Dr. Ron Ross, Fellow of National Institute of Standards and Technology (NIST) and Mary Ann Davidson, Chief Security Officer, Oracle and entitled “Cybersecurity Standards: Finding the Right Balance for Securing Your Enterprise”.

Dr. Ross stated the world is developing the most complicated IT infrastructure ever. Critical missions and business functions are at risk – affecting national economic security interests of the US. Companies throughout the globe are trying to make systems secure, but there are challenges when getting to the engineering aspect. Assurance, trustworthiness, resiliency is the world we want to build. “Building stronger, more resilient systems requires effective security standards for software assurance, systems security engineering, supply chain risk management.” It is critical to focus on the architecture and engineering. The essential partnership is government, academia and industry.

Mary Ann posed the question “why cybersecurity standards?” with the answer being that standards help ensure technical correctness, interoperability, trustworthiness and best practices. In her view, the standards ecosystem consists of standards makers, reviewers, mandaters, implementers, certifiers, weaponizers (i.e. via regulatory capture). She stated the “Four Ps of Benevolent Standards” are problem statement, precise language and scope, pragmatic solutions and prescriptive minimization. “Buyers and practitioners must work hand in hand; standards and practice should be neck and neck, not miles apart.”

The plenary culminated with the Cybersecurity Panel. Dave Lounsbury, CTO, The Open Group, moderated the panel. Panelists were Edna Conway, Chief Security Officer for Global Supply Chain, Cisco; Mary Ann Mezzapelle, America CTO for Enterprise Security Services, HP, Jim Hietala, VP Security, The Open Group, Rance Delong, Security and High Assurance Systems, Santa Clara University. They all agreed the key to Security is to learn the risks, vulnerabilities and what can you control. Technology and controls are out there but organizations need to implement them effectively. Also, collaboration is important among public, private, industry and supply chain, and people, processes and technology.

By The Open Group

Rance Delong, Jim Hietala, Edna Conway, Mary Ann Mezzapelle, Dave Lounsbury

The afternoon featured tracks Risk, Dependability and Trusted Technology; IT4IT™; EA Practice and Professional Development. One of the sessions “Services Model Backbone – the IT4IT™ Nerve System” was presented by Lars Rossen, Distinguished Technologist and Chief Architect, IT4IT Initiative, HP.

In the evening, The Open Group hosted a lovely reception on the outside terrace at the Westin Gaslamp.

Most plenary sessions are available via: Livestream.com/opengroup

Please join the conversation – @theopengroup #ogSAN

By Loren K. BaynesLoren K. Baynes, Director, Global Marketing Communications, joined The Open Group in 2013 and spearheads corporate marketing initiatives, primarily the website, blog and media relations. Loren has over 20 years experience in brand marketing and public relations and, prior to The Open Group, was with The Walt Disney Company for over 10 years. Loren holds a Bachelor of Business Administration from Texas A&M University. She is based in the US.

 

 

 

 

 

 

 

 

3 Comments

Filed under Business Architecture, Conference, Cybersecurity, Enterprise Architecture, Enterprise Transformation, O-TTF, Professional Development, Security, Standards

Professional Training Trends (Part Two): A Q&A with Chris Armstrong, Armstrong Process Group

By The Open Group

This is part two in a two part series.

Professional development and training is a perpetually hot topic within the technology industry. After all, who doesn’t want to succeed at their job and perform better?

Ongoing education and training is particularly important for technology professionals who are already in the field. With new tech trends, programming languages and methodologies continuously popping up, most professionals can’t afford not to keep their skill sets up to date these days.

The Open Group member Chris Armstrong is well-versed in the obstacles that technology professionals face to do their jobs. President of Armstrong Process Group, Inc. (APG), Armstrong and his firm provide continuing education and certification programs for technology professionals and Enterprise Architects covering all aspects of the enterprise development lifecycle. We recently spoke with Armstrong about the needs of Architecture professionals and the skills and tools he thinks are necessary to do the job effectively today.

What are some of the tools that EAs can be using to do architecture right now?

There’s quite a bit out there. I’m kind of developing a perspective on how to lay them out across the landscape a bit better. I think there are two general classes of EA tools based on requirements, which is not necessarily the same as what is offered by commercial or open source solutions.

When you take a look at the EA Capability model and the value chain, the first two parts of it have to do with understanding and analyzing what’s going on in an enterprise. Those can be effectively implemented by what I call Enterprise Architecture content management tools, or EACM. Most of the modeling tools would fall within that categorization. Tools that we use? There’s Sparx Enterprise Architect. It’s a very effective modeling tool that covers all aspects of the architecture landscape top-to-bottom, left-to-right and it’s very affordable. Consequently, it’s one of the most popular tools in the world—I think there are upwards of 300,000 licenses active right now. There are lots of other modeling tools as well.

A lot of people find the price point for Sparx Enterprise Architect so appealing that when people go into an investment and it’s only $5K, $10K, or $15K, instead of $100K or $250K, find it’s a great way to get into coming to grips with what it means to really build models. It really helps you build those fundamental modeling skills, which are best learned via on-the-job experience in your real business domain, without having to mortgage the farm.

Then there’s the other part of it, and this is where I think there needs to be a shift in emphasis to some extent. A lot of times the architect community gets caught up in modeling. We’ve been modeling for decades—modeling is not a new thing. Despite that—and this is just an anecdotal observation—the level of formal, rigorous modeling, at least in our client base in the U.S. market, is still very low. There are lots of Fortune 1000 organizations that have not made investments in some of these solutions yet, or are fractured or not well-unified. As a profession, we have a big history of modeling and I’m a big fan of that, but it sometimes seems a bit self-serving to some extent, in that a lot of times the people we model for are ourselves. It’s all good from an engineering perspective—helps us frame stuff up, produce views of our content that are meaningful to other stakeholders. But there’s a real missed opportunity in making those assets available and useful to the rest of the organization. Because if you build a model, irrespective of how good and relevant and pertinent it is, if nobody knows about it and nobody can use it to make good decisions or can’t use it to accelerate their project, there’s some legitimacy to the question of “So how much value is this really adding?” I see a chasm between the production of Enterprise Architecture content and the ease of accessing and using that content throughout the enterprise. The consumer market for Enterprise Architecture is much larger than the provider community.

But that’s a big part of the problem, which is why I mentioned cross-training earlier–most enterprises don’t have the self-awareness that they’ve made some investment in Enterprise Architecture and then often ironically end up making redundant, duplicative investments in repositories to keep track of inventories of things that EA is already doing or could already be doing. Making EA content as easily accessible to the enterprise as going to Google and searching for it would be a monumental improvement. One of the big barriers to re-use is finding if something useful has already been created, and there’s a lot of opportunity to deliver better capability through tooling to all of the consumers throughout an enterprise.

If we move a bit further along the EA value chain to what we call “Decide and Respond,” that’s a really good place for a different class of tools. Even though there are modeling tool vendors that try to do it, we need a second class of tools for EA Lifecycle Management (EALM), which is really getting into the understanding of “architecture-in-motion”. Once architecture content has been described as the current and future state, the real $64,000 question is how do we get there? How do we build a roadmap? How do we distribute the requirements of that roadmap across multiple projects and tie that to the strategic business decisions and critical assets over time? Then there’s how do I operate all of this stuff once I build it? That’s another part of lifecycle management—not just how do I get to this future state target architecture, but how do I continue to operate and evolve it incrementally and iteratively over time?

There are some tools that are emerging in the lifecycle management space and one of them is another product we partner with—that’s a solution from HP called Enterprise Maps. From our perspective it meets all the key requirements of what we consider enterprise architecture lifecycle management.

What tools do you recommend EAs use to enhance their skillsets?

Getting back to modeling—that’s a really good place to start as it relates to elevating the rigor of architecture. People are used to drawing pictures with something like Visio to graphically represent ”here’s how the business is arranged” or “here’s how the applications landscape looks,” but there’s a big difference in transitioning how to think about building a model. Because drawing a picture and building a model are not the same thing. The irony, though, is that to many consumers it looks the same, because you often look into a model through a picture. But the skill and the experience that the practitioner needs is very different. It’s a completely different way of looking at the world when you start building models as opposed to solely drawing pictures.

I see still, coming into 2015, a huge opportunity to uplift that skill set because I find a lot of people say they know how to model but they haven’t really had that experience. You just can’t simply explain it to somebody, you have to do it. It’s not the be-all and end-all—it’s part of the architect’s toolkit, but being able to think architecturally and from a model-driven approach is a key skill set that people are going to need to keep pace with all the rapid changes going on in the marketplace right now.

I also see that there’s still an opportunity to get people better educated on some formal modeling notations. We’re big fans of the Unified Modeling Language, UML. I still think uptake of some of those specifications is not as prevalent as it could be. I do see that there are architects that have some familiarity with some of these modeling standards. For example, in our TOGAF® training we talk about standards in one particular slide, many architects have only heard of one or two of them. That just points to there being a lack of awareness about the rich family of languages that are out there and how they can be used. If a community of architects can only identify one or two modeling languages on a list of 10 or 15 that is an indirect representation of their background in doing modeling, in my opinion. That’s anecdotal, but there’s a huge opportunity to uplift architect’s modeling skills.

How do you define the difference between models and pictures?

Modeling requires a theory—namely you have to postulate a theory first and then you build a model to test that theory. Picture drawing doesn’t require a theory—it just requires you to dump on a piece of paper a bunch of stuff that’s in your head. Modeling encourages more methodical approaches to framing the problem.

One of the anti-patterns that I’ve seen in many organizations is they often get overly enthusiastic, particularly when they get a modeling tool. They feel like they can suddenly do all these things they’ve never done before, all that modeling stuff, and they end up “over modeling” and not modeling effectively because one of the key things for modeling is modeling just enough because there’s never enough time to build the perfect thing. In my opinion, it’s about building the minimally sufficient model that’s useful. And in order to do that, you need to take a step back. TOGAF does acknowledge this in the ADM—you need to understand who your stakeholders are, what their concerns are and then use those concerns to frame how you look at this content. This is where you start coming up with the theory for “Why are we building a model?” Just because we have tools to build models doesn’t mean we should build models with those tools. We need to understand why we’re building models, because we can build infinite numbers of models forever, where none of them might be useful, and what’s the point of that?

The example I give is, there’s a CFO of an organization that needs to report earnings to Wall Street for quarterly projections and needs details from the last quarter. And the accounting people say, “We’ve got you covered, we know exactly what you need.” Then the next day the CFO comes in and on his/her desk is eight feet of green bar paper. She/he goes out to the accountants and says, “What the heck is this?” And they say “This is a dump of the general ledger for the first quarter. Every financial transaction you need.” And he/she says, “Well it’s been a while since I’ve been a CPA, and I believe it’s all in there, but there’s just no way I’ve got time to weed through all that stuff.”

There are generally accepted accounting principles where if I want to understand the relationship between revenue and expense that’s called a P&L and if I’m interested in understanding the difference between assets and liabilities that’s a balance sheet. We can think of the general ledger as the model of the finances of an organization. We need to be able to use intelligence to give people views of that model that are pertinent and help them understand things. So, the CFO says “Can you take those debits and credits in that double entry accounting system and summarize them into a one-pager called a P&L?”

The P&L would be an example of a view into a model, like a picture or diagram. The diagram comes from a model, the general ledger. So if you want to change the P&L in an accounting system you don’t change the financial statement, you change the general ledger. When you make an adjustment in your general ledger, you re-run your P&L with different content because you changed the model underneath it.

You can kind of think of it as the difference between doing accounting on register paper like we did up until the early 21st Century and then saying “Why don’t we keep track of all the debits and credits based on a chart of accounts and then we can use reporting capabilities to synthesize any way of looking at the finances that we care to?” It’s allows a different way for thinking about the interconnectedness of things.

What are some of the most sought after classes at APG?

Of course TOGAF certification is one of the big ones. I’d say in addition to that we do quite a bit in systems engineering, application architecture, and requirements management. Sometimes those are done in the context of solution delivery but sometimes they’re done in the context of Enterprise Architecture. There’s still a lot of opportunity in supporting Enterprise Architecture in some of the fundamentals like requirements management and effective architectural modeling.

What kinds of things should EAs look for in training courses?

I guess the big thing is to try to look for are offerings that get you as close to practical application as possible. A lot of people start with TOGAF and that’s a great way to frame the problem space. I would set the expectation—and we always do when we deliver our TOGAF training—that this will not tell you “how” to do Enterprise Architecture, there’s just not enough time for that in four days. We talk about “what” Enterprise Architecture is and related emerging best practices. That needs to be followed up with “how do I actually do Enterprise Architecture modeling,” “how do I actually collect EA requirements,” “how do I actually do architecture trade-off analysis?” Then “How do I synthesize an architecture roadmap,” “how do I put together a migration plan,” and “how do I manage the lifecycle of applications in my portfolio over the long haul?” Looking for training that gets you closer to those experiences will be the most valuable ones.

But a lot of this depends on the level of maturity within the organization, because in some places, just getting everybody on the same page of what Enterprise Architecture means is a big victory. But I also think Enterprise Architects need to be very thoughtful about this cross-training. I know it’s something I’m trying to make an investment in myself, is becoming more attuned to what’s going on in other parts of the enterprise in which Enterprise Architecture has some context but perhaps is not a known player. Getting training experiences in other places and engaging those parts of your organizations to really find out what are the problems they’re trying to solve and how might Enterprise Architecture help them is essential.

One of the best ways to demonstrate that is part of the organizational learning related to EA adoption. That may even be the bigger question. As individual architects, there are always opportunities for greater skill development, but really, organizational learning is where the real investment needs to be made so you can answer the question, “Why do I care?” One of the best ways to respond to that is to have an internal success. After a pilot project say, “We did EA on a limited scale for a specific purpose and look what we got out of it and how could you not want to do more of it?”

But ultimate the question usually should be “How can we make Enterprise Architecture indispensible? How can we create an environment where people can perform their duties more rapidly, more efficiently, more effectively and more sustainably based on Enterprise Architecture?” This is part of the problem, especially in larger organizations. In 2015, it’s not really the first time people have been making investments in Enterprise Architecture, it’s the second or third or fourth time, so it’s a reboot. You want to make sure that EA can become indispensible but you want to be able to support those critical activities with EA support and then when the stakeholders become dependent on it, you can say “If you like that stuff, we need you to show up with some support for EA and get some funding and resources, so we can continue to operate and sustain this capability.”

What we’ve found is that it’s a double-edged sword, ironically. If an organization has success in propping up their Architecture capability and sustaining and demonstrating some value there, it can be a snowball effect where you can become victims of your own success and suddenly people are starting to get wind of “Oh, I don’t have to do that if the EA’s already done it,” or “I can align myself with a part of the business where the EA has already been done.” The architecture community can get very busy—more busy than they’re prepared for—because of the momentum that might exist to really exploit those EA investments. But at the end of the day, it’s all good stuff because the more you can show the enterprise that it’s worth the investment, that it delivers value, the more likely you’ll get increased funding to sustain the capability.

By The Open GroupChris Armstrong is president of Armstrong Process Group, Inc. and an internationally recognized thought leader and expert in iterative software development, enterprise architecture, object-oriented analysis and design, the Unified Modeling Language (UML), use case driven requirements and process improvement.

Over the past twenty years, Chris has worked to bring modern software engineering best practices to practical application at many private companies and government organizations worldwide. Chris has spoken at over 30 conferences, including The Open Group Enterprise Architecture Practitioners Conference, Software Development Expo, Rational User Conference, OMG workshops and UML World. He has been published in such outlets as Cutter IT Journal, Enterprise Development and Rational Developer Network.

Join the conversation! @theopengroup #ogchat

Leave a comment

Filed under Business Architecture, Enterprise Architecture, Enterprise Transformation, Professional Development, Standards, TOGAF, TOGAF®, Uncategorized