hackathon 240x200

In the response to the dynamically changing geo-political environment that we face today, NATO conducts a process of continuous transformation guided by a high level political agenda. Bringing effective change to such a large organization is however, a complex endeavor. It involves many actors, and typically is accompanied by water-fall type, lengthy procurement processes. This significantly hampers innovation, especially in the area of Information and Communication Technology where rapid agile methods have been proven to be much more effective.

In order to manage the enterprise change the North Atlantic Council issued the "Alliance Consultation, Command and Control Strategy" with a call to "establish Enterprise Architecture discipline". This new discipline is further guided by Enterprise Architecture Policy, which explicitly sets Enterprise Architecture primary objective to "...translate NATO’s vision and strategy into effective change of the current business and IT environments".

Enterprise Architecture Hackathon 2017

2017 ea hackathon hbThe 2nd Enterprise Architecture Hackathon will build on already proven business model to further stimulate transformation and innovation within NATO. During Enterprise Architecture Track at TIDE Sprint in the fall of 2016 the following three business areas were selected for the 2nd edition of Enterprise Architecture Hackathon: Cyberspace, Verification and Validation, Command and Control.

The participants of Modelling challenge will be tasked to develop a set of architectural patterns representing innovative aspects of the Cyberspace Domain by applying ideas from state-of-the- art technologies and business practices.
The developed patterns should apply service oriented architecture principles, work in the federated environment, and identify interoperability points along with standardization opportunities.

The participants of Coding challenge will be tasked to apply modern Data Analytics to discover “hidden gems” within the provided datasets from multiple, different interoperability testing events in which NATO-related Command and Control systems participate every year.
The goal is to come up with appealing visualizations of findings, and explain how those could be used to transform business.

The participants of Joint Challenge will be tasked to develop experimental solutions in the domain of the Internet of Things (IoT) that can be used to solve operational problems.
Solutions can be either architectural models or working software/hardware prototypes.

The 2nd NATO Enterprise Architecture Hackathon will take place in London on 27-31 Mar 2017; click here for the Invitation Letter.

Additionally, a Request For Information has been issued for industry and academia. It is available here.

Enterprise Architecture practice within NATO is already well established and the number of architectural products and use cases constantly increases. Nevertheless, the delivery of the ultimate effect – Enterprise Change – is often delayed due to organizational inertia.

Allied Command Transformation, driven by its transformational mission, have developed the concept of the Enterprise Architecture (EA) Hackathon as a means to enable rapid transformation and innovation that could instantly re-shape the NATO Enterprise. The concept is to directly address current business needs by applying an industry proven format, engaging with groups made up of both of experts and novices "parachuted" into high intensity work environment for a time limited period to focus on specific challenges.

NATO’s multinational nature, consensus-based business model and high level of organizational complexity form an environment where unique problems emerge. Some of them are trivial, other very challenging and difficult to solve by traditional means. EA Hackathon focuses on the latter and provides participants a rare opportunity to work with NATO experts to develop solutions. Many will agree - "If you can solve it for NATO you surely can solve it for anyone else".

Participants from nations, NATO bodies, academia, and industry come to EA Hackathon to work in competitive environment on the pressing issues NATO is facing today. The resultant solutions developed for a set of predefined challenges are kept in the open source domain to enable future development and collaboration. The best solutions are being deployed within NATO Enterprise to address urgent business needs.

EA Hackathon does not replace the traditional research, development and procurement processes, but rather complements them, with the aim to accelerate the enterprise change by stimulating multidisciplinary innovation in the areas of the greatest business risks and opportunities.


The aim of EA Hackathon is to create the environment for experts and novices who are involved, or interested, in businesses innovation and transformation to competitively work on the pressing problems identified within NATO Enterprise that are difficult to solve by the traditional means.


The EA Hackathon events provide a mechanism to:

  • Develop innovative architectural models, views, and methods for presented business cases
  • Develop novel software/hardware based solutions for the “low-hanging fruits” business cases
  • Promote EA discipline by sharing knowledge and increasing awareness among EA stakeholders


In 2009 a small group of NATO and National architects met at TIDE Sprint in Amsterdam to begin building a community of experts interested in innovation and transformation of Enterprises by applying the frameworks, tools and techniques of the Enterprise Architecture discipline. The Enterprise Architecture track was born, and quickly has become one of the most popular tracks of the TIDE Sprint events.

The EA community grew over the years reaching 100+ registered participants in 2015. Throughout the years the main objectives that the group remain relatively constant and stand as:

  • To foster relationships among NATO and National bodies using and promoting Enterprise Architecture approach.
  • To meet in a peer-to-peer format to share architecture methods, techniques, and tools supporting Transformation of and Innovation within Enterprises
  • To review and harmonize current and future architectural activities/initiatives

The EA community work led to many joint ventures among participants and contributed to the production of the architectures, increase of the capability development process maturity and increase of the Communication and Information Systems (CIS) interoperability and standardization levels within NATO. The community driven architectural products include Consultation, Command and Control (C3) Taxonomy and C3 Technical Services Taxonomy.

The EA community also influenced the work conducted by NATO policy makers what resulted in the approval by the NAC of the C3 Alliance Strategy4 that recognized and calls for the implementation of Enterprise Architecture as a discipline in the NATO Enterprise. As the highest level policy document this strategy guides the development of Policies and Directives that orchestrate NATO organization and its interactions with Nations and partner organizations.

To further increase the adoption and maturity of the architectural discipline, the EA community proposed to provide more "hands-on" experience that could bring closer the mindsets of participants and lead to the development of transformational products. It has becoming especially critical as the number of the architectural products is constantly growing and the lack of standardisation and effective exchange mechanisms hampers further evolution of the discipline. Appendix A provides more insight into the EA discipline primary work areas.

Following the best industry practices it was agreed during the Fall TIDE Sprint in 2015 to use the Hackathon format to address the need for change. It allows for engagement with participants who are not traditionally involved in enterprise architecture, but could provide an eye-opening ideas to the community. At the same time the teamwork and on-site prototyping of solutions would allow for rapid idea-to-solution cycles. Lastly, the hackathon format brings the friendly competition aspect that shouldn’t be underestimated.

The details of the future event were discussed and the formal name and definition was agreed as follows:

The EA Hackathon is an event where enterprise architects, software developers, and experts from related fields meet to form a teams and compete to rapidly develop solutions for business problems by applying the EA discipline methods, tools and techniques.

During a EA Hackathon teams compete to identify solutions to specific challenges by fostering innovation, engaging diverse stakeholders and improving understanding of challenges faced by the NATO Alliance.


The EA Hackathon offers the participants two main types of challenges for competition – modelling and coding. It's recommended for the participating teams to select only one of the challenges. The generic description of the challenges is given below and is constant over multiple EA Hackathon events. The specific details of challenges for a given event are provided in the PART TWO of this Handbook and will vary from event to event.

The Modeling Challenge(s) calls, for the given business case, to develop of an innovative EA method, visualization, architectural model, or technique improving effectiveness of enterprise architecture approach.

The Coding Challenge(s) calls, for the given business case or the previous modelling challenge outcome, to develop a novel software/hardware based solution.

The Joint Challenge calls, for the given business case, to develop experimental solutions in the domain of the Internet of Things (IoT) that can be used to solve operational problems. Solutions can be either architectural models or working software/hardware prototypes.

The professions and skillset of the individuals participating in the EA Hackathon is not constrained by any formal requirements and includes, but is not limited to, EA/Business/ICT architects, operational analysts, system engineers, software developers, graphics designers, human factors experts, business managers, and students.

There are no prerequisites on the level of expertise and both experienced professionals, early adopters, and students can participate. The EA Hackathon equally welcomes participants from Industry, Academia and Military/GO/NGO organizations. The EA Hackathon is not strictly technical event, and therefore there is no need, nor prerequisite for a technical knowledge. Equality important as expertise are enthusiasm and energy.

The only formal requirement imposed on a participant is a sponsorship requirement that could be obtained via National Military or Government organizations. See the Preparation chapter for more information about registration process.

All the participants will register and form (or be formed) into the teams of 2-3 persons before or on the first day of the event. Only registered teams will participate in the competition.

To assure the fairness of the competition and facilitate for wide participation the EA Hackathon organizer will colour code each of the participating teams by either blue, green or white colour.

Blue Teams are a competitive hackers’ group of individuals from Military, Industry and Academia. The primary task of the Blue Teams is to solve and present the the offered challenge(s).
Green Teams are a non-competitive hackers’ group of individuals from NATO with a NATO Architect on board. The primary task of the Green Team is to solve and present the offered challenge. To assure the fairness of competition green teams are not participating in competition. The Green Teams are allowed to provide the expertise to the Blue Teams upon request.
White Team is a non-competitive control team. The primary responsibility of the White Team is to assure the efficient execution of the Hackathon and fairness of the competition. The White Team is allowed to select one of the challenges and present the solution. The team members will include modelling and coding challenge designers, game controllers, SMEs, Media, Infrastructure designers and administrators.

The Selection Board consists of the three voting members and the lead of the White team. The Lead of White team plays only advisory role and has no voting right. The selection board members will be nominated for each EA Hackathon.

All the participants are required to bring their own devices (BYOD) with wi-fi network cards. The participants may offer their architectural/requirements/3P repositories for other for reuse/exploitation/integration.


The EA Hackathon process includes three main stages; preparation, execution and closure.

In the process of preparation all the participants are encouraged to familiarize themselves with the read ahead materials posted for each of the challenges.

The registration process involves two steps.

In the first step all the participants who don’t have Tidepedia website account are required to send account creation request to This email address is being protected from spambots. You need JavaScript enabled to view it. with the following data:

  • First and Last Name
  • Organization – including command/agency/company name and country (if applicable)
  • Sponsor (if the organization is non-military)
  • E-mail address – confirmation and instructions will be sent to this address
  • Mentioning that the account is requested for the EA Hackathon

Once the participants received the credentials for Tidepedia portal and form a team they should send the following information to This email address is being protected from spambots. You need JavaScript enabled to view it. to complete the team registration.

  • Team Name
  • Team Members’ names
  • Team Members’ roles (see Teams and Selection Boards chapter of the EA Handbook)
  • Team suggested allocation (blue or green team).
  • Accepted Challenge (modeling, coding, both)
  • Willingness to open a team for external participants (only for teams with 2 players)

The individual participants who received the Tidepedia credentials, in order to complete the registration process, should send email to This email address is being protected from spambots. You need JavaScript enabled to view it. with the following information:

  • Tidepedia user name
  • Team preference (blue or green team)
  • Challenge preference (modeling, coding, both)

The organizer will make the best effort to allocate individual participants to their preferred teams and challenges. The list of individual participants with their preferences will be published online as soon as they complete the registration process. The individual participants are welcome to contact directly the registered teams accepting external participants before the event.

The registration will be formally closed on the first day of the EA Hackathon.

Preparation of Challenges
The coding and modelling challenges will be revealed in stages leaving the element of surprise for the last minutes before the execution. The high level description of the challenges will be posted early on with the initial information package. The final information package will specify more details of the challenges providing detailed selection criteria, examples of possible solutions, and mandatory prerequisites. Lastly the element of surprise will be brought to the participants on the day of the hackathon execution.

The execution of the main event will be broken into three stages. First the Set Up and Introductory sessions will prepare the execution on the site, followed later by the main competition stage including Final Products Submission and then Closure.

During the main competition the teams will be solving the offered challenges. While this take place the interaction among teams is allowed as long as it not distracting other teams work. The participants are encouraged to act as following basic “library” behaviour rules.

The EA Hackathon Organizer promotes a healthy and respectful working environment and stimulates:

  • Civilized and unambiguous use of language, considering that participants may not speak their native tongue;
  • Emphatic and open relations within the team, empowering all participants and valuing each other's abilities; and
  • Helpful and friendly interactions with other participants, respecting opposite and alternate opinions and contributions.

The final products along with presentation (optional) need to be stored on the shared server following the guidance provided by the Hackathon Coordinator.