The Power of Business Events
Situational Awareness – A Business Objective.
Aggregated enterprise architecture wisdom
Situational Awareness – A Business Objective.
Following my previous blog on Working With Projects & Dependencies I wanted to say a little on working with deliverable’s and avoiding some pitfalls.
In this article, I would like to discuss the critical importance of connected healthcare systems during an epidemic or a pandemic. Everyone benefits from connected healthcare systems; people, families, districts, states, nations. Leadership from all levels of healthcare authorities is essential, from hospital workers to governments, to global organizations such as the World Health Organization (WHO).
By Myles Suer, #CIOChat Facilitator, CIO.com Contributor, and Dell Boomi Head of Global Enterprise Marketing
Many years ago, I was asked to review an early draft of ITIL Version 3.0. I remember even taking the draft service strategy book on vacation with me. My wife asked me at one point why I was getting so excited about a ‘tech manual’ while she said that she was reading something truly exciting, a romance novel. In the end, I made many comments and suggestions as a business strategist. Most did not get accepted.
This blog talks about requirements in the context of architecture design – including their importance and some bare minimum needs.
In this time of the Covid-19 pandemic and the associated extreme economic disruption we’re all experiencing, the imperative to move rapidly toward digital products and business models is becoming both clear and increasingly urgent.
Recently, the Banking Industry Architecture Network (BIAN) published version 8.0 of its financial industry reference architecture. This provides a comprehensive model of the business capabilities, business scenarios, service domains and business objects used in banking and other financial services.
To reopen business and society after the COVID-19 lockdown a fine-grained approach is required to selectively enable movement for people. Right now, governments and organizations around the world are working on technology solutions for tracing contacts of people who have tested positive for COVID-19 and enforcing quarantine for those people (also for new arrivals to […]
The post Gamification Can Flatten the COVID-19 Curve appeared first on Brian Burke.
Like many of technology’s better creations, the IT4IT™ Reference Architecture standard was born out of necessity.
The IT landscape is continually shaped by innovation. Despite that being a cause for celebration for consumers and end-users, the introduction of these new technologies – such as the mainframe, the PC, client servers, the Internet, cloud computing, IoT, etc. – meant that the IT function had, effectively, lost track of what it needed to manage and control.
An open standard architecture-based approach to managing the business of IT was needed. This would have to be a holistic, end-to-end, service-based description of everything the IT function needs, and to be a good steward of all the IT components, solutions, and services within its remit. It was this issue that set in motion the train of events that brought us to where we are today. But there are no grounds for complacency. The work continues.
Even today the complexity and pervasiveness of, and the dependency on, IT systems continues to grow. In many cases, in many organizations today, the management solution is a loose collection of siloed processes. We are still not paying enough attention on how to remain in control. That is why the IT4IT standard is such an important instrument to manage IT, and why we have chosen to document how it came to be.
In this second article, I discuss key ideas and concepts underlying the design of a Reference Architecture for Health. Based upon the principles developed in the first article, these ideas and concepts describe what is needed. Together with the essential capabilities that we will introduce in a third article, they provide the input to how to build and deliver such a Reference Architecture. This document uses the following approach:
– From the large to the small: Start with the outer context, the overall Healthcare system, and refine into individual subject areas and building blocks
– Outside in: Start outside the organization, from the perspective of a customer, and design your organization around the needs of the customer
In this article, I’ll share guiding principles for a reference architecture for the Healthcare industry. The main beneficiaries of this reference architecture are patients, health professionals, and Healthcare organizations. Its main users are planners, managers, and Enterprise Architects. A second article will focus on key design ideas for such a reference architecture, followed by a third article to describe its essential capabilities.
Our massive use of IT (the information revolution with its information inertia and its fast but stupid behaviour) is enabling our innate behaviour to surge against our learned behaviour and that is severely damaging the social structures we humans have created. Why is this happening and what can we do about it?