PLENARY - IT4IT™: Managing the Business of IT
TRACK: IT4IT™ In Practice
Good Reference Architecture is an accelerator. It will speed an enterprise
architect to end-of-job and increase confidence in the target.
This session examines using IT4IT as a Reference Architecture answer the
questions: Does it accelerate a good EA? Does it increase confidence in the
We'll discuss three examples of changing the IT business: a bank, a capital
intensive energy company and an insurance company. We'll examine how we used
IT4IT, the work to align it with an existing EA Framework and its
applicability supporting substantive change.
Used as a reference IT4IT provides the basis of a capability, process,
service, application & information model. When astutely aligned with a proven
EA content framework (Conexiam's Navigate) and score-based Portfolio-level
architecture approach IT4IT accelerates the EA journey. We obtained
simplification in high confidence gap analysis and crucial trade-off
decisions in roadmap development.
This talk highlights seven dimensions in which
IT4IT can add value to any EA or strategic transformation effort, including
lessons learned in my leadership in 2014-2015 -- using IT4IT as the starting
point -- in the creation of two related but distinct enterprise-specific
models: (a) An Enterprise IT Operating Model to be used as a template for
creating strategic transformation road maps across the whole scope of CIO
responsibilities; and (b) A functional model to be used as a template for
rationalization, alignment and future-state planning for IT tooling across
the value chain. Both work products are currently in use as intended.
talk will not identify the specific organization, but will describe seven key
benefits of the approach taken, with practical examples, and include some
best-practice learnings based on this effort.
The talk will be based on --
but will not be identical to -- an article on this subject currently being
considered by the Journal of Enterprise Architecture.
We are at a crucial moment in time where the very fundamental of how enterprises use technology is metamorphosing. Technologies and mobility are giving birth to disruptive business practices and changing the rules of the game at a blinding pace. Today, the world’s largest virtual store generates more profit than the biggest brick and mortar chain store; the largest hospitality provider does not own a single room; the largest transport provider does not own a single car.
The traditional role of IT as a provider of technology and fixer of issues is no longer sufficient to stave off competition from a start-up who would use a credit card to rent IT Services and exploit another company’s valuable people, infrastructure, applications, management and logistics resources. In such an environment, there is a need for a new way of doing things. Early adopters of the Plan-Build-Run and Broker-Integrate-Operate, IT operating models are progressing towards enabling themselves to operate in the new world order of cloud, telephony, SAS even as they create new paradigms for engagement with their customers as well as their service providers.
This paper discusses a real life intervention with the objective of building, in-house, ITSM EA Capability required for examining and constructing a capability based architecture; for a technical function to operate in a SOA mode and manage the supply of IT services to business as a supply- chain driven by outcomes.
The initiative uses the IT4IT Reference Architecture, flavoured with the FlexModeIP Continual improvement ITSM SOA framework to define process roles and uses the Skills Framework for the Information Age (SFIA) to create a ‘Capability Calibration Engine’ that can objectively define required customer focused capabilities, enable the Self-Assessment of the capability of the people, Identify Gaps, take Learning and Development actions using the 6 Disciplines of breakthrough learning; to systematically fill these gaps, meet the needs of the business, while enabling people to better identify and reach personal aspirations.
Value stream mapping (VSM) is a technique that can be
used to enable a DevOps transformation. It allows you to see where the
bottlenecks and inefficiencies are in your delivery pipeline. If you think about the IT4IT Reference Architecture, a VSM
exercise would touch all the component areas of Plan, Build, Deliver and Run.
collaborative workshop session, you will learn how to develop a value stream
map of your delivery pipeline in line with the
IT4IT operating model, identify obstacles across it, target DevOps
practices that address your specific needs, and develop a pragmatic approach
to get started. The key to success with DevOps is identifying what to
automate, how much to automate, and what to measure!
TRACK: Security Practice
Trusted Platform Module / Trusted Execution
Technology (TPM/TXT) provides advanced hardware based security, root of
trust, geo tag location, and helps deliver compliance reporting. However,
integrating TPM/TXT into OpenStack is not for the faint at heart and requires
changes to your cloud DevOps.
Consumer and Enterprise IAM have quite distinct requirements and solutions.
We are seeing a significant growth in Consumer IAM solutions as this becomes
one of the key enablers to providing the necessary customer experience to
securely grow digital business.
On the one hand, separate implementations are typically owned and operated by
different areas of the business, to completely different architectures, and
progressing at different speeds. However, at the same time we also seeing a
blurring of boundaries between Enterprise and Consumer identities, systems,
devices and policies that increasingly necessitate an integration and
co-ordination between these two worlds.
1. This presents an architectural conundrum – just how distinct should
organisations treat these two worlds?
2. What are the realistic opportunities and possibilities going forwards
around a more ‘Unified IAM’ approach?
3. What business and technical architectures exist, if any, to address this
4. How might ‘game changers’ like IDaaS impact this issue?
This presentation explores this topic.
It recommends how organisations might move forward to address these issues in
the short, medium and long term.
TRACK: Professional Development
This presentation will talk about how Philips IT
has embraced The Open Group Open CITS Framework to enable competency development. It
will contain details about how The Open Group philosophy is now an integral part
of Philips Competence Development Framework, what benefits we have reaped,
the current challenges, improvement areas as well the way forward.
The same technology trend that gave rise to enterprise architecture threatens
to paint it into a corner. This talk considers the role that distributed
information processing has played in the genesis and evolution of enterprise
architecture, and how the logical culmination of distribution will likely
relegate enterprise architecture to the “back office”, supplanted in the
“front office” by newly fashionable approaches like design thinking and
In response to this scenario, the presentation enumerates 28 essential ideas
that frame an alternate concept of enterprise architecture, one that, by
applying to all forms of human endeavor, frees itself from the vicissitudes
of information technology and subsumes design thinking and enterprise design
under a broader and more inclusive umbrella.
These ideas include thinking of design as the specification of constraints on
downstream decisions, the central role of people in design, the importance
of considering making and using things (the reasons we design) as an integral
part of the design process, the kinds of things we have to consider designing
making and using when we undertake any form of human endeavor, the kinds of
errors we can make when designing, making and using these things, the idea of
architecture as a very special kind of design, and how the ideas of mission,
solution and environment relate to these concepts of design and architecture.
TRACK: Security Standards
New ISO standard helps assure more secure products and safer operating environments!
Learn about the cybersecurity and supply chain risks that plague the IT products your enterprise depends on. Understand the simple steps you can take to mitigate the risks of tainted and counterfeit parts from making their way into IT products and into your operating environments.
The Open Group recently announced that its Open Trusted Technology Provider™ Standard – Mitigating Maliciously Tainted and Counterfeit Products (O-TTPS) was approved as an ISO/IEC International Standard (ISO/IEC 20243:2015).
The standard is one of the first aimed at assuring both the integrity of commercial off-the-shelf (COTS) information and communication technology (ICT) products and the security of their supply chains. The O-TTPS Accreditation Program identifies Open Trusted Technology Providers who conform to the ISO standard.
This session will focus on cybersecurity and supply chain risks, how the standard and the accreditation can address them, and what steps you can take to assure products you buy are more secure and your enterprise is safer.
Mils is the emerging Open Group standards for a modular approach to critical system construction and assurance. Mils is a component-based approach to dependable systems design and implementation that encourages an ecosystem of commercially available components and services for the cost-effective development and certification of critical systems. Mils can be understood as a two-phase approach: design
of an architecture (policy architecture) that achieves the system purpose,
and implementation and deployment on a robust resource-sharing platform.
The Open Group has served as host to the activities of the Mils Initiative for a decade and a half. The Open Group and its members have engaged in Mils research and development projects, and The Open Group is actively pursuing the advancement of Mils technology through several projects. The Critical Systems Forum (previously Real Time and Embedded Systems Forum) of The Open Group seeks to create a set of standards under the name Mils™ that will enable the community to achieve the consistency and interoperability goals implicit in the Mils™ Ecosystem objectives.
In this presentation I will describe the past and present activities of the
Mils Initiative, including concepts and research results throughout the
community. Since the development and assurance of critical systems is a
challenging technical activity, I will summarize the key technical results
that contribute to our optimistic outlook for Mils. I will then outline plans to develop the set of Open Group Mils™ standards, and to stand up an
evaluation and certification support scheme to serve the Mils Community.
TRACK: EA Practice
Often Enterprise Architecture teams find it difficult to deploy their master
plans and designs at the project level and
have development teams align to and comply with an overall EA vision. Agile
development approaches are gaining popularity and as a result EA is often
skipped and overlooked as the need to deploy working software quickly
The scaled agile framework addresses this problem and has been
developed specifically to allow very large organizations to deploy agile
practices at scale, across multiple program areas. Linkages between EA teams
and development / devops teams have been explicitly defined and this talk
will demonstrate how a TOGAF oriented EA group can work within the framework
to directly influence agile software efforts.
EA has been legislated and in use a strategic
business function for more than 30 years, yet its use is still overwhelmingly
in the CIO IT domain, often relegated to technical architecture. In
retrospect a new (old) approach would be useful where EA is considered as a
widely used business technique rather than a stand-alone CIO or business
This presentation examines this approach and how the presenter
successfully used EA as a business technique (while in plans and portfolio
management) to conduct what now would be called architecture based planning
for a massive business transformation.
Networking Reception (Mon)
Members Only Meetings
Plenary - Enabling Digital Business
Digital Health Platforms (DHPs) propose new and improved ways to health and
health services at reduced cost. Digital Health Platforms utilize the
fast-growing web of sensors, wearables and mobile devices along with
internet-based technologies and services in connected care settings. They
capture and manage a person’s health information across episodes of care to
provide new insights and advanced analytical capabilities – to aid in the
prevention of diseases, promote healthy living and to help diagnose and treat
However, can they deliver on their promise?
This presentation provides an introduction and overview of the market for
DHPs. It outlines major platform vendors and their market focus. After an
introduction into the required capabilities within and across DHPs, we will
briefly discuss how Digital Health Platforms relate to concepts and
technologies such as Electronic Health Records (EHR) or Health Information
We will then outline the major elements and building blocks of a Reference
Architecture for DHP in the context of existing and potential future work of
the Open Group Healthcare Forum.
The government of Madhya Pradesh (MP), India in 2006, launched “Janani Express Yojana” (JE), a decentralized, 24X7, free emergency transport service for all pregnant women. JE vehicles were well dispersed across the districts and used by 50.03% mothers of which 47.03% took >2 hours to reach a medical facility. As per medical research most of the emergencies/casualties happened when woman in labor takes more than 2 hrs to reach medical facility. The primary reason for this delay is system is manual and currently run through call centers having un-skilled / un-aided employees.
In this paper we have proposed a TOGAF9 based boundary less data flow architecture between Call Center system, Emergency Vehicle system, Medical facility system, Non Governement Organisation system and GIS system to guide call center employees, emergency vehicle drivers, health care volunteers and patients to avail faster emergency vehicle service and quick drop at nearby medical facility. The architecture model could be generalized and extended to other emergency transport systems in resource constraint settings like India.
TRACK: Open Platform 3.0™
Today's trend is digitalisation and it affects us everywhere and all the time. It challenges the owners and leaders of existing businesses and sectors because there is so much new technology available and the pressure comes from every direction to exploit it.
Internal users, customers, external partners, competition and legislation all have their demands and expectations, but are often limited by the established business models, culture, processes and "way of doing things".
In this presentation I will share experiences from an innovation project that started with the idea and a business case for the creation of a "web portal" to support a network of medium and small companies delivering occupational health services, that have now matured in a more Digital Business Customer eXperience (DBCX) direction.
Based on work done in the DBCX Work group in The Open Group which is a collaboration between the Architecture Forum and the Open Platform 3.0 Forum, a more customer centric and architected approach was proposed for the sponsors of the innovation project.
Together with the project manager I have introduced the Digital Business and Customer Journey concepts to more than 20 key resources and decision makers in the four leading occupational health companies, and now have a different focus in the innovation project.
The project matured from IT-centric to business- and customer-centric and can have a much wider impact on the future of the occupational health service providers and their ability to deliver great customer experience and improved business results.
With the world becoming increasingly digital, we are experiencing one of the
most fundamental shifts in human history. Business are transforming into
experience delivery platform, radically moving away from traditional product
/ service based business model. Hence, crafting and realising transformative
vision centred around customer experience became pivotal.
In effect, “Digital” is a lifestyle, significantly different way of
working and collaborating, which demands fundamentally different capabilities
leading to a new business model altogether.
With empowered consumers taking charge of the steering wheel and dictating
norms, there is an unprecedented demand and expectation for integrated
services mapped to consumer life-cycle events - the customer journey.
To be successful and relevant, digital business must be carefully architected
to become preferred platform consistently delivering outstanding customer
experience. Architecture of future digital business would be concentric,
cohesive and adaptive, seamlessly marrying outside-in and inside-out
This session will focus on the differentiating aspects of digital
architecture, along with an integrated approach of business design.
takeaways and learning from the session includes, but is not limited to:
The operation of an extended enterprise, or other
group of collaborating enterprises, is typically supported by a number of
data processing systems that exchange data. These systems may be operated by,
and have been developed by, different organizations. The organizations
operating and developing them generally use different terms to identify the
data elements. Substantial effort is needed when programming and configuring
a system to determine how data elements supplied by other systems should be
interpreted. This effort is reduced by use of the recently published Open
Data Element Framework (O-DEF) standard by the Open Group.
provides an overview of the new standard.
This talk introduces the key concepts for the Open Business Data Lake
(O-BDL), as a first step towards a Reference Architecture. By describing a
set of architectural patterns, principles, and other re-usable artifacts and
guidance, it intends to help organizations leveraging new disruptive “Big
Data” solutions and setting up an associated “data-centric” strategy
for an increased performance and competitiveness.
This workshop will show you how the realization of your business strategy can be supported by a combination of strategy modeling, capability-based planning, enterprise architecture and portfolio management.
Enterprise architecture is at the heart of organizational design. It provides a clear line-of-sight between strategic goals, business capabilities, operational services, processes, and systems, and the project and programs that realize these. Enterprise architecture models in ArchiMate® are the backbone of our approach. These enable you to manage the various dependencies and risks involved in realizing your strategy, ensuring coherence across the enterprise.
Strategy models such as the Business Model Canvas add to this the ability to formalize and focus the business strategy, and they are geared towards communication with business stakeholders. Capability-based planning is centered on realizing strategy by focusing on what an organization can do, rather than how it can do this. With this, business leaders can plan organizational change based on business outcomes, rather than projects, processes and applications.
Enterprise portfolio management supports prioritization and decision making on the requisite assets and change initiatives that realize the envisaged architecture and capabilities. We will show how you can relate data from financial and other systems to your architecture models and manage the elements in your architecture in portfolios. Decision makers are supported by various customizable dashboards that visualize costs, risks and business value at different levels. Decisions on these portfolios, in turn, are validated using the underlying architecture models, thus closing the loop to the organization’s strategic goals.
We will illustrate this approach to strategy execution with two real-life case studies:
We will describe how this entire trajectory of strategy execution is facilitated by an integrated software solution for describing and managing your strategy, capabilities, enterprise architecture, and portfolios.
Archimate is fit for purpose as an Architecture Description Language(ADL). The standard supports the use of attributes. How can the Open Fair ontology be used to visualize risk in an architecture repository by adding values to the attributes?
TOGAF has a set of inputs, steps and outputs in the ADM. What are the risk and security related items?
This presentation will explain how a security architecture practitioner used TOGAF, ArchiMate and Open FAIR to communicate privacy and security concerns in a business context.
The presentation will also give a teaser and some insight in using agile methods supported by GitHub and Taiga.io.
ArchiMate has been receiving increasing attention
througout the past years. Still, there are not many field reports available,
and discussions in the community have been revolving around the quest for
adequate and effective ways of using ArchiMate. This includes aspects such
as, e.g., for what specific purpose and at what level of granularity to model
architectures using ArchiMate and for what target audience to create
ArchiMate views. This presentation provides an overview and analysis of
different cases of using ArchiMate as present in some user organizations in
Germany and Austria. It outlines and consolidates the different approaches
and derives some good practices.
TRACK: TOGAF® 9 Tutorials
TOGAF® describes a set of industry standard best practices for implementing and operating an enterprise architecture capability. The BABOK similarly describes the same for a business analysis capability. While each of these standards is directed towards different professional communities, they both describe common areas of interest where the two professions can clearly collaborate.
First, the Architecture Development Method (ADM) is grounded in a common set of Architecture Requirements Management activities that aligns with the Requirements Management and Communication knowledge area in the BABOK. A big part of Phase A: Architecture Vision is related to eliciting requirements from architecture stakeholders which can be supported by the BABOK Elicitation knowledge area. When describing the baseline and target architectures in Phases B-D, the architecture project is also supposed to be collecting requirements for the architecture. During Phases E-F, when gap analysis and planning occur, the Enterprise Analysis and Requirements Analysis knowledge areas can be applied, along with Solution Assessment and Validation.
The speaker will discuss how enterprise architects and business analysts can effectively collaborate by integrating the two practices.
Digital transformation is more than technology. It means innovation to
connect technology, data science, devices, design, and business strategy to
change a business process or customer experience.
Digital transformation means putting the customer, device, organization, or
business process at the center of real change in how we engage, create,
build, and buy.
This can be truly achieved by adding digital extensions to the TOGAF meta
model in order to support Digital Ecosystem and Digital Transformation. This
paper will describe what digital extensions are and how we arrived at them.
TRACK: TOGAF® 9 Case Studies
Early 2014 a core team of Zurich Architects embarked on restructuring
enterprise architecture in Zurich. Zurich is global insurer with a federated
organizational structure where business units have autonomy and act like
Our challenge was to create a global architectural governance practice,
establish methods and tools, standards and reference architectures that would
align these disparate business units. Our goal was to increase EA maturity
from (current) Level 1 to Level 4 across the group, while in parallel
developing reference architectures to support our organization on it's
digital and cognitive journey. Our digital strategy benefited from the
structure of ADM Togaf and we addressed our cognitive challenges using the
transition architecture approach from Togaf.
This talk will cover challenges in adoption, approach taken, TOGAF
methodology, lessons learnt and next steps.
The Genesis Housing Association is a charity that provides both social and
market rate housing, and a range of care and support services, for more than
100,000 people across London. It was formed through the merger of three other
housing associations in 2011, and has a staff of 1500 people. Government cuts
have taken tens of millions of pounds from the Genesis’ budget, and in the
coming months, it will merge with yet another housing association.
Michelle has recently been appointed as Genesis’ Enterprise Architect. TOGAF
has been adopted as the architecture framework, and the
pressure is on to establish an enterprise architecture capability, to
determine a baseline architecture for Genesis, to prepare the organisation
for merger, and to find efficiency savings to offset the budget cuts.
Networking Dinner Event (Tue)
TRACK: The Internet of Things
The relatively recent global interest in the Internet of Things (IoT) concept has resulted in the creation of IoT initiatives within all major standardization organizations. Most such IoT initiatives are currently specifying IoT reference architectures based on ongoing requirements identification efforts. An important part of that work is also identifying potential standardizations gaps in those reference architectures.
The standards published by The Open Groups' IoT Work Group, the Open Messaging Interface (O-MI) and Open Data Format (O-DF), are the result of a similar standardization gap work that started around 2002. Over the years, O-MI and O-DF have been applied to most application domains with tens of different organizations.
In the recently started BioTope EU Horizon 2020 project, O-MI and O-DF are being used for implementing Smart City use cases with the target to create viable business IoT ecosystems, also contributing to the work and future standards of The Open Group's Open Platform 3.0 initiative.
The Industrial Internet Reference Architecture (IIRA) is an important
resource in the consideration and discussions about the Industrial Internet
of Things (IIoT) around the world. Developed with broad industry consensus,
the IIRA was built to drive product interoperability and simplify development
of IIoT systems that are better built and integrated with shorter time to
market and, at the end, able to better fulfill their intended uses. This
Reference Architecture is a statement of what the most important IIoT
architecture components are, how they fit together and how they influence
each other. It reflects consensus on major architecture questions among
participants from energy, healthcare, manufacturing, transportation and
This presentation will explore the IIRA to help the audience better
understand it’s message, it’s organization, the technical requirements it
describes, and methodologies and roadblocks to IIoT adoption. Current work
being done to build upon the IIRA and a preview into proposed IIoT standards
that may need to be adopted by standards organizations in the coming years
will also be discussed.
The World Wide Web Consortium’s (W3C) mission is to develop open web
technology standards to lead the Web to its full potential. Our aim is to
expand the Web from a Web of Pages to a Web of Things. The IoT suffers from
fragmentation due to non interoperable platforms and a bewildering variety of
technologies. We want to counter this fragmentation through the introduction
of an abstraction layer for “things” that sits on top of existing
platforms and standards, and as such defines a platform of platforms.
Application development is simplified by decoupling the lower layers in the
communications stack. Things standing for physical entities (whether
connected or not) or abstract entities, are exposed as software objects with
properties, actions and events. These can be for local things or act as
proxies for remote things. Platform developers take care of the bindings to
specific protocols, data formats and encodings, along with the communication
patterns as appropriate to the requirements as indicated by the metadata
associated with the “things”.
W3C has extensive experience with semantic technologies and we have defined a
widely used suite of associated standards. Every “thing” in the Web of
Things is named with a URI in keeping with Tim Berners-Lee’s vision for the
Semantic Web. Thing descriptions include data models that servers interpret
to create the software objects for use by applications. Other metadata
describes the semantics as needed for semantic interoperability. Further
metadata is needed for security and communications.
We’re looking for help with defining standard vocabularies, APIs and
protocol bindings, security, privacy and resilience, along with enablers for
dynamic open markets of services including discovery, automated negotiation
of prices, terms and conditions, provisioning, payments and support
throughout the product lifecycle from design to obsolescence. The Web of
Things Interest Group is preparing the way with work on use cases, and
requirements, technology landscape studies, an emphasis on implementation
experience, and preparations for chartering a Working Group to take this
forward along the W3C Recommendations track.
The ISO/IEC JTC1 Working Group 10 is responsible for creating Internet of Things (IoT) international standards.
The core standard currently under development at WG10 is the IoT Reference Architecture, ISO/IEC 30141. The Reference Architecture aims to give
a high level view of IoT systems - the various components involved, how they relate to each other and how IoT systems are put together from those
Mike's talk describes the various elements of the ISO IoT Reference Architecture and the different viewpoints that are shown in the architecture,
starting with fundamental concepts such as Physical Entities, the Sensors and Actuators which interact with the physical entities, the local and
wide area networks that connect IoT devices to applications and services - and the applications and services themselves and how they relate to
cloud computing, edge computing and end-user devices such as smartphones.
Consideration is given to the major topic areas of Security, Data Protection (sometimes call Privacy) and Management of IoT systems, all of which
span all the elements of the IoT system.
Building on earlier presentations from this track, we have three workshop sessions that will look at the requirements for standards and produce an overview map of the overall IoT standards landscape.
14:00-15:15 Vertical Application Areas of the IoT
The Internet of Things is the basis of many "smart" topics: smart homes, smart cities, smart healthcare, smart manufacturing, and smart agriculture, to name but a few. This workshop session will:
16:00-16:30 What Are the Roadblocks for the IoT?
The IoT is developing very rapidly but there are always roadblocks that delay the full realization of a new concept. Once identified, they can often be removed by concerted action of the organizations concerned. This workshop session will identify the current roadblocks for the IoT. It will:
16:30-17:30 The IoT Standards Map
Many of the major IoT standards initiatives will have been presented during the day. This final workshop session will discuss:
The IoT Standards Map emerging from this discussion will be the key result of the workshop.
TRACK: EA Practice (continued)
As a Solution Architect, I participated in many successful (and not so successful projects, and I learned some interesting lessons on communication between the client's EA and the solution team. It might seem like insignificant detail in comparison with activities such as strategic planning, preparing PowerPoint slides for the Board, or putting efforts into polishing your governance; however, I would not underestimate the impact of Solution-related phases to the overall EA practice success.
Tips and tricks in building appropriate communication between EA and SA based on practical experience; positive and negative examples from both sides are in the spotlight.
The aim of this presentation is to highlight the
importance of engaging young professionals and how knowledge sharing can
improve the quality of work and also the organisation as a whole.
I will go
on to introduce what sort of level of knowledge young professionals should
have and what has helped me thus far. Furthermore, how can (non-young) IT
professionals take on the responsibility of a mentor.
TRACK: Architecture Methods and Techniques
This presentation will examine how the TOGAF and
IT4IT standards can work together to create and deliver value to the
enterprise. Although the two standards are different in their scope and
focus, both seek to enhance the value of enterprise. They have different
approaches, but similar goals.
This presentation will focus on highlighting
the areas where the standard intersect, and how to address the differences in
a positive approach.
Ever struggled with the question, What is the Value of Enterprise
Architecture? In this facilitated conversation, Michael Fulton will share his
perspective on Enterprise Architecture and the value it provides to the
CIO, to IT, and to the business.
Come ready to engage, because in the
conversation we will discuss:
At the end of this conversation, you should walk away with:
The next stage of technological evolution will
involve using artificial intelligence to solve problems that currently are
either too complex to solve, takes too much time or is prone to human error.
This, along with the ability to give the customer an extremely personal
experience, makes A.I a vital capability in your organization.
presentation we will discuss some of the key heuristics, building blocks and
challenges associated with building an A.I capability within your
In 2015 Kuehne + Nagel initiated a project together with the
University of Hamburg (ITMC department) to evaluate semantic web tools
for Enterprise Architecture Management (EAM).
For the evaluation, a business demand from contract logistics was
The goal is to optimize the incident management for IT failures in the
warehouse and transport management process. An ontology was defined
that combines information from the extended enterprise (partners and
with information from different enterprise architecture domains, like
warehouses, business and IT organization structures, application
components, infrastructure devices and severity definitions. Data for
a selected use case is stored in an RDF database and analyzed for
different incident cases with a modern web user interface (AngularJS,
Bootstrap) and SPARQL queries.
The presentation will give a short introduction of the relevant
semantic web technologies (RDF, OWL and SPARQL) and how they relate to
the information management for enterprise architecture. We will show
what semantic web tools we selected with the applied selection
criteria’s. For the ontology modeling Protégé is used. We will present
the OWL2 ontology in Protégé and discuss the experiences that we made
during ontology design so far. We will also talk about the integration
of data from EAM tools. Finally we will show a demo of the evaluation
The presentation will conclude with a summary of our experiences and
an overview of our evaluation results. We will give some information
where we are at this point in time and give an outlook of our future
plans for Enterprise Architecture and Linked Data.
Most EA teams now need to collaborate on data and models across multiple
locations and time-zones.
They are under pressure to stay on top of a process of continual business
transformation and reinvention.
Dr Tim O'Neill will discuss how organizations can take steps to implement a
clear digital business strategy in real-time, using the latest enterprise
architecture techniques including multiple architecture analysis, roadmapping,
and algorithms geared for complex business ecosystems.
Open Sessions (Wed)