Enterprise Architecture
HUD's Enterprise Architecture (EA) Practice initiates an information technology (IT) lifecycle that is comprised of three integrated phases - architecture, investment, and implementation. EA work is business-driven, and technology solutions begin with the intended business model as the goal. HUD "architects" before design, and designs before building and deploying technologies.
Enterprise Architects and Solutions Architects work collaboratively with business and technical subject-matter experts from throughout the Department and other agencies to guide the development of information technology Blueprints, which represent segments within the HUD Enterprise Architecture v4.0. The Practice provides strategic direction to the IT Investment Management (ITIM) process by aligning common solutions across HUD's strategic lines of business, business functions and core IT services. These activities enable accelerated IT Modernization at HUD.
HUD is mandated by the Clinger-Cohen Act and by OMB Circular A-130 to develop and enforce a single enterprise architecture. EA is also a key E-Government component in the progress of the President's Management Agenda.
This enterprise approach:
Simplifies IT investment decision-making
HUD's EA practice uses blueprints to enhance the evaluation of proposed IT initiatives. Blueprints provide a common language that links IT initiatives with the Department's strategic objectives and core business functions. Our simple approach provides executive-level staff with a strategic, enterprise view of HUD's IT portfolio.
Accelerates system implementation
HUD's EA practice applies existing blueprints to accelerate system design and development. Blueprints are working documents. They define core business processes, common data elements, cross-cutting applications, and standard system platforms. Blueprints are used to verify common system needs that span program areas, and facilitate enhanced communication between program areas and technical staff to define custom requirements. Our leveraged approach means that system design does not start from scratch. We also utilize the EA Roadmap, a 5-year plan to help modernize HUD's capabilities to achieve our strategic and agency priority goals.
Reduces system diversity
HUD's EA practice uses blueprints to streamline HUD's IT environment. Blueprints define core business processes, common data elements, and standard applications and platforms. Standardization reduces the number of IT products, reduces system maintenance and operation costs, and simplifies staff training. Our standards-based approach reduces systems diversity across the Department.
More Information
About Us
HUD's Enterprise Architecture (EA) Practice is under the direction of the Enterprise Architecture Team in the Office of the Chief Information Officer.
The Enterprise Architecture practice is coordinated closely with HUD's Information Technology Investment Management (ITIM) process. The EA provides guidance in the design and selection of IT projects for program operations. Together the EA practice and the ITIM process work with IT program management to deliver top quality information services to support HUD strategic objectives.
Benefits
Simplifies IT investment decision-making HUD's EA practice uses blueprints to enhance the evaluation of proposed IT initiatives. Blueprints provide a common language that links IT initiatives with the Department's strategic objectives and core business functions. Our simple approach provides executive-level staff with a strategic, enterprise view of HUD's IT portfolio.
Accelerates system implementation HUD's EA practice applies existing blueprints to accelerate system design and development. Blueprints are working documents. They define core business processes, common data elements, cross-cutting applications, and standard system platforms. Blueprints are used to verify common system needs that span program areas, and facilitate enhanced communication between program areas and technical staff to define custom requirements. Our leveraged approach means that system design does not start from scratch.
Reduces system diversity HUD's EA practice uses blueprints to streamline HUD's IT environment. Blueprints define core business processes, common data elements, and standard applications and platforms. Standardization reduces the number of IT products, reduces system maintenance and operation costs, and simplifies staff training. Our standards-based approach reduces systems diversity across the Department.
Blueprints
HUD's Enterprise Architecture (EA) Practice works collaboratively with business and technical subject-matter experts from throughout the Department to guide the development of information technology Blueprints.
Blueprints describe the future state of information technology at HUD. They are organized using HUD's enterprise architecture model and reflect HUD's enterprise architecture principles (pdf).
Blueprints are developed to:
- translate strategic business drivers into a common vision for information technology.
- define core business functions and information requirements.
- describe crosscutting application functions that can be shared by information systems.
- specify standard system components including data, applications and platforms.
See a sample blueprint (pdf) and review a case study.
News
Enterprise Architecture Team Assists in Establishing HUD's Recovery Act Web Site
HUD's Enterprise Architecture Team coordinated with members of HUD's Office of Departmental Operations and Coordination to quickly establish a website and mapping application highlighting the President's American Recovery and Reinvestment Act of 2009. This effort took place only eight days after President Obama signed the Act into law.
The mapping application allows the public to search Recovery Act Program funding allocations by state. HUD will administer $13.61 billion for projects and programs supporting the Recovery Act. As of February 25, 2009, nearly 75 percent of the funds were allocated to state and local recipients.
Rental Housing Assistance Blueprint
Workshop sessions with the Office of Public and Indian Housing (PIH) and Multifamily Housing are complete, and the Rental Housing Assistance Blueprint is 100% complete.
FY 09/10 SELECT Strategic Portfolio Review
As part of the FY 09/10 Select Process, the OCIO scheduled one-on-one meetings for major initiatives. The EA Team, along with the IT Investment Management Team, and representatives from the Office of Systems Engineering and Efficiency facilitated the meetings. The purpose of the meetings is to review this year's Strategic Portfolio Review recommendations, the IT Master Schedule and performance. More.
FY 08/09 SELECT Strategic Portfolio Review
As part of the FY 09/10 Select Process, the OCIO will schedule one-on-one meetings for major initiatives. The EA Team, along with the IT Investment Management Team, and representatives from the Office of Systems Engineering and Efficiency will facilitate the meetings. The purpose of the meetings is to review this year's Strategic Portfolio Review recommendations, the IT Master Schedule and performance. More.
FY 06/07 SELECT Strategic Portfolio Review
The Strategic Portfolio Review (SPR) is a set of analysis and recommendations designed to advance the IT portfolio during the FY 2007 Select process relative to the principles defined in the Target Enterprise Architecture (EA). The EA Team conducted meetings with the Program Areas in March 2005, and specific EA Training/Workshop sessions in April 2005.
Grants Management Segment Architecture Development
The HUD eGrants initiative combines the needs of integrating and streamlining the diverse grant management programs and systems of the Department with the goals and priorities of the Federal eGrants initiative (one of OMB-sponsored Quicksilver projects). The result will be a HUD-wide solution to support end-to-end grants management activities that maximizes the services provided within communities, business partner collaboration, and agency financial and technical integrity. The Grants Management Blueprint has been completed, and is going through review.
Financial Resource Management Segment Architecture Development
The HUD Integrated Financial Management Improvement Project (HIFMIP) has successfully completed its first of six major milestones - the Initiate Phase or Planning work, that included 3 components:
1. mapped the "as is" financial systems environment;
2. identified a high-level vision of a "future" state; and
3. provided a recommended systems solution to replace HUD's decades-old legacy financial management systems.
The HIFMIP started the second major project phase - System Define - or Requirements work in October 2004. This includes establishing business processes and system requirements, including development of the initial enterprise architecture for the financial management resource (FMR) function for the Department. This critical second phase includes the selection of an OMB-OFFM certified COTS software system.
The HIFMIP System Define Project Team is completing the requirements for HIFMIP, including the following planning documents:
1. Roadmap;
2. Project Work Plan;
3. Legacy Disposition Plan; and
4. Solicitation package to select System Integrator/Center of Excellence (COE) project team to support the project through implementation of the COTS certified financial system.
The draft segment architecture for the Financial Management Resource Function has been completed and reviewed by the Office of Assistant CFO for Systems Management. The OCFO Management, and OCIO Management have been briefed. The System Define phase, and planning documents were completed.
The HIFMIP blueprint is complete, and includes the information and recommendations presented in the revised planning documents. The selection of a Systems Integrator/Center of Excellence (COE) (alternate service provider) in FY 2006, will require an update to reflect the COTS selection, system design and system configuration decisions made by the System Integrator COE project team; after they evaluate the project and requirements.
The HIFMIP Project Team members are participating in the E-Government Financial Management Line of Business (FM LoB) Project Team, and working to ensure HIFMIP aligns with and implements the recommendations approved for Federal financial management organizations.
Single Family Housing (SFH) Blueprint
The Department awarded the SF Systems Modernization Contract to Frontline Systems on February 4, 2004. This contract commences the process of re-engineering the SF systems, and integrating them into HUD's Target Architecture. The effort will help FHA comply with legislation, address audit weaknesses and reduce the cost of systems ownership. The SF Blueprint was completed in September 2002, which will reduce the number of SFH systems by nearly 80 percent. More. (pdf)
In October, 2004, a contract was awarded to IES, Inc., for "end-to-end" System Analysis, Project Management Support, and Re-Design of the Single Family Enterprise Architecture.
Crosscutting Segment Architecture Development
Workflow Management Segment Architecture Development
Every activity at HUD has a process. A key component of proper information technology implementation is how processes are currently automated, and which processes can benefit from automation, and how they are automated. This segment architecture development effort defines these processes, and how automation relates to existing, and future systems at HUD.
Document Management/Records Management Segment Architecture Development
Much of HUD's business involves the use of documents, and other non-structured data. In addition, there exists explicit regulations on the storage and aging of these items. This segment architecture development effort will define what lines of business and functions require electronic storage, and management of documents and other non-structured data, and how these capabilities should be implemented across HUD.
The blueprint under development is a standard technology architecture that updates and extends a previous draft blueprint.
Enterprise Architecture Management Maturity
In a survey published in December 2003, GAO identified HUD's Enterprise Architecture Practice as one of the top ten (10) EA Practices in the Federal Government. Of 96 agencies, HUD was 5th overall. HUD was rated at a Stage 3 under GAO's new, more stringent Enterprise Architecture Management Maturity Framework Version 1.1, and is one of seven (7) agencies that are five (5) or fewer elements away from reaching the "Highly Effective" Stage 5. (See the link to the GAO site below for more.) Information Technology: Leadership Remains Key to Agencies Making Progress on Enterprise Architecture Efforts. GAO-04-40, November 17.
HUD and Department of Interior Share Data Architecture Best Practices
The HUD Enterprise Data Management Team shared Best Practices and provided the Department of Interior (DOI) with the Segment Data Architecture Development Methodology (SDADM). HUD reviewed the DOI data architecture development in the Best Practices study that it prepared prior to completing its Segment Data Architecture Development Methodology. The DOI used a phase of the HUD SDADM to capture initial considerations for identifying Authoritative Data Sources (ADS). These considerations are being used as a mechanism to obtain feedback from their bureaus and offices on the process that DOI should utilize to identify and implement an ADS as they transition from baseline to target architecture.
Resources
Federal Resources