PLENARY - E-Government
The European Interoperability Reference Architecture (EIRA) defines a common terminology, consisting of the most salient architecture building blocks needed to design, assess, and communicate about interoperable e-Government solutions. It provides the structure necessary for coordination between public administrations in the EU institutions and/or Member States on ICT solutions to avoid the risk of creating new digital barriers for administrations, businesses, and citizens.
The EIRA is built upon TOGAF® and the model is expressed in ArchiMate®.
TRACK: EA in Government
Information and data are now the global currency in the 24/7 digital economy. The use of information and data for product and business process innovation across all sectors, including the public sector, has emerged as a primary engine of productivity and growth for national economies.
Today, the Federal Geospatial Platform (FGP) plays a key role in bringing together the Canadian government’s economic, social and environmental data to better support location-based decision-making on a range of complex issues, such as responsible resource development, environmental management, regulatory reviews, and safety and security.
This case study aims to identify the specific barriers to information sharing in the e-Government open data context, and describe the specific suite of open standards, frameworks and policies that were key to overcoming those barriers and enabling information interoperability and sharing for the Federal Geospatial Platform.
Enterprise Architecture techniques, and standards such as TOGAF® and ArchiMate® facilitated the enterprise transformation while leveraging a common platform of technical infrastructure, policies, standards and governance enabled the Government of Canada to make more high-quality, authoritative, and useable geospatial data available in open formats to support better services to Canadians.
Businesses, researchers, governments and individuals who generate, share or use geospatial information may benefit from understanding and adopting standards and policies that allow data to be used for many different applications.
Additionally, leveraging open standards to overcome barriers to interoperability is a universal topic that is of interest to many different organizations that are looking to increase the share-ability and value of their information assets, as interoperability can best be fostered through the consistent application of applicable principles and standards.
The European Union invests a large budget to develop a transportation
corridor with multi-modality (road, river, sea, and railway) across the
European countries. In this context, France is eligible to have a subvention
to develop new services through its transportation infrastructures.
the streams of this EU program consists in creating River Information
Services to help the stakeholders who use the river infrastructures to obtain
information in almost real-time about the condition of navigation. Through a partnership between EDF and VNF, who manage the Rhine in France, a
River Information Services project has been done in 2014/2015 with a large
use of Enterprise Architecture concepts and particularly with the TOGAF
In this presentation, we offer you to discover how Enterprise Architecture
has contributed to the success of this innovative project that allowed France
to have a strategic position in Europe in the development of these kinds of
TRACK: IT4IT™ In Practice
The goal of The Open Group and IT4IT Forum is Industry-wide adoption of the
IT4IT standard. This requires that customers, partners, consultants and
vendors all engage. The main questions are what will make vendors invest in
IT4IT and how can they participate to create real value for customers?
Take a sneak peek into the methodology used by one vendor - Hewlett Packard
Enterprise – using IT4IT to create value for its customers - both external
Learn about the HPE IT4IT Reference Implementation (“RI”) methodology of
mapping products and integrations to the IT4IT Reference Architecture on
multiple levels and how it is used to benefit 3 different types of
Get the inside scoop on real world case studies about customers who have
already applied the HPE IT4IT RI – what problems they solved and what
opportunities they won.
The topic of running IT as a Business has been gaining increasing attention over the past few years, as IT organisations are tasked with leveraging IT to make their organisations more effective, or pioneering radical innovation in the form of new products, markets and business models. A working IT Business Model is decisive for creating value. The publication of the IT4IT Reference Architecture and the complementary IT Management Guide are important steps in understanding, documenting and communicating the value an IT organisation is set to provide. The relevant forums have already seen many companies beginning to use the Requirement to Deploy, Request to Fulfil and Detect to Correct value streams for further cost optimization of the IT operations and show various benefits in adopting the value chain thinking in their IT organisations.
However, it is seldom that we can find companies who have begun to use the Strategy to Portfolio value stream for further enhancing the IT Value Proposition and IT Operating Model of their IT organisations. Having a closer look at the Strategy-to-Portfolio value stream also reveals that this is slightly under-developed in the IT4IT Reference Architecture and the documentation does not really cater for proper understanding of what happens when you begin the transformation journey from this end of the value chain.
This presentation aims to shed some light into what really happens when you begin this journey from the value end. It describes how you can combine additional industry standards and best practices (such as those in BPM, BA, EA disciplines) to comprehensively and holistically translate and structure your IT Value Architecture, and describes the authors’ best practices, having executed such a journey in a green field ERP implementation at a manufacturing company.
TRACK: Open Business Architecture
This track is an opportunity to acquaint oneself with the Preliminary Open Business Architecture Standard. This standard has evolved over more than a decade within The Open Group, and has been aligned with several other initiatives to standardize the practice. Internet communities on business architecture have also shown to resonate well with the standard as defined within The Open Group. The track is furthermore an opportunity to gain insight in the most difficult questions during its development and last but not least learn the about successful use cases.
This first session provides and introduction to and overview of the standard.
2:00 - 2:15 Introduction to the Business Architecture Initiative
-- Paulo Pereira Filho, Philips
2:15 - 2:45 Part I - Introduction to the Open Business Architecture Standard
-- Joel Courquet, Capgemini
2:45 - 3:15 Part II - The Standard Applied to the Business Architecture Value Stream - Work-in-progress Update
-- Paulo Pereira Filho, Philips
3:15 - 3:35 Key Questions that Had to be Resolved to Become a Standard
-- Patrice Duboe, Capgemini
TRACK: EA and Government Regulation
Regulation has been tightened considerably on the banking industry after the
crisis, and it absorbs a considerable amount of change capacity in banks.
Regulation is trickled down from international regulatory bodies such as the
Basel Committee for Banking Supervision (BCBS) and the Financial Stability
Board (FSB) into national and super-national regulation. When banks operating
across multiple legislations apply them, they need to deal with several
similar, but not identical sets of requirements.
Regulation impacts the operating model of a bank at multiple interdependent
levels, and banks need to carefully construct their business architecture to
be both effective in dealing with the differences, while at the same time
being efficient in leveraging the opportunities of a global sourcing
environment, and maintaining control.
TOGAF has constructed the notion of the Enterprise Continuum as a tool for
describing the iterative specialization of a set of requirements,
capabilities and architectural building blocks. The presentation will explain
how these concepts have been applied in the adoption of the FRTB (Fundamental
Review of the Trading Book) and the IRRBB (Interest Rate Risk in the Banking
Book) regulations in the context of the global investment banking industry,
and how business architecture can make change more effective.
TRACK: IT4IT™ In Practice (cont.)
CIOs can use IT4IT™ to provide a powerful link between strategic IT objectives and operational investment. The speaker will review some lessons learned
using IT4IT as a strategy tool in two large corporate environments, and
suggest some approaches that may apply elsewhere.
In both cases, IT4IT was the starting point for IT operating models that
included both the core IT4IT scope and other functions for which CIOs are
responsible, but which are not part of the core IT4IT model, such as
strategic planning, governance, IT finance, etc.
In both cases, IT4IT became the inner shell of a unique visualization adapted
to the culture and strategic dynamic of the organization.
In both cases, this
enabled IT executives to focus investment on root causes and provided the IT
leadership teams with a richer common language for strategic investment in
the Business of IT.
This presentation describes how to get started with IT4IT in your own organization. It describes how IT4IT can be used to realize new IT paradigms such as Bi-Modal IT, Continuous Delivery, DevOps and Cloud management.
This presentation is illustrated with a number of cases of organizations that have applied IT4IT to enable the transition to an agile and modern IT service provider.
This presentation provides the guidance and examples of how to get started with IT4IT. This will provide value insight to help people interested in this topic to get sponsorship of the IT4IT standard within their own organization.
TRACK: Open Business Architecture (cont.)
This second session describes successful use cases, and provides a panel discussion giving the audience the opportunity to ask questions.
4:00 - 4:15 Use Case: Create Vision – Disrupting Technology
-- Paulo Pereira Filho, Philips
4:15 - 4:30 Use Case: From Strategy to Capability Transformation DBCX
-- Giovanni Traverso, Huawei
4:30 -4:45 Use Case: BA Throughout the Transformation Lifecycle
-- Paulo Pereira Filho, Philips
4:45 - 5:15 Panel Discussion
-- Moderator: Patrice Duboe, Capgemini
5:15 - 5:30 Wrap-Up and Way Forward
-- Patrice Duboe, Capgemini
Members Only Meetings
PLENARY - Business Transformation
Innovation. Now what a lot of people do is, they say, “We’re going to go
drive innovation”, and they don’t know very much about their customer,
they don’t know very much about their business, and they don’t know the
issues or opportunities, and they just start free-flowing innovation.
Sometimes that works, like "pin the tail on the donkey". But in a lot of cases,
If you have a clear understanding your customer’s needs at an emotional
level, you ought to be able to have clear focus on the impact to your
business by meeting those needs. What we’re trying to do is to identify the
issues or opportunities that are getting in the way of us actually delivering
those experiences which will meet the needs of the customer so we can drive
the kind of impact we want.
This presentation will illustrate a blend of journey mapping, capability
based planning, and enterprise architecture woven together to create a new
engaging approach to developing the digital business.
TRACK: Open Platform 3.0™ / Digital Architecture
Enterprise Architecture had been serving IT industry for many years and had
been standardized, continually improved, ingrained in IT governance practice.
By contrast, the internet industry has evolved around Agile, Data analytics,
Customer Experience, Cloud and DevOps, Mobile, challenging the traditional
business and operation models.
On the one hand, this tension produced an evolution of EA towards enhanced
Business Architecture, aimed to support new business models based on
ecosystem openness while assuring holistic integration.
This approach failed to become mainstream due to its limiting factor: the
“top-down” transformative approach seems to trail rather than lead the
speed of the business.
On the other hand a blind adoption of “bottom-up” can lead to
uncontrolled duplications and complexity increase, to detriment of
organization/resource efficiency and customer experience.
Such a dichotomy in IT practices (some call it “bi-modal IT”), if not
solved, tends to accumulate technical debt, jeopardizing industry growth
Attempts had been made so far to resolve the dichotomy by adapting non-agile
This approach has a difficulty to render the needed rapid cycle-based process
(with small granularity) as it comes from traditional transformational
We believe that the right model should start from an Agile-native backbone
moving away from large, vertical, centralized approaches towards a
micro-services, embracing incremental development and distributed
responsibilities. Rather than a pure “bottom up” approach as can be found
in Internet startups, however, this model will seek to introduce the concept
of “enterprise architecture as service library”, encouraging the
continual augmentation and refinement of service offerings through common
language and standards.
Digital Technologies, including cloud computing, social computing, mobile computing, big data analysis, and the Internet of Things, are the basis of new business models. The challenge for enterprise architects is to develop architectures that enable enterprises to exploit these models and gain business benefit from the technologies. This can be done by creating enterprise platforms for the development and deployment of business solutions. The solutions will often use multiple technologies, and employ products and services from multiple vendors. Portability and interoperability are therefore essential.
The Open Group established its Open Platform 3.0(tm) Forum to help enterprises gain business advantage from new technical phenomena. The Forum has been exploring the requirements for and current state of the art of open digital platforms, and developing artefacts that architects can use to specify platforms in their enterprises.
This presentation will survey the current state of portability and interoperability between digital platforms, looking at trends such as microservices and container technology, and describe the approach that the Forum has taken and will take going forward to guide architects in creating enterprise platforms for multi--vendor and multi-technology solutions.
Before IT4IT became a standard, I, like many other consultants in my
industry, worked with customers (including public sector bodies) to define
and implement their operating model and associated governance, processes and
standards. This was typically done in an ITIL context with specific
constraints on supplier and partner roles as well as the internal operational
capabilities of the customer.
Looking back, had IT4IT been introduced as a standard, say, 4 years ago, many
of the outcomes of these strategic engagements could have been very different
and I believe for the better. I will therefore provide some examples of where
I believe these improvements could be made.
In turn, this broadens the thinking around learning from history. It is said
that to predict the future, one need only look to the past (e.g. in warfare
or periods of financial boom/bust). I will therefore look to use examples of
retrospective IT4IT evaluation of customer examples to provide insight to our
future IT4IT transformation activity and provide some audience takeaways.
Understanding IT4IT in a ‘non-waterfall’ world. This talk outlines some
practical lessons learnt adopting areas of IT4IT in a traditional utility
ahead of the curve. For example: addressing the issues of project-based
failure vs. the continuous and incremental delivery of measurable benefit (as
opposed to ‘value’) and managing customers’ expectation of fulfilment.
Agile is often blamed for failure, however this is because Agile was never
designed to 'go left' only to ‘go right’ – that is, as a delivery vehicle
mostly for software development. We need to consider this from a wider
perspective, 'accelerated delivery' that takes into account the strategic
investment through to benefits delivery. Capability and services are
considered in detail to highlight the bidirectional nature of IT4IT.
This talk will challenge traditional approaches to IT by integrating IT4IT,
Kanban and workstreams and will suggest some approaches to provide
measurement of these.
TRACK: Professional Development
Disruptive developments from the contemporary information society deeply affect the business and IT operations of enterprises. New IT-driven business models tend to lean heavily on readily available industrialized as-a-service concepts, making the IT dialogue increasingly strategic. The unavoidable question arises, whether architects continue to have a role in this, or, to speak a bit philosophically: “has architecture never become what it used to be?”
Do you, as an architect, want a respectable role in the years ahead? Then earn it! Being valued and respected is not a right, you must show why you should be considered as such.
This session will explore the existential role of architects against the background of new developments in the architecture profession. It will provide a recipe for how architects and/or architecture offices can earn their respect by articulating their value proposition.
One of the most sought after professional titles right now is Enterprise Architect. But the pathway to becoming a qualified and effective Enterprise Architect has been murky and ill defined for years. Over 20 international organizations have come together to address this challenge with a carefully crafted “Career Path Guide to Enterprise Architecture”. In this short talk, Jean Gehring, President of FEAPO, will discuss the key trends transforming Enterprise Architecture and introduce the Career Path Guide for Enterprise Architecture currently under development.
This presentation will explain how the TOGAF and IT4IT standards work together to provide enterprises with the ability to improve the way they deliver IT Services to the business.
The first part will explain the collaboration between Enterprise Architects and IT teams during the execution of an ADM cycle. We will discuss the fundamental role of the Service Portfolio in these interactions and our vision of how the IT4IT Enterprise Architecture Functional Component facilitates this collaboration.
The second part of the presentation will focus on how Enterprise Architects can use the IT4IT Reference Architecture to transform the IT function of the enterprise to a service-oriented operating model.
The presentation shows a high level approach on how to achieve a service
oriented delivery of healthcare services. It centers on how you can connect
services in healthcare to architecture building blocks and a simple reference
architecture that can structure and simplify the it-orchestration and
processes necessary in a transformation process.
The presentation shows what artifacts are necessary and how they relate to an
architecture model which can be used to define services, and structure how
they can be delivered. It connects service portfolio management and
portfolio lifecycle management from the IT4IT Framework and shows how enterprise
and solution architecture can be mapped to the IT4IT value streams.
In this presentation we present our view on capability-based planning (CBP) and its relation to other domains such as
strategy and enterprise architecture. We propose a method for CBP focusing on
mapping capabilities, linking them to the strategy and Enterprise
Architecture, assessing them according to several performance indicators,
determining gaps, and planning their implementation.
We define the role of
capability based-planning as a bridge between disciplines and illustrate it
via the example of ArchiPharma, representing a real, but anonymized,
Furthermore, we investigate how ArchiMate can be
used and extended with concepts and relationships relevant to CBP. Moreover
the application of the TOGAF® standard supporting CBP will also be
Why is CBP relevant? Nowadays most organizations are faced with a
more dynamic environment which means they need to undergo more frequent
transformations to stay competitive and agile. Knowledge is power. Knowing
what your organization can do (business capabilities) and what resources are
available can help make more informed decisions. Thus, having this knowledge
and a good process for strategy development and implementation can be vital
ArchiMate® 3.0 was released in June 2016. This latest version of the language represents an important evolution of the popular open standard that is used by Enterprise Architects globally. It is now possible to model the strategy of the enterprise using new concepts such as Capability and Resources, and also to model the physical world with the Equipment, Material, and Factory concepts.
Archi is an open source modelling tool that provides an open and free
implementation of the ArchiMate language. It has been downloaded many
thousands of times since its introduction in 2010 and provides a low cost to
entry solution to users who may be making their first steps in the ArchiMate
modelling language, or who are looking for a free, cross-platform ArchiMate
modelling tool for their company.
In this presentation we show that Archi has been an important enabler of
ArchiMate globally, why it's important to continue to develop and support the
tool, and the challenges faced in implementing ArchiMate 3.0. We also discuss
the importance of open source and open implementations for an open standard.
We will provide a review of progress and new features in the next version of
Archi, and progress on its implementation of The Open Group's ArchiMate
Furthermore, we will provide an example of how Open Source developments based
on Archi within Arismore have made a DevOps approach to Architecture work
possible and allowed the company to rethink their EA practice.
TRACK: Automation & Standards in ICS Systems
Process control systems have lacked some key
characteristics that we take for granted in IT, including multi-vendor
interoperability, rapid technology refresh, and the ability to easily add new
capabilities. In addition, given the cybersecurity threat to critical
infrastructure (much of which depends on ICS technology to operate), there is
a real need to enable new security capabilities in ICS systems to address the
This talk will describe the business problems faced by end
users of process control equipment, and it will also describe steps that The
Open Group is taking to create a forum focused on these issues.
In order to meet the challenges of interoperability
in the control systems area, The Open Group will be relying on lessons
learned from creating the FACE consortium and technical standard. This talk
will describe how The Open Group will be applying these lessons learned from
FACE to help create not just a technical standard, but also a compelling
business value proposition for the control systems vendor community.
Networking Dinner Event (Tue)
TRACK: Bridging Strategy and Implementation
This workshop will help attendees understand how to establish a bridge between Business Strategies and Implementation while ensuring a sustainable development for value delivery.
During this workshop, a subset of priorities, including Innovation, Prosperity and Sustainable Development, of the Canada’s Third Biennial Open Government Plan related to Geospatial Data Management will be addressed.
The following how-to steps will be explained:
Attendees will learn to:
TRACK: Open Platform 3.0 / Architecting for IoT
Intelligent Traffic Systems (ITS) are key to more efficent travelling with
lower emissions and reduced congestion. To enable sharing of relevant traffic
Information (e.g. construction sites, detours) many Partners have to
communicate with each other and their Systems have to be interoperable. This
is ensured by a current Project funded by the German Federal Highway Research
Institute (BASt), which has the Goal to build reference architectures in the
Domain of ITS.
The overall project is called „IVS“ (Intelligent Traffic Systems). The
goal of the project is to develop 3 pilot reference architectures on 3
different areas of Intelligent Traffic Systems. Later, these pilot projects
will have defined the defaults, and all companies and authorities will have
to comply to these reference architectures. During the projects, roles and
stakeholders will be defined as well as processes and technology
requirements. In a nutshell, enabling the exchange of traffic related
information (e.g. traffic jams, construction sites, delays, ..) is the
overall goal of the project.
The three areas that we are piloting are:
TRACK: EA Practice
Thanks to a 6-year background in creation and
deployment of an international architecture practice in a retail group,
will share three best practices to balance enterprise architecture with speed and
agility. I will show real examples of what have been done at the core of the
on-going omnichannel business transformation. And I will illustrate pragmatic and
concrete tools used to help business partners benefit from an enterprise
I will then illustrate the spirit that must drives
architects in the quest of efficiency and agility in their day to day job.
Cloud architectures enable a fundamentally
different approach to delivering capabilities. With less focus on
infrastructure management, architects can concentrate more on innovation.
How do you apply the rigour of an architecture methodology, without losing
the agility that you wanted from your cloud strategy? Hear how Salesforce
and our customers have evolved an approach to enterprise architecture, taking
key approaches and deliverables from TOGAF to develop a pragmatic approach to
Coffee (Wed a.m.)
TRACK: Agile Enterprise Architecture
Agility and effectiveness are one of the key success factors in modern, global economy. Everyday enterprise architects have to deal with complexity of the enterprises with many components and dependencies as well they need to assure the agile response for the changing business needs.
The participants of our workshop will be able to experience how to use agile approach together with TOGAF® framework. This workshop will combine the lessons learned from real projects with active participation of attendees, business simulation through gamification. It also will be the opportunity to exchange of the knowledge and experiences between participants.
The participants will take part in simulation of architecture project, managed using agile technique and by making proper decision they will have to accomplish project goals.
TRACK: Open Platform 3.0/Architecting Smart Cities
The major challenges of urban mobility today are emissions and lack of space.
To overcome these, we do not only need new vehicles, electric or autonomous.
We also need a new approach to content and service integration. Technically
and from a business perspective, this means openness and flexibility on many
levels where we find rigid structures today. We have to carefully balance
benefits for individuals and benefits for society as a whole.
This discussion session will consider:
TRACK: Architecture Methods and Techniques
The microservices architectural style has significant benefits in enabling
agile software development and delivery of large and complex enterprise
applications. However, as the number of deployed microservices increases, new challenges arise. These challenges are not apparent in monolithic applications. For instance, many small microservices will lead to significant increase of deployed units to manage. Typically, these microservices will
both expose and consume services. This will result in an ecosystem of
microservices talking to each other. Some of these microservices will even
expose an external API.
The microservices architectural style leads to a
dynamic system landscape – new microservices will be deployed, old ones
will be replaced or removed more rapidly and new instances of existing
microservices will be launched to cater to the increasing load. Lastly, the
mean time between failures will decrease. With larger count of small
deployable units, the probability of one or more such units failing will
increase compared to a system landscape with a few big monolithic
This will lead to a number of important considerations: What are the microservices, and where are they deployed? How are they configured? Are the configurations correct? How to keep their routing information updated? How to prevent cascading chain of failures? How to confirm that all microservices are healthy? How to ensure that only the required APIs are exposed externally and how to ensure that they are secure?
To address many of these questions, new operations and management functionality is required in a microservices-based system landscape, and with it new patterns have emerged.
Dipanjan will present a prototype of an open standards-based platform for microservices design and delivery that will help enterprises adopt the Microservices Architecture pattern, including the design and development of not just the microservices but also implementing the typical patterns and infrastructural service components necessary for addressing the challenges that this new architecture paradigm presents, using the technology of choice. The platform additionally enables the enterprise to expose the relevant microservices as well-formed and secured APIs.
Dipanjan will discuss the relevance of this framework in light of the emerging Open Platform 3.0™ standard.
Enterprises are complex and dynamic by nature, yet our approaches have been
largely treating them as static, deterministic and mechanistic entities. As
architects and analysts we work with outdated models, as designers we try to
shape dynamic brands through static style guides, technology solutions are
confined to restrictive platforms that fail to smoothly accommodate the
diverse and unexpected.
What if we strive to co-create a dynamic system to reshape the enterprise?
Nicolas and Milan will give an insight into eda.c’s ongoing quest for a
systemic platform: a solution that would implement the enterprise’s
ambition from its long-term core idea down to the diversity of users, in
changing conditions both inside and outside the enterprise.
TRACK: Open Platform 3.0™/Information from the IoT
Most current Internet of Things strategies and implementations still seem to focus on the installation of sensors for "everything" and collecting as much data as possible from them. The assumption is that there is huge hidden value in the collected data, which just waits to be analyzed and distilled into golden nuggets of information and knowledge. In practice, this is difficult because the usability of collected data tends to deteriorate over time. It is also rare that data would be "labeled" properly with the context in which it was created, thereby making it unfeasible to do any useful analysis on it.
This presentation shows how to collect and label data based on context and, in particular, shows how to use gained information for providing context-based services to users. Smart City and other "smart" environments and systems are used for showing how such context-based services create value for end-users, as well as for the companies providing such services.
The Data Lake paradigm is gaining in popularity as an approach to storing and analysing data. The Open Group is developing an Open Business Data Lake technical standard, containing key concepts, architectural patterns, principles and other reusable artifacts and guidance. This presentation will give an overview of the data lake concept, based on the material being developed by The Open Group, and discuss its use for data garnered from the Internet of Things.
In this session the findings are presented with regards to the use of
Industrial IoT reference architectures within batch controlled (food
& beverage) manufacturing environments. First an IIoT reference
architecture model is shown, which positions
the data lake from an S95 perspective, distinguishing between different
enterprise and shop floor levels using the S95 standard. This model is
then used to derive and assess an application roadmap based on input
from several manufacturers.
Smart cities are an application of the Internet of Things, and collection of vehicle information is a specific use-case of that application. How do the data collection, labeling, storage and analysis techniques presented during the day meet its specific requirements? How far do they meet the needs of the Internet of Things in general?
Particular questions include:
This concluding discussion will build on the earlier sessions and consider the question of how to architect systems to gain useful information from the huge amount of data that is generated by the Internet of Things.
To start the session, there will be a presentation by Don Brancato on
the need to correlate information related to events, to give business
people an understanding of what is happening, and determine when a
multitude of small occurrences indicate that something major has
A panel of experts will then discuss correlation and
understanding of data generally, with members of the audience also
invited to input questions and make points.
The discussion will be
moderated by Open Group Director of Interoperability Chris Harding.
TRACK: Architecture Methods and Techniques (cont.)
This talk aims to demonstrate how various traits of architecture work are
essentially about simplifying some kind of complexity. The end goal of this
simplification will be to enable comprehensible communication of the
structure and dependencies within some problem area to different stakeholder
The talk will refer to several real-life case study examples from
architecture work at different abstraction levels targeted at different
stakeholder groups including technicians, business executives and end users.
Finally, it will be shown how this understanding of architecture as
simplification has been successfully applied to build and operationalize a
tailored TOGAF-based architecture framework and governance model across a 1BN
$ international IT service provider company.
Communication is a very important part of our life: engineering, work,
processes, family – everything is improving thanks to right communication.
Community provides us opportunity for networking and communications, it helps
us to grow up and develop, gives us more freedom and space. Participants can
satisfy primary human being need – sense of belonging.
During our talk
we’ll share how community can facilitate Enterprise and why is it so
important for EA professionals and Management.
Co-presented by an active Enterprise Architect and a Community Manager.
A determinant factor in transforming a traditional business environment into an innovative and lean architecture blueprint is the role of the applied patterns, services and building blocks. Such a transformation should be assisted with an efficient transformation and architecture framework like TOGAF that includes a patterns, services and building blocks assembling concept - where such concepts can change the transformation project’s outcomes and make the architectures transcendent.
The enterprise architect’s role is crucial for the finalization of the
implementation phase of the very complex business transformation project.
During this phase the enterprise architect’s knowledge is determinant to
design and implement the end-system. There is a need to build a concise
patterns, services and building blocks composite model; shortly a
“holistic brick”. A holistic brick is a composite model that can be used as a
template for a variety of architecture transformation projects, using methods
This research phase’s focus is on the various technology
and methods that can support a holistic architecture. The theory and concept
of composite patterns suggest that implementers must be able to reuse proven
components that emerge from the best architecture and modeling practices in
order to solve generic architecture implementation requirements. Composite
patterns promote the concept of design patterns, services building and
solution blocks. Without the use of composite patterns enterprise architects,
business analysts, designers and implementers would be poorly applying
architecture and modeling techniques; and that can result in the target
business system failing to deliver.
TRACK: TOGAF® 9
Architecture Projects are typically complex in nature. They need proper Project Management to stay on track and deliver on promise. This presentation is intended for people responsible for planning and managing Architecture Projects. We explain how the TOGAF® Architecture Development Method (ADM) can be supplemented with de facto methods and standards such as PRINCE2® or PMBOK® to strengthen Project Management and improve the probability of success for Architecture Projects.
This presentation will provide Architecture Project Teams with an overall view and detailed guidance on what processes, tools, and techniques of PRINCE2 or PMBOK can be applied alongside the TOGAF ADM for project planning, monitoring, and control.
The presentation is will be summary of the the all findings that were described in the white paper: “Architecture Project Management - How to Manage an Architecture Project using the TOGAF® Framework and Mainstream Project Management Methods”. This white paper was the collaborative effort of the companies such as Architecture Centre Ltd, EY and IBM. The presenters are co-authors of this publication.
The purpose of this initiative is to have a Payments Overarching Solution or
logical framework to start a program of further integration of systems,
provide greater visibility of transactions, decrease people dependency,
enhance Operations efficiency, and reduce Operational Risk exposure.
The approach taken was to document the AS-IS landscape, identify the pain
points and drivers, and define the TO-BE, develop a strategic roadmap which
prioritizes the solutions to problems across short, medium and longer
The approach will provide a unified and integrated ‘big picture’
framework to align and inform information technology investment planning and
implementation—program and project management—with the business strategy.
High incidents of customers’ complaints and delays.
Lack of business rules checks and other validations.
Extensive manual and paper based processes.
Absence of daily monitoring and audit trail.
Information security gaps.
Auto-notifications system to the customer.
Customers’ files automatically captured across all eligible channels.
Paperless customers’ reports via email.
Centralized business rules engine.
Integrated workflow of end-to-end business processes.
Customer reporting preferences.
Real time process monitoring including dashboards.
Reduce risk of changing customers’ instructions.
Case-Study and success stories:
Coffee (Wed p.m.)