Glossary

A collection of Enterprise Architecture terms and definitions from a variety of sources: EA3 Cube, Introduction to Enterprise Architecture, The Common Approach to Federal Enterprise Architecture (FEAF-II), ISO 42010:2011 and TOGAF 9. 00

Freedom and Responsibility

Responsibility is like a hot potato, but we have developed better ways to handle it than simply passing it on. We keep paying for this trickery, and so far, we can afford it. However, the stakes grow exponentially. This is another essay in the Autonomy and Cohesion series. Autonomy and Cohesion is one of the essential balances that […]

EA: The Missing Puzzle Piece

The words Enterprise Architecture often elicit a predictable reaction: a nod of polite acknowledgement, sometimes tinted by mild apprehension or indifference. Somewhere along the line, it became something that busily hums behind the scenes, tucked away in senior briefing decks or internal frameworks, occasionally referenced but rarely felt at the grassroots. Yet that quiet presence hides a paradox. For many organizations striving to steer through complexity, boost resilience, and drive transformation, Enterprise Architecture is not an optional refinement — it is the missing puzzle piece that makes everything else fall into place.

The post EA: The Missing Puzzle Piece appeared first on EAWheel.

EA as a Cultural Navigation Practice

Holding the balanced view and perspective “I keep trying to teach the business about enterprise architecture but they just don’t get it!“ A former colleague from a nearby university would periodically invite me to coffee for a lengthy discussion about the frustrations of working as an enterprise architect in higher education. Each time, she’d end […]

Netflix and Algorithms

Following my previous posts on Netflix, I have been reading a detailed analysis in Ed Finn’s book, What Algorithms Want (2017).Finn’s answer to my question Does Big Data Drive Netflix Content? is no, at least not directly. Although Netflix had used dat…

Netflix and Algorithms

Following my previous posts on Netflix, I have been reading a detailed analysis in Ed Finn’s book, What Algorithms Want (2017).Finn’s answer to my question Does Big Data Drive Netflix Content? is no, at least not directly. Although Netflix had used dat…

Why CIOs Need to Consider Application Rationalization for Digital Transformation

When talking to customers and prospects, I hear great ambitions for digitization. But I also hear about pains when they describe their IT landscape. Customers have often grown a complex IT landscape and lack transparency about their costs, or functional redundancy occurs, especially after mergers and acquisitions. Information about their IT landscape sometimes resides in…

Address Regulatory Compliance Challenges in the Financial Services Industry with Enterprise Architecture

Regulatory compliance is a core business fact of life for the financial services industry today. Compliance is not only about combating financial crimes such as money laundering, fraud, and tax evasion. But also about operating in a prudent and responsible manner and being able to prove that you have the policies, procedures and processes in…

The post Address Regulatory Compliance Challenges in the Financial Services Industry with Enterprise Architecture appeared first on BiZZdesign.

Organizations as Systems – Kurosawa, Clausewitz, and Chess

In order to respond appropriately to the context we find ourselves in, it’s helpful that we be able to correctly define that context. It’s something humans aren’t always good at. Not too long ago, Sun Tzu’s The Art of War was all the rage as among executives. While the book contains some excellent lessons that […]

DATA Act IT Infrastructure – Platform Consolidation, Virtualization & Collaborative Governance as Change Enablers

Momentum and activity regarding the Data Act is gathering steam, and off to a great start. Reaching the 2017/2018 milestones, however, will require IT infrastructure change.
Some change may be simple or take advantage of existing modernization
efforts; much change will be very difficult, complex and/or costly.
Strategies to prepare for this change, and catalyze it, are not yet part
of the government-led discussion – but they are now part of the
industry-led discussion, per this new Executive Report from ACT-IAC, co-authored by Oracle: “The DATA Act – IT Infrastructure Guidance Change Facilitation for IT Departments”.

DATA Act IT Infrastructure – Platform Consolidation, Virtualization & Collaborative …

Momentum and activity regarding the Data Act is gathering steam, and off to a great start. The DATA Act directs the Office of Management and Budget (OMB) and the Department of the Treasury (Treasury) to establish government-wide financial reporting data standards by May 2015. The act also requires agencies to begin reporting financial spending data using these standards by May 2017 and to post spending data on USASpending.gov or an alternate system by May 2018.

According to many reports, including a recent GAO testimony, “OMB and Treasury have taken several significant steps towards meeting these requirements including the release of 27 discrete data standards, draft technical specifications, and implementation guidance intended to help federal agencies meet their responsibilities under the act. However, given the government-wide scope of the technical and cultural reforms required by the DATA Act, much more remains to be done…OMB and Treasury have proposed standardizing 57 data elements for reporting under the act. They released 15 elements in May 2015, a year after the passage of the act, and have since released 12 more. Eight of these were new elements required under the DATA Act; the balance of the first 15 data elements were required under the Federal Funding Accountability and Transparency Act of 2006 (FFATA). Officials told us that they expect to complete the process by the end of the summer.”

Reaching the 2017/2018 milestones, however, will require IT infrastructure change. Some change may be simple or take advantage of existing modernization efforts; much change will be very difficult, complex and/or costly. Strategies to prepare for this change, and catalyze it, are not yet part of the government-led discussion – but they are now part of the industry-led discussion, per this new Executive Report from ACT-IAC, co-authored by Oracle: “The DATA Act – IT Infrastructure Guidance Change Facilitation for IT Departments”.

At this time, there is considerable effort and oversight focused, and rightly so, on essentially the requirements and governance around the requirements, i.e. (as the GAO report focuses on) things like:

  • Data Standards Governance
  • Identification of Data Programs
  • Stakeholder Collaboration

Yet this effort only address the first few steps towards solution strategy, design and implementation (therefore including information technology infrastructure), as Treasury recommends in its DATA Act Playbook: “To assist agencies with implementation, Treasury recommends eight key steps that can help agencies fulfill the requirements of the DATA Act by leveraging existing capabilities and streamlining implementation efforts.”

The eight key steps are:

(These are well underway by many entities)

1. Organize Your Team: Create an agency DATA Act work group including impacted communities within your agency and designate a Senior Accountability Officer (SAO);
2. Review Elements: Review the list of DATA Act elements and participate in data definitions standardization;

(The following are not yet commonly underway)

3. Inventory Data: Perform an inventory of agency data and associated business processes and systems;
4. Design & Strategize: Plan changes to systems and business processes to capture financial, procurement, and financial assistance data;
5. Execute Broker: Implement a “broker”at the agency.  The broker is a virtual data layer at the agency that maps, ingests, transforms, validates, and submits agency data into a format consistent with the DATA Act Schema (i.e., data exchange standards).  
6. Test Broker Implementation: Test broker outputs to ensure data is accurate and reliable;
7. Update Systems: Implement other system changes (e.g., establish linkages between program and financial data, and capture any new data); and
8. Submit Data: Update and refine process (repeat 5-7 as needed)

Acknowledgement of the change ahead for IT departments is out there, though…”Creating the linkages for these data (i.e. the mapping among data across various systems) is going to be one of the biggest challenges for many federal agencies. While it might seem like a relatively straight-forward task, the volume of data and the complexity of systems make it a significant challenge.” – Statement of David A. Lebryk, Fiscal Assistant Secretary, U.S. Department of the Treasury before the House Committee on Oversight and Government Reform Subcommittee on Information Technology and Subcommittee on Government Operations, United States House of Representatives, July 29, 2015

The ACT-IAC paper lays out three fundamental tenets for addressing this change, to help either reduce or facilitate processing the volumes of data, and most importantly, to reduce the complexity of the system changes required.

Consolidation: the DATA Act mandate includes no new budget, yet requires agencies to instigate or take advantage of a wealth of shared services and data management improvement or modernization programs already underway, both in government and industry, to reduce duplication and unnecessary IT management and integration complexities. Message: “standardization and consolidation initiatives are a priority, aligned via enterprise architecture tenets.”

Engaged governance: most public sector agencies are faced with generational data management change drivers already, from big data to secure mobile analytics requirements. This federal-led initiative provides a top-down, organizational imperative for actionable, cost-effective data governance across the entire community of data users and stewards. Message: “let’s get committed, transparent, and hands-on with data governance.”

Virtualization: the variety of data standards and processing maturity across all the stakeholders is so great, from federal to state, local, and private recipients, that the elements of a solution will require a great deal of abstraction from the legacy data stores, systems and acquisition plans that can’t easily be changed. This introduces a dynamic, agile layer of usefulness between the existing IT infrastructure and new users with high, consumer-driven expectations. Message: “do no harm, but expose tangible value quickly.”

Contact me or anyone at Oracle for more information about challenges regarding IT Consolidation (including Data Integration, Master Data & Data Integration Services, i.e. “Broker” approaches), Collaborative & Engaged IT Governance, or IT Virtualization Strategies (from platform technologies to cloud services) – whether to prepare your agency for DATA Act compliance, or to simply advance and accelerate IT modernization altogether.

Enabling Successful Business Change with Enterprise Architecture

How successfully does your organization implement strategic business change initiatives? A recent study[1] by the Economist Intelligence Unit revealed that only 56 percent of strategic initiatives meet the original goals and business intent. Advances in digital technology will continue to enable all kinds of new products and services and inspire innovative strategies, but will your

The post Enabling Successful Business Change with Enterprise Architecture appeared first on Louise A Harris on Enterprise Business Architecture.