Five Steps to Improved Enterprise Architecture

January 30, 2017

Enterprise architecture improves how organizations develop their strategic plans, make investment decisions, and establish effective enterprise governance. Federal agencies can use enterprise architecture to make their operations more efficient as well as promote strategic and innovative initiatives.

Laws, such as the Federal Information Technology Acquisition Reform Act (FITARA), require federal agencies to provide more transparent reporting on IT portfolios. These laws are so new, many best practices on IT portfolio reporting are still being developed.

LMI works with the General Services Administration (GSA) to better connect its budget and IT portfolio management processes to help with its reporting. This approach helps GSA answer the following questions:

  • How do we decide when to enhance, migrate, or retire our applications?
  • What functions do those applications support and what are their life cycle costs?
  • What technology standards are approved for use?
  • How should we introduce new or emerging technology?
  • Are we engaging with all of our stakeholders on the right projects and at the right time?

In many cases, the ability to rapidly and consistently pull standardized reports saves time and improves data quality for employees.

This conversation often starts with compliance, but very quickly, it becomes an even more interesting discussion around how to better fulfill your mission because data is more transparent and easily accessible.

Building a Healthy Enterprise Architecture

  1. Make a business case for investment: Identify specific problems and expected outcomes that enterprise architecture will address. Track how much time employees spend on pulling reports. Evaluate the risks or costs associated with not providing reports in a timely fashion.
  2. Evaluate business needs: Asking the right questions will help prioritize what data needs to be visualized and at what level of detail
  3. Assess your current enterprise architecture: How is the enterprise architecture program currently defined within your organization? Where is it in your organizational chart? How many resources does your enterprise architecture program have or need? How is it integrated with your current governance processes? Are they only in compliance or do they have a seat at the table when budget decisions are made? What types of interactions do they have with other departments? There are enterprise architecture maturity models for assessment and goal setting in this area.
  4. Assess your data management strategy: How many data repositories are there? Is there an open data policy? How is enterprise data currently managed—is it standardized or stove-piped? Are data repositories well-maintained and well-governed?
  5. Create open communication between stakeholders: Making advances in using data for decision making for an organization involves considerable user outreach. It is important to let people, especially leadership, know this data exists. Ensuring dashboards continually improve requires an ongoing interaction between data visualization people and developers. Things are changing all the time either due to legal changes or lessons learned.

A Healthy Enterprise Architecture Can Spur Innovation

When an organization improves its data quality, there are more opportunities to use data in innovative ways. Clean repositories with easy hooks or an application programming interface (API) can allow developers to support new applications that never would have been possible if the organization did not build a foundation of well-managed data.

LMI works with federal agencies and private industry on enterprise architecture best practices every day. We know which tools provide the reports needed for compliance and have an eye for open-source tools that do not require additional acquisitions.