March 2006 deadline looms for implementing enterprise architecture
Writing in Federal Times, Karlu Rambhala of Avineon notes that OMB will start assessing agencies' enterprise architectures starting in October. They'll be done by March 2006. Here are the points they'll be judging. Does the architecture:
- Enable change management?
- Enable integration and standardization regarding interoperability, data, business logic and interface?
- Support the technological aspects of system components, operating platforms, performance and security?
- Mesh with the agency’s strategic goals?
Fortunately, this isn't exactly untrod ground, he writes.
To accelerate compliance — and a higher level of performance — agencies can borrow from the playbook of commercial enterprises that have achieved success with standardization and interoperability. For example, best practices in architecture design and software development are achieved when design efforts are focused on sound processes, repeatability, clear documentation, appropriate feedback and excellence in project management. The Treasury Department’s Financial Management Service is one agency that has followed this model through its migration from legacy systems to more functional and reusable component-based systems, which offer a measure of success for integration requirements.
Ultimately, doing this work will yield great things.
Enterprise architecture has become central to every agency because it is where people, processes, data and technology come together to deliver the citizen-centered, results-oriented government outlined in the president’s management agenda. Agencies that build and take full advantage of well-designed architectures are leading the charge in delivering on the president’s vision. In the longer term, compliance means agencies will have systems that adapt by incorporating feedback into design and operations, so they are “future-proofed” against unknown challenges. Now that sounds like a transformed government.
Enterprise Architecture White Papers
- Business Process Trends: Developing an Enterprise Architecture - Business Process Trends
- California Enterprise Architecture Framework - State of California
- DHS Enterprise Architecture: A National Architecture for Information Sharing - Input
- Advancing Enterprise Architecture Maturity - Institute For Enterprise Architecture Developments
- The Four-Domain Architecture: An Approach to Support Enterprise Architecture Design - IBM
- An IT Enterprise Architecture Process Model - U.S. Department of Commerce
- Information Technology: INS Needs to Better Manage the Development of Its Enterprise Architecture - Government Accountability Office
- Gartner Enterprise Architecture: A Home for E-Government - Gartner
- Enterprise Representation: A Different Paradigm for Designing Process-Interoperability Standards - National Institute of Standards and Technology
- Adancing Enterprise Architecture Maturity - Interoperability Clearinghouse