Search Results for: business model

The 1st Belgian ArchiMate User Group Meeting

by

<p><span style=”color: rgb(80, 80, 80); font-size: 11px; line-height: 19px;”>Last week I was proud to chair the first Belgian </span><a href=”http://pubs.opengroup.org/architecture/archimate2-doc/” style=”font-size: 11px; line-height: 19px;”>ArchiMate</a><span style=”color: rgb(80, 80, 80); font-size: 11px; line-height: 19px;”> User Group meeting in Brussels, hosted by </span><a href=”http://www.itworks.be/” style=”font-size: 11px; line-height: 19px;”>IT Works</a><span style=”color: rgb(80, 80, 80); font-size: 11px; line-height: 19px;”>. With three good speakers and a group of about 30 participants, the meeting was a big success. Hopefully we will have many more of such sessions in the years to come. </span></p><p>In this short blogpost I’ll present some of the highlights from the session. Rather than attempting to summarize the excellent talks by Jan Casteels (AXA, ING), Geert Cannaerts &amp; Christof Nikolay (both HP), and Pieter van Ostaeyen (de Lijn), I’ll stick to presenting some of the highlights.</p><ul><li>A common element in each of the three stories is “business-focused analyses”. Or, to put it differently: we spoke a lot about the type of analyses we can do for various (business) stakeholders as well as creating powerful visualizations to support decision making.</li> <li>The three speakers each used different tools (including <a href=”http://archi.cetis.ac.uk/”>Archi</a>, <a href=”http://www.sparxsystems.com.au/”>Sparx</a>, and <a href=”http://www.bizzdesign.nl/tools/architect/”>BiZZdesign Architect</a>).  The consensus seemed to be that all tools work as long as the focus is on modeling / entry of concepts and relations. A “proper” tool like Architect is needed when the focus shifts to analyses (i.e., color views, label views, generating views and cross tables, roadmapping and so on)</li> <li>There was a lot of discussion about different levels of models. <ul><li>On the one hand this refers to the difference between “architecture” and “design” (i.e., growing attentions to linking architecture models at the enterprise level to process management, business rule management, and data management at the design level).</li> <li>It also appeals to the difference between three levels of abstraction: conceptual, logical, and physical models. A crisp and clear distinction between these levels is far from easy, yet it is important to at least distinguish (and create links) between a “conceptual/logical” model and a “physical” model of the enterprise</li> </ul></li> <li>Other topics that were briefly discussed include </li> <li>The use of reference models for re-use and a head-start in creating consistent models across the enterprise.</li> <li>Starting ArchiMate modeling projects from the bottom-up. That is: rather than shooting for a top-down, enterprise-wide initiative, we see more and more organizations where the first ArchiMate models are developed in projects. This has the added advantage of adding business value early, as well as establishing good practices in modeling from the start!</li></ul><p>After a good discussions, we also found several areas where more support and guidance would be useful for the ArchiMate community at large. These boil down to the following:</p><ul><li>Easy exchange of models between tools: we see that different stakeholders and groups of professionals require different types of tools. At some point the necessity to integrate these models / to upgrade to a full-blown EA tool like Architect arises. Being able to seamlessly switch between tools is important. After all, it is about the content, not the tool.</li> <li>In line with the discussion on different levels of models, more guidance on conceptual / logical / physical modeling as well as tool support (i.e., the use of dependency relations in BiZZdesign Architect) will help the community to deal with this issue consistently and effectively</li> <li>Last but not least: in many situations it would be valuable to be able to represent the modality of relations between concepts. This goes for “cardinality” of associations, but it goes further than that. Being able to represent the fact that “a process always uses a services” versus “a process may optionally use a service” can be equally important</li></ul><p> All in all a great session with plenty of tips, real-world stories, and suggestions for taking ArchiMate initiatives to the next level.</p>

Categories Uncategorized

Mom says Save Up; I say do it with Application Rationalization

by

In part 7 of “Memoirs of an Enterprise Architect” I tested your knowledge on data classification and compliance.  Well, I have good news for this week.  There will not be another quiz so you can just sit back, relax and maybe learn a thing or two…

Categories Uncategorized

Accelare Announces WhatFirst 2013

by

I am excited about the new edition of our business architecture product, WhatFirst™. Here is the scoop. Accelare announces the general availability of WhatFirst™ 2013, the next generation of Strategy-to-Execution software on the Microsoft SharePoint 2013 platform. WhatFirst™ is designed as a planning tool to unpack strategy into executable packages of integrated work and provide […]

James Martin – A personal reflection

by
James Martin, technologist, methodologist, entrepreneur and philanthropist died Monday 24 June 2013 aged 79.

I first came across James Martin in the early 1970s. I went to a lecture he gave in London, and he captivated an audience of about 100 people for 2 hours on the topic of real time systems design.  Later on I attended his famous seminars in London and Johannesburg. It was extraordinary how he held huge audiences for multi day sessions, with minimal audience interaction as he drove through the thousands of slides, delivered on two overhead projectors. In those days he was the consummate technology seer and he filled a need in the days before industry analysts.

Yet he was so much more than just a showman. I bought his book on real time system design in 1971 and this was my bible. And down the years I relied on his books in data modeling, database design and  information engineering; they were detailed and useful to a practitioner.

I joined James Martin Associates (JMA) in 1986. I think I was employee number 30 and I had the privilege of working in what must have been one of the most extraordinary and innovative companies at that time. Even when I meet ex JMA colleagues today, we always recall how it was such a great place to be, where everyone was on the leading edge and contributing to the overall development of information engineering. We were taking his ideas and turning them into practical method and tools for many of the world’s largest companies and government agencies.

We didn’t see that much of James Martin. He would attend our annual JAM (sic) session, and if he was in town he might drop in, but that was rare. But he did get feedback. I was deeply involved at one stage, together with Richard Veryard and Mike Mills in developing ideas for Rapid Application Development (RAD) that we took to customer projects and of course appeared later in the James Martin book.

The core of his thinking was the idea that model driven systems were the future and at JMA and subsequently Texas Instruments Software (TI) we proved this by delivering the IEF based on James’ ideas, that became the leading mainframe and client server development tool in the early 1990s. Of course we knew even then that this tool was limited to a very narrow set of patterns, and history has taught us that there is a need for a much broader range of patterns, and varying levels of abstraction and intervention. And even as early as the mid-1990s we were working on componentization and service interfaces because we understood the monolithic architecture, however commercially successful for a short few years, was in reality a simplistic first attempt. Today the term CASE tool is widely disparaged. Yet I believe that James’ original vision will be realized, although the method of realization will be radically different, and by strange coincidence I blogged on this topic very recently. 

James Martin provided inspiration for technologists by identifying big ideas, but he went further by detailing the ideas in his books and teaching and “having the courage of his convictions” by investing in start-up businesses. Which of course made him very wealthy. I would be proud to say that in my work and in everything that CBDI has developed, we have been true to some of the core principles that we hammered out nearly thirty years ago including model driven (including meta model based) and structured with maximum automation. And these are equally applicable to today’s Agile, fast moving world. Of course we (Everware-CBDI) have added and evangelized the  principles of component and service oriented, but the original vision is intact. 
James Martin was an idealist. In several of his works he developed his thinking for a utopian society where technology and automation are used for the greater good in education, health and creating a better world. Sadly I myself came to see some of his works as out of touch with reality. He failed to see the shoddy reality of how politics and politicians are incapable of leveraging technology to deliver better models for society, how the giant Internet companies are creating worldwide networks based on old fashioned capitalistic principles while espousing such things as “do no evil” and practicing tax avoidance, and governments are increasingly using technology to track the every move of citizens without understanding how to govern the use of that data. 
I believe we will remember James Martin, but not necessarily for his big ideas like the early prediction of the Internet or his philanthropy. Rather we will come in time to reflect on his guidance that technology should be leveraged to improve society. Every time we destroy tens of thousands of jobs by introducing new technologies, we should be using the power of technology in education and resource mobilization to ensure that vast numbers of our young people do not remain out of work, or that older people can continue to contribute to society beyond conventional retirement age. 

James Martin – A personal reflection

by
James Martin, technologist, methodologist, entrepreneur and philanthropist died Monday 24 June 2013 aged 79.

I first came across James Martin in the early 1970s. I went to a lecture he gave in London, and he captivated an audience of about 100 people for 2 hours on the topic of real time systems design.  Later on I attended his famous seminars in London and Johannesburg. It was extraordinary how he held huge audiences for multi day sessions, with minimal audience interaction as he drove through the thousands of slides, delivered on two overhead projectors. In those days he was the consummate technology seer and he filled a need in the days before industry analysts.

Yet he was so much more than just a showman. I bought his book on real time system design in 1971 and this was my bible. And down the years I relied on his books in data modeling, database design and  information engineering; they were detailed and useful to a practitioner.

I joined James Martin Associates (JMA) in 1986. I think I was employee number 30 and I had the privilege of working in what must have been one of the most extraordinary and innovative companies at that time. Even when I meet ex JMA colleagues today, we always recall how it was such a great place to be, where everyone was on the leading edge and contributing to the overall development of information engineering. We were taking his ideas and turning them into practical method and tools for many of the world’s largest companies and government agencies.

We didn’t see that much of James Martin. He would attend our annual JAM (sic) session, and if he was in town he might drop in, but that was rare. But he did get feedback. I was deeply involved at one stage, together with Richard Veryard and Mike Mills in developing ideas for Rapid Application Development (RAD) that we took to customer projects and of course appeared later in the James Martin book.

The core of his thinking was the idea that model driven systems were the future and at JMA and subsequently Texas Instruments Software (TI) we proved this by delivering the IEF based on James’ ideas, that became the leading mainframe and client server development tool in the early 1990s. Of course we knew even then that this tool was limited to a very narrow set of patterns, and history has taught us that there is a need for a much broader range of patterns, and varying levels of abstraction and intervention. And even as early as the mid-1990s we were working on componentization and service interfaces because we understood the monolithic architecture, however commercially successful for a short few years, was in reality a simplistic first attempt. Today the term CASE tool is widely disparaged. Yet I believe that James’ original vision will be realized, although the method of realization will be radically different, and by strange coincidence I blogged on this topic very recently. 

James Martin provided inspiration for technologists by identifying big ideas, but he went further by detailing the ideas in his books and teaching and “having the courage of his convictions” by investing in start-up businesses. Which of course made him very wealthy. I would be proud to say that in my work and in everything that CBDI has developed, we have been true to some of the core principles that we hammered out nearly thirty years ago including model driven (including meta model based) and structured with maximum automation. And these are equally applicable to today’s Agile, fast moving world. Of course we (Everware-CBDI) have added and evangelized the  principles of component and service oriented, but the original vision is intact. 
James Martin was an idealist. In several of his works he developed his thinking for a utopian society where technology and automation are used for the greater good in education, health and creating a better world. Sadly I myself came to see some of his works as out of touch with reality. He failed to see the shoddy reality of how politics and politicians are incapable of leveraging technology to deliver better models for society, how the giant Internet companies are creating worldwide networks based on old fashioned capitalistic principles while espousing such things as “do no evil” and practicing tax avoidance, and governments are increasingly using technology to track the every move of citizens without understanding how to govern the use of that data. 
I believe we will remember James Martin, but not necessarily for his big ideas like the early prediction of the Internet or his philanthropy. Rather we will come in time to reflect on his guidance that technology should be leveraged to improve society. Every time we destroy tens of thousands of jobs by introducing new technologies, we should be using the power of technology in education and resource mobilization to ensure that vast numbers of our young people do not remain out of work, or that older people can continue to contribute to society beyond conventional retirement age. 

CEA Credential Renewal Instructions

by

cea logo

6/3/15 UPDATE: feacinstitute.org is currently under complete overhaul! Please continue to submit your EADUs. Even though they do not show on your profile, we are collecting them. We are excited about the new site and ask for your patience in the credential renewal process while this is being completed. This re-design will make the EADU submittal process more functional, give you more information on your profile and will make update our lookup. Thank you again!

CEA Credential Renewal Instructions:

Our ZCEA and CEA recertification process is being refreshed!  Effective 1 October, 2014 we are implementing new guidance on what qualifies for Enterprise Architecture Development Units (EADUs) as part of the Zachman® and FEAC® enterprise architecture certifications. This guidance (published below) is intended to leverage the broad source of education and professional development opportunities you engage in as a professional as an active source of maintaining your certifications. With this refresh we are establishing a six month transition period for those alumni whose certification renewal has lapsed outside of the three year cycle. From 1 Oct to 1 April, Zachman and FEAC graduates may register their EADUs and submit their renewal fee regardless of the lapse in certification. After 1 April, alumni whose certification has lapsed will be required to take an online exam to re-qualify. If you have questions please send them to info [AT] feacinstitute [DOT] org.

FEAC™ has a triennial process for CEA credential renewals, similar to other professional organizations. Your EADU cycle begins on the month of graduation and you should begin filing and recording EA Development Units (EADUs) accuring 20 per year. For example, if you graduated, as a CEA, in April of 2013 your certification is active until April 2016. During this cycle you should be recording EADUs using the online submission form. In April 2016 you submit a request to renew your certification along with the administrative processing fee.  

Remember you need to document 20 EA Development Units per year for a total of 60 in a refreshment period, with member profiles updated, after payment of the CEA Fellow dues.

1) Log into feacinstitute.org

2) Under the menu EA Zone/My Dashboard/My Renewal, fill out the form with how many EADU you are claiming, the event for credit and the date. You may submit this form more than once for multiple events/claims. We will process your request and your EADU total will be updated on your Registration Profile within 7-8 business days.

3) If you have submitted your 60 hours, they have been approved and you are actually applying for CEA renewal and are looking to pay your $99 renewal fee, hit the “Subscribe Now” on the above (My Renewal) page. Your request will be verified and processed by an administrator within 3-4 business days.

 

Certified Enterprise Architect: Maintaining Your Certification

Certification as either a Zachman Certified Enterprise Architect or FEAC Certified Enterprise Architect (CEA) is an industry-recognized credential. You have worked hard to earn this prestigious milestone and need to adhere to FEAC’s continuing certification program to retain professional achievement.  To follow the program, you can participate in a range of professional development activities to earn Enterprise Architecture Development Units (EADUs). 

Every credential requires a specific number of EADU in different categories as a part of a three-year certification cycle. If YOU hold a ZCEA (level 1-4) and a CEA (or ACEA) your EADUs count towards both as a part of the triennial certifications.

Certification

EADU in a 3 year cycle

EADU Requirements per Categories

Zachman Certified Enterprise Architect (Level 1 Associate)

15

(5 EADUs per year)

Educational- 15

Zachman Certified Enterprise Architect (Level 2 Practitioner)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

Zachman Certified Enterprise Architect (Level 3 Professional)

45

(15 EADUs per year)

Educational-30

Development of the Profession-10

Consultant Engagement-5

Zachman Certified Enterprise Architect (Level 4 Educator)

60

(20 EADUs per year)

Educational-20

Development of the Profession-40

(10 must be in Category 5 creating new knowledge)

FEAC Certified Enterprise Architect (CEA)

60

(20EADUs per year)

Educational -40

Development of the Profession-20

FEAC Associate Certified Enterprise Architect (ACEA)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

EADU categories are intended to ensure your continuing professional development is focused on the broad acquisition of knowledge and engagement with the Enterprise Architecture Community.  Professional Development activities yield different numbers of EADUs, as illustrated below.

EADUs earned in excess of a single triennial cycle may be applied to the next cycle, but will still incur additional processing for review, acceptance and auditing of your professional development efforts. 

The following provides additional detail on the EADU categories and amplifying guidance.  Please note that you may be requested to provide documentation if your request for EADU’s is selected for audit. Accepted documentation normally consists of a copy of completion certificates, letter of attendance, registration forms, etc. This documentation is NOT retained beyond any specific audit. 

 

Education Category– The acquisition of knowledge is a key element of ensuring growth in the ability to apply EA concepts.  The following categories provide examples of the types of education you can receive credit for.

Category 1: Zachman/FEAC endorsed courses.

You can take courses officially provided by Zachman International or its education clearing house FEAC.  Courses include:

  • FEAC CEA or ACEA certification training.
  • Zachman ZCEA certification training
  • FEAC Continuing Education Courses.

EADU Guidance: Zachman/FEAC courses generally provide 2 EADU per Continuing Education Course.

Obtaining a second certification in either Zachman or FEAC provides 1.5  EADU for each 8 hours of instructional contact time.

Category 2: Continuing Education

Complete Courses in the following areas.

College credit Courses in the areas of:

  • Systems Engineering
  • Computer/Data Science
  • Business Analysis
  • Strategic Planning and Analysis
  • Program Management/General Management

Or

Non-credit granting educational efforts include:

  • Massive Open Online Course offerings in the areas of the college credit areas listed above.
  • TOGAF certification training (independent of obtaining the certification)
  • IIBA certified provider training courses.
  • PMI certified providers (REPS) in the area of :
    • Agile Methodology
    • Risk Management
    • Portfolio Management
  • Six Sigma Training
  • Professional Courses in the field of Information Security or Information Security training. 

EADU Guidance: College Credit Courses generally grant 3 EADUs per course completed regardless of number of semesters or quarters granted.

Non-credit granting education efforts provide for 1 EADU per 8 hours of instructional contact.  These activities should result in a certificate of completion or some other formal means of documentation.

Category 3: Self-Guided Learning

Self-Guided learning are those engaged by a practitioner independent of any professional facilitation. These may involves research or study.

This includes activities such as:

  • Attendance at workshops or conference meetings.
  • Reading articles, peer journals or instructional manuals related to the field of EA.
  • Watching Video, podcasts or other related efforts not resulting in a certificate of completion.
  • May include being mentored by another EA professional.

EADU Guidance: Credit for this category is limited to no more than 10 EADUs in a cycle.

1/2 EADU is provided for each hour spent involved in self-guided learning.

 

Development of the Profession Category– The development of Enterprise Architecture as a profession is central to the Mission of Zachman International. 

Category 4: Working as an EA Professional

You may earn credit for being an active EA practitioner as a part of your company or in a non-compensated (e.g. volunteer) role as a part of providing support to others as an EA.

This can include:

  • Work as a compensated employee actively engaged in EA activities.
  • Volunteer work for a recognized EA organization.
  • Providing EA services to a recognized non-profit, not-for-profit or other charitable group.

EADU Guidance: Credit for this category is limited to no more than 15 EADUs in a cycle (5 per year).

1 EADU is provided for each hour non-compensated service. (e.g. volunteer)

1 EADU is provided for each 160 hours of compensated service.

Category 5: Creating New Knowledge

You may earn EADUs for creating or supporting the creation of knowledge in the area of Enterprise Architecture.

This can include:

  • Authoring or co-authoring a peer-reviewed article
  • Authoring or co-authoring a non-peer reviewed article
  • Serving as a speaker on an EA related topic (i.e. Zachman Framework, Model Based System Engineering, Strategic Planning etc.).
  • Serve as a Subject Matter Expert on EA or a related topic (e.g. Big Data, Decision Science, etc.).
  • Presenting in a webinar or podcast on the topic of EA or a related area.  (Must be publicly available either free or for purchase).
  • Creating education courses or training content in the area of Enterprise Architecture or related area. (Course work must be publicly available either free or for purchase).

EADU Guidance: There is NO LIMIT for this category.

1 EADU is provided for each hour of activity. 3 EADUs are provided for publication of a peer reviewed article. 1 EADU is provided for publication of a non-peer reviewed article.

 

Consultant Engagement Category– Unique to the Zachman Level 3 certification is the requirement to maintain proficiency-supporting clients in the field of Enterprise Architecture. This category only applies to the Zachman Level 3 for the purposes of maintaining this unique designation in the field of EA.

Category 6: External Consultant

This requirement is unique to Zachman Level 3 certified Zachman consultant. Part of maintaining this certification is having at least 100 hours or more as a paid consultant for EA services.

EADU Guidance: Each 50 hours of paid consultancy provides 2.5 EADUs.

Proof of completion may be in the form of a redacted invoice or contract form. Contact Zachman International directly for more information.

CEA Credential Renewal Instructions

by
CEA Logo ZCEA Logo

 

ZCEA, CEA and ACEA Credential Renewal Instructions:

The following is guidance on what qualifies for Enterprise Architecture Development Units (EADUs) as part of the Zachman® and FEAC® enterprise architecture certifications. This guidance (published below) is intended to leverage the broad source of education and professional development opportunities you engage in as a professional as an active source of maintaining your certifications. With this refresh we are establishing a six month transition period for those alumni whose certification renewal has lapsed outside of the three year cycle. From 1 Oct to 1 April, Zachman and FEAC graduates may register their EADUs and submit their renewal fee regardless of the lapse in certification. After 1 April, alumni whose certification has lapsed will be required to take an online exam to re-qualify. If you have questions please send them to info [AT] feacinstitute [DOT] org.

The FEAC™ Institute and Zachman International® has a triennial process for certification credential renewals, similar to other professional organizations. Your EADU cycle begins on the month of graduation and you should begin filing and recording EA Development Units (EADUs) accruing 20 per year. For example, if you graduated, as a CEA, ACEA or ZCEA in April of 2013 your certification is active until April 2016. During this cycle you should be recording EADUs using the online submission form on your profile. In April 2016 you submit a request to renew your certification along with the administrative processing fee of $99 US.

Remember you need to document 20 EA Development Units per year for a total of 60 in a refreshment period, with member profiles updated, after payment of the CEA Fellow dues.

Instructions:

  1. Log into FEACinstitute.org or Zachman.com
  2. Under the menu My Account/My Profile then the EADU Submissions tab, fill out the form with how many EADUs you are claiming, the event for credit, EADU claim and the date. Click the “Green Plus” button to submit multiple EADU entries. These will post to your profile immediately and be in a “pending” status. Your claim will be “approved” or “denied” (with reasons why) within a week or two.
  3. If you have submitted your 60 hours, and you are actually applying for CEA renewal and are looking to pay your $99 renewal fee, go to the My Account/Certification Renewal menu, click the link and you will be prompted to pay your renewal fee. Your request will be verified and processed by an administrator.’ 

Certified Enterprise Architect: Maintaining Your Certification

Certification as either a Zachman Certified Enterprise Architect or FEAC Certified Enterprise Architect (CEA) is an industry-recognized credential. You have worked hard to earn this prestigious milestone and need to adhere to FEAC’s continuing certification program to retain professional achievement.  To follow the program, you can participate in a range of professional development activities to earn Enterprise Architecture Development Units (EADUs). 

Every credential requires a specific number of EADU in different categories as a part of a three-year certification cycle. If YOU hold a ZCEA (level 1-4) and a CEA (or ACEA) your EADUs count towards both as a part of the triennial certifications.

Certification

EADU in a 3 year cycle

EADU Requirements per Categories

Zachman Certified Enterprise Architect (Level 1 Associate)

15

(5 EADUs per year)

Educational- 15

Zachman Certified Enterprise Architect (Level 2 Practitioner)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

Zachman Certified Enterprise Architect (Level 3 Professional)

45

(15 EADUs per year)

Educational-30

Development of the Profession-10

Consultant Engagement-5

Zachman Certified Enterprise Architect (Level 4 Educator)

60

(20 EADUs per year)

Educational-20

Development of the Profession-40

(10 must be in Category 5 creating new knowledge)

FEAC Certified Enterprise Architect (CEA)

60

(20EADUs per year)

Educational -40

Development of the Profession-20

FEAC Associate Certified Enterprise Architect (ACEA)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

EADU categories are intended to ensure your continuing professional development is focused on the broad acquisition of knowledge and engagement with the Enterprise Architecture Community.  Professional Development activities yield different numbers of EADUs, as illustrated below.

EADUs earned in excess of a single triennial cycle may be applied to the next cycle, but will still incur additional processing for review, acceptance and auditing of your professional development efforts. 

The following provides additional detail on the EADU categories and amplifying guidance.  Please note that you may be requested to provide documentation if your request for EADU’s is selected for audit. Accepted documentation normally consists of a copy of completion certificates, letter of attendance, registration forms, etc. This documentation is NOT retained beyond any specific audit. 

 

Education Category– The acquisition of knowledge is a key element of ensuring growth in the ability to apply EA concepts.  The following categories provide examples of the types of education you can receive credit for.

Category 1: Zachman/FEAC endorsed courses.

You can take courses officially provided by Zachman International or its education clearing house FEAC.  Courses include:

  • FEAC CEA or ACEA certification training.
  • Zachman ZCEA certification training
  • FEAC Continuing Education Courses.

EADU Guidance: Zachman/FEAC courses generally provide 2 EADU per Continuing Education Course.

Obtaining a second certification in either Zachman or FEAC provides 1.5  EADU for each 8 hours of instructional contact time.

Category 2: Continuing Education

Complete Courses in the following areas.

College credit Courses in the areas of:

  • Systems Engineering
  • Computer/Data Science
  • Business Analysis
  • Strategic Planning and Analysis
  • Program Management/General Management

Or

Non-credit granting educational efforts include:

  • Massive Open Online Course offerings in the areas of the college credit areas listed above.
  • TOGAF certification training (independent of obtaining the certification)
  • IIBA certified provider training courses.
  • PMI certified providers (REPS) in the area of :
    • Agile Methodology
    • Risk Management
    • Portfolio Management
  • Six Sigma Training
  • Professional Courses in the field of Information Security or Information Security training. 

EADU Guidance: College Credit Courses generally grant 3 EADUs per course completed regardless of number of semesters or quarters granted.

Non-credit granting education efforts provide for 1 EADU per 8 hours of instructional contact.  These activities should result in a certificate of completion or some other formal means of documentation.

Category 3: Self-Guided Learning

Self-Guided learning are those engaged by a practitioner independent of any professional facilitation. These may involves research or study.

This includes activities such as:

  • Attendance at workshops or conference meetings.
  • Reading articles, peer journals or instructional manuals related to the field of EA.
  • Watching Video, podcasts or other related efforts not resulting in a certificate of completion.
  • May include being mentored by another EA professional.

EADU Guidance: Credit for this category is limited to no more than 10 EADUs in a cycle.

1/2 EADU is provided for each hour spent involved in self-guided learning.

 

Development of the Profession Category– The development of Enterprise Architecture as a profession is central to the Mission of Zachman International. 

Category 4: Working as an EA Professional

You may earn credit for being an active EA practitioner as a part of your company or in a non-compensated (e.g. volunteer) role as a part of providing support to others as an EA.

This can include:

  • Work as a compensated employee actively engaged in EA activities.
  • Volunteer work for a recognized EA organization.
  • Providing EA services to a recognized non-profit, not-for-profit or other charitable group.

EADU Guidance: Credit for this category is limited to no more than 15 EADUs in a cycle (5 per year).

1 EADU is provided for each hour non-compensated service. (e.g. volunteer)

1 EADU is provided for each 160 hours of compensated service.

Category 5: Creating New Knowledge

You may earn EADUs for creating or supporting the creation of knowledge in the area of Enterprise Architecture.

Examples of what this can include:

  • Authoring or co-authoring a peer-reviewed article
  • Authoring or co-authoring a non-peer reviewed article (this can include posts to LinkedIn, social groups etc.)
  • Serving as a speaker on an EA related topic (i.e. Zachman Framework, Model Based System Engineering, Strategic Planning etc.).
  • Serve as a Subject Matter Expert on EA or a related topic (e.g. Big Data, Decision Science, etc.).
  • Presenting in a webinar or podcast on the topic of EA or a related area.  (Must be publicly available either free or for purchase).
  • Creating education courses or training content in the area of Enterprise Architecture or related area. (Course work must be publicly available either free or for purchase).
  • Other

EADU Guidance: There is NO LIMIT for this category.

1 EADU is provided for each hour of activity. 3 EADUs are provided for publication of a peer reviewed article. 1 EADU is provided for publication of a non-peer reviewed article.

 

Consultant Engagement Category– Unique to the Zachman Level 3 certification is the requirement to maintain proficiency-supporting clients in the field of Enterprise Architecture. This category only applies to the Zachman Level 3 for the purposes of maintaining this unique designation in the field of EA.

Category 6: External Consultant

This requirement is unique to Zachman Level 3 certified Zachman consultant. Part of maintaining this certification is having at least 100 hours or more as a paid consultant for EA services.

EADU Guidance: Each 50 hours of paid consultancy provides 2.5 EADUs.

Proof of completion may be in the form of a redacted invoice or contract form. Contact Zachman International directly for more information.

 

 

CEA Credential Renewal Instructions

by
CEA Logo
ZCEA Logo

ZCEA and CEA Credential Renewal Instructions:

The following is guidance on what qualifies for Enterprise Architecture Development Units (EADUs) as part of the Zachman® and FEAC® enterprise architecture certifications. This guidance (published below) is intended to leverage the broad source of education and professional development opportunities you engage in as a professional as an active source of maintaining your certifications. With this refresh we are establishing a six month transition period for those alumni whose certification renewal has lapsed outside of the three year cycle. From 1 Oct to 1 April, Zachman and FEAC graduates may register their EADUs and submit their renewal fee regardless of the lapse in certification. After 1 April, alumni whose certification has lapsed will be required to take an online exam to re-qualify. If you have questions please send them to info [AT] feacinstitute [DOT] org.

FEAC™ has a triennial process for CEA credential renewals, similar to other professional organizations. Your EADU cycle begins on the month of graduation and you should begin filing and recording EA Development Units (EADUs) accruing 20 per year. For example, if you graduated, as a CEA, in April of 2013 your certification is active until April 2016. During this cycle you should be recording EADUs using the online submission form on your profile. In April 2016 you submit a request to renew your certification along with the administrative processing fee.  

Remember you need to document 20 EA Development Units per year for a total of 60 in a refreshment period, with member profiles updated, after payment of the CEA Fellow dues.

1) Log into feacinstitute.org

2) Under the menu My Account/My Profile then the EADU Submissions tab, fill out the form with how many EADUs you are claiming, the event for credit and the date. Click the “Green Plus” button to submit multiple EADU entries. These will post to your profile immediately. 

3) If you have submitted your 60 hours, and you are actually applying for CEA renewal and are looking to pay your $99 renewal fee, go to the My Account/Certification Renewal menu, click the link and you will be prompted to pay your renewal fee. Your request will be verified and processed by an administrator within 3-4 business days.

 

Certified Enterprise Architect: Maintaining Your Certification

Certification as either a Zachman Certified Enterprise Architect or FEAC Certified Enterprise Architect (CEA) is an industry-recognized credential. You have worked hard to earn this prestigious milestone and need to adhere to FEAC’s continuing certification program to retain professional achievement.  To follow the program, you can participate in a range of professional development activities to earn Enterprise Architecture Development Units (EADUs). 

Every credential requires a specific number of EADU in different categories as a part of a three-year certification cycle. If YOU hold a ZCEA (level 1-4) and a CEA (or ACEA) your EADUs count towards both as a part of the triennial certifications.

Certification

EADU in a 3 year cycle

EADU Requirements per Categories

Zachman Certified Enterprise Architect (Level 1 Associate)

15

(5 EADUs per year)

Educational- 15

Zachman Certified Enterprise Architect (Level 2 Practitioner)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

Zachman Certified Enterprise Architect (Level 3 Professional)

45

(15 EADUs per year)

Educational-30

Development of the Profession-10

Consultant Engagement-5

Zachman Certified Enterprise Architect (Level 4 Educator)

60

(20 EADUs per year)

Educational-20

Development of the Profession-40

(10 must be in Category 5 creating new knowledge)

FEAC Certified Enterprise Architect (CEA)

60

(20EADUs per year)

Educational -40

Development of the Profession-20

FEAC Associate Certified Enterprise Architect (ACEA)

30

(10 EADUs per year)

Educational-20

Development of the Profession-10

EADU categories are intended to ensure your continuing professional development is focused on the broad acquisition of knowledge and engagement with the Enterprise Architecture Community.  Professional Development activities yield different numbers of EADUs, as illustrated below.

EADUs earned in excess of a single triennial cycle may be applied to the next cycle, but will still incur additional processing for review, acceptance and auditing of your professional development efforts. 

The following provides additional detail on the EADU categories and amplifying guidance.  Please note that you may be requested to provide documentation if your request for EADU’s is selected for audit. Accepted documentation normally consists of a copy of completion certificates, letter of attendance, registration forms, etc. This documentation is NOT retained beyond any specific audit. 

 

Education Category– The acquisition of knowledge is a key element of ensuring growth in the ability to apply EA concepts.  The following categories provide examples of the types of education you can receive credit for.

Category 1: Zachman/FEAC endorsed courses.

You can take courses officially provided by Zachman International or its education clearing house FEAC.  Courses include:

  • FEAC CEA or ACEA certification training.
  • Zachman ZCEA certification training
  • FEAC Continuing Education Courses.

EADU Guidance: Zachman/FEAC courses generally provide 2 EADU per Continuing Education Course.

Obtaining a second certification in either Zachman or FEAC provides 1.5  EADU for each 8 hours of instructional contact time.

Category 2: Continuing Education

Complete Courses in the following areas.

College credit Courses in the areas of:

  • Systems Engineering
  • Computer/Data Science
  • Business Analysis
  • Strategic Planning and Analysis
  • Program Management/General Management

Or

Non-credit granting educational efforts include:

  • Massive Open Online Course offerings in the areas of the college credit areas listed above.
  • TOGAF certification training (independent of obtaining the certification)
  • IIBA certified provider training courses.
  • PMI certified providers (REPS) in the area of :
    • Agile Methodology
    • Risk Management
    • Portfolio Management
  • Six Sigma Training
  • Professional Courses in the field of Information Security or Information Security training. 

EADU Guidance: College Credit Courses generally grant 3 EADUs per course completed regardless of number of semesters or quarters granted.

Non-credit granting education efforts provide for 1 EADU per 8 hours of instructional contact.  These activities should result in a certificate of completion or some other formal means of documentation.

Category 3: Self-Guided Learning

Self-Guided learning are those engaged by a practitioner independent of any professional facilitation. These may involves research or study.

This includes activities such as:

  • Attendance at workshops or conference meetings.
  • Reading articles, peer journals or instructional manuals related to the field of EA.
  • Watching Video, podcasts or other related efforts not resulting in a certificate of completion.
  • May include being mentored by another EA professional.

EADU Guidance: Credit for this category is limited to no more than 10 EADUs in a cycle.

1/2 EADU is provided for each hour spent involved in self-guided learning.

 

Development of the Profession Category– The development of Enterprise Architecture as a profession is central to the Mission of Zachman International. 

Category 4: Working as an EA Professional

You may earn credit for being an active EA practitioner as a part of your company or in a non-compensated (e.g. volunteer) role as a part of providing support to others as an EA.

This can include:

  • Work as a compensated employee actively engaged in EA activities.
  • Volunteer work for a recognized EA organization.
  • Providing EA services to a recognized non-profit, not-for-profit or other charitable group.

EADU Guidance: Credit for this category is limited to no more than 15 EADUs in a cycle (5 per year).

1 EADU is provided for each hour non-compensated service. (e.g. volunteer)

1 EADU is provided for each 160 hours of compensated service.

Category 5: Creating New Knowledge

You may earn EADUs for creating or supporting the creation of knowledge in the area of Enterprise Architecture.

Examples of what this can include:

  • Authoring or co-authoring a peer-reviewed article
  • Authoring or co-authoring a non-peer reviewed article (this can include posts to LinkedIn, social groups etc.)
  • Serving as a speaker on an EA related topic (i.e. Zachman Framework, Model Based System Engineering, Strategic Planning etc.).
  • Serve as a Subject Matter Expert on EA or a related topic (e.g. Big Data, Decision Science, etc.).
  • Presenting in a webinar or podcast on the topic of EA or a related area.  (Must be publicly available either free or for purchase).
  • Creating education courses or training content in the area of Enterprise Architecture or related area. (Course work must be publicly available either free or for purchase).
  • Other

EADU Guidance: There is NO LIMIT for this category.

1 EADU is provided for each hour of activity. 3 EADUs are provided for publication of a peer reviewed article. 1 EADU is provided for publication of a non-peer reviewed article.

 

Consultant Engagement Category– Unique to the Zachman Level 3 certification is the requirement to maintain proficiency-supporting clients in the field of Enterprise Architecture. This category only applies to the Zachman Level 3 for the purposes of maintaining this unique designation in the field of EA.

Category 6: External Consultant

This requirement is unique to Zachman Level 3 certified Zachman consultant. Part of maintaining this certification is having at least 100 hours or more as a paid consultant for EA services.

EADU Guidance: Each 50 hours of paid consultancy provides 2.5 EADUs.

Proof of completion may be in the form of a redacted invoice or contract form. Contact Zachman International directly for more information.

 

 

Enterprise Architecture Lifecycle

by

The Enterprise Architecture team has a lifecycle of its own, but doesn’t operate in a vacuum. The Enterprise Architecture capability fails if it is seen too much as blue sky thinking in an ivory tower. The Enterprise Architecture team will interact closely with all the other management processes in an organisation, especially the IT management […]

Cloud: The Testing Ground for the New CIO

by

Guest post by: Mike Pearl In case you missed it, Michael Hickins of the Wall Street Journal recently detailed a lively panel discussion that unfolded during MIT’s CIO Symposium on May 22, 2013. CIOs complained in chorus about cloud computing vendors circumventing the IT department and selling directly to business units. One CIO compared the proliferation of rogue cloud deployments to cockroaches. In the midst of the fiery finger pointing and complaints about redundancy, complexity, […]

Building Blocks of Your Enterprise Mobile Strategy

by
Given my current focus on Multi-Channel architecture & technology programs for Retail and Logistics customer in UK&I, I am often on a look out for new ideas, trends and business case studies. This interest took me to the IBM Enterprise Mobile Summit earlier this week in London Southbank. It was a compact but impressive gathering of Mobile industry experts, suppliers and consumers. It did help me crystallize my thoughts around Enterprise Mobile Strategy which I am trying to summarize in this blog post.   
When an Enterprise (commercial organisation) makes an investment decision to develop a Mobile Strategy (e.g. Mobile Applications or Apps) and related products or services, it should do so based on strategic enterprise intent (or in certain instances tactical response). This investment should take into account a number of stakeholder perspectives such as Functional, Development, Delivery, Operations, End-User Consumer and the Market.


IBM MobileFirst

The Strategic Intent and drivers behind Enterprise Mobile Investment – 
Before committing funds on Mobile strategy a valid question to ask is, what is your Enterprise attempting to achieve by mobile investment? For instance do you see mobile evolving as one of your primary channel to market? Are you attempting to gather insights from mobile data which may provide new opportunities for product and services expansion? 

Or are you simply trying to increase your business transactions though Mobile media. In some instances it may be seen as a media for extending the brand experience for more personal shopping or browsing experience.


The Enterprise Functional Perspective – If the purpose of Mobile strategy is to address internal organisation efficiency then the functional objectives need to focus on employee and organisation productivity enhancement. For instance how can a Mobile App transform, optimise internal work flow and may be also enhance the customer interactions. KPIs here could be reduction of complexity, reduction in wastage, improving quality, faster time to market etc. As I observed in IBM session, some of IBM customers are using the Mobile strategy to extend Enterprise business network in new ways. For instance an Italian organisation leveraged Mobile Apps to find promotions in their network and connected people to these promotions. Michael Gilfix of IBM in this session also cited IBM’s own example of how Mobile strategy is driving next level of productivity by acknowledging its global workforce segmentation.

The Development Lifecycle Perspective – During the session both Michael Gilfix of IBM and Jessica Figueras, a Mobile Industry Analysthighlighted a point that there is a difference between creating conventional Apps and Mobile Apps. Mobile development and developers need to understand the Mobile App consumption patterns, workflows and user interaction in different ways. IBM briefly shared their Mobile Development Lifecycle process which comprises of iterative phases such as; Design & Develop, Instrument, Integrate, Test, Scale & Certify, Deploy, Manage, Obtain Insight and back to Design & Develop. Jessica made a good point that Mobile Apps are becoming more and more complex and they need Enterprise Architecture underpinning them to be successful.


The IT Delivery and Operations Perspective – The above point about Enterprise Architecture requirements extends into the Operational and Delivery aspects of IT too. Challenge of Fragmentation is particularly important; how best to serve different fragmented devices to serve multi-channel experience which is a different challenge that Web Apps where one size often fits all consumers. Michael was also keen to point our Security and Access control aspects such as Loss of control over distribution, impact of BYOD, Control of data and access as code often would run in environment outside of Enterprise control. From the customer satisfaction perspective, the end-user of Mobile Apps will look out for and increasingly expect consistent multi-channel experience. e.g. Airline – phone, kiosk, in-flight, travel experience.

The consumer perspective: Creating compelling mobile user experience – Ali Al-Shakarchi, the UX Architect and Strategist from IBM had some very interesting themes on this perspective which can be argued as the most important factor to make Mobile strategy successful. He highlighted the fact that, user expectations are high and user tolerance is low when it comes to Apps as the competition is fierce, an alternative App is a tap away. Some of the tips which Ali shared were; Stay Relevant, Keep it simple, Build richer experience, Think innovation, Optimise for mobile, Create end to end experience, Be more social and evolve on an ongoing basis in a smart way.

Some of the demos / case studies during the session further underlined some of above points. The Barclays Pingit case study and how it is driving the C2C is a prime example of how Apps can bring success and create new Operating Models for large Enterprises. While the Tealeaf demo effectively showcased the power of analytics behind smart Mobile strategy. 


One of the key takeaway for me was, “Why limit Mobile conversations to IT? Focus must be on exploring business opportunities & enhancing business capabilities”. Iwould like to congratulate IBM for putting together a smart, effective and useful summit. I certainly hope to apply some of the above lessons learnt for my customers in Retail and Logistics in near future. 

For more on IBM Mobilefirst read here