1. Collaboration and SOA: The HUD CIO Perspective

2. Page 2 Agenda A New HUD – iMPACT 200 HUD Modernization Plan Target Enterprise Architecture SOA Infrastructure Transition to SOA

3. Page 3 HUD Business Overview – Impact200 o Promote responsible, sustainable homeownership for all Americans o Maximize options for safe and affordable housing so all Americans can embark on a path to self-sufficiency o Deliver effective, timely service to our customers, employees and partners

4. Page 4 HUD Business Architecture

5. Page 5 FY2008 IT Portfolio

6. Page 6 HUD Modernization Plan Modernization Plan  Define Baseline Architecture  Analyze Baseline to Identify Improvements  Define Target Architecture  Perform Gap Analysis Between Target and Baseline Architecture  Develop Sequence Plan  Monitor Performance

7. Page 7 Target Enterprise Architecture Structured on SOA model  Characteristics of Target Architecture Agility Scalability Interoperatibility Flexibility Innovation Re-usability Portability Reduced Complexity Extensibility

8. Page 8 Target Enterprise Architecture

9. Page 9 Competing SOA Solutions…? Microsoft SOA How we Conduct Business… …How We Collaborate Internally Business Focus User Focus Business Focus User Focus A Product Trend to Watch

10. Page 10 Oracle SOA at HUD - Business

11. Page 11 SharePoint Approach Traditional Approach Cost per user = High Seat license includes functionality most users will never use High Training Costs – High Difficulty SharePoint Portal Approach Use InfoPath and SharePoint services to interact with one or more LOB applications Low cost of integration/ Development Uses Tools already on Desktop Reduces LOB Application Seat Licenses required

12. Page 12 Operating System Services Database Services Search Services Workflow Services ASP.NET (Web Parts, Personalization, Master Pages, Provider Framework (Navigation, Security, etc.) Applications Collaboration Discussions Calendars E-Mail Integration Alerts Project Mgmt “Lite” Offline Lists/Docs Content Mgmt Authoring Approval Web Publishing Policy & Auditing Rights Mgmt Retention Multi-Lingual Staging Portal MySites Targeting People Finding Social Networking Privacy Profiles Site Directory Search Indexing Relevance Metadata Customizable UX Biz Processes Rich/Web Forms LOB Actions Single Sign-On BizTalk Integration BI Excel Services Dashboards KPIs Report Center SQL RS/AS Integ. Biz Data in Lists Biz Data Catalog Platform Services Storage Repository Metadata Versioning Backup Security Rights/Roles Pluggable AuthN Per Item Rights Trimming Management Admin UX Delegation Provisioning Monitoring Topology Config Mgmt Farm Services Feature Policy Extranet Site Model Rendering Templates Navigation Visual Blueprint APIs Fields/Forms OM and SOAP Events Deployment SharePoint 2007 SOA

13. Page 13 Employees Customers Partners Information sharing Controlling content Decision making Unified, enterprise-ready solution = organizational effectiveness XML Web Services Application Integration/ Custom Apps Portals Team Collaboration Personal Enterprise Portal Line Of Business Applications (PS, data warehouse, custom...) SharePoint Web Facing Portal SharePoint SOA at HUD - User

14. Page 14 Benefits of SOA at HUD Align Business with IT by driving IT through Business Process Management Improve Customer satisfaction by streamlining and automating business processes Achieve Business Agility using collaborative infrastructure Reusability of services lower the maintenance cost for IT

15. Page 15 Transition to SOA Establish an Enterprise-Wide Vision Use a SOA Maturity Model to transition to SOA Adopt SOA Framework to align to EA –Business Processes Management –Blueprints –Service Identification and realization –Flexible and scalable Infrastructure –Best Practices Develop a SOA Roadmap Communicate SOA Governance

16. Page 16 Initial Steps at HUD for Transition Current Steps  Standardize the Presentation Layer using Portal Technologies  Use the SOA Infrastructure for transitioning Identify Services performed by the current applications  Identify new/re-usable services  Establish standards for interoperation  Orchestrate current business processes using these services Going Forward  Optimize the business processes  Re-engineer the current applications using SOA

17. Page 17 Current Projects in Transition National Housing Locator System (NHLS) FEMA Interfaces to Disaster Information System

18. Page 18 National Housing Locator System NHLS provides disaster affected citizens help by allowing them to search for temporary housing Citizens can easily navigate the NHLS application with no help.  Can Look for Current Disasters  User friendly with familiar tools; Google Maps, simple searches, navigable interface  Resource/Disaster locator: one stop shop for a citizen to find disaster information  they can look for disaster related resources near their current location (find a shelter nearby)  HUD will be able to provide briefs using Announcement tools on NHLS (in development)  24/7 available public access via web Citizens able to get HUD Disaster announcements  This improves communication between Agency and the Citizen

19. Page 19 A SOA Success Story: NHLS Rich User Experience User friendly Utilizes AJAX for fluid user navigation Commenting & Mapping system Desktop application look-and-feel under a distributed Web environment Rapid Application Development (RAD) Short iterative development cycles Developed using the RAD methodology Utilized an Integrated Development Environment (IDE) to reduce development time Quick and flexible development Perpetual Beta Constantly accepting requirements Soliciting requirements direct from Users Adaptive/Corrective Maintenance Long-Tail Approach to Data Collection Accept data from a large number of sources No data set is too small Ability to collect data from numerous sources to increase the total number of units available Data Mashups Utilizing APIs (e.g., Google Maps) as a data mashup platform Overlays Potential to display other overlays Displaying grouped data enhances overall user experience Web Service/REST Means of data exchange between systems Direct access to property data to outside organizations Transfer of data using a simple form of Web service Adhere to a standard transportation method

20. Page 20 Technical  Business Value Technical  Rich User Experience User Friendly Utilizes AJAX for fluid user navigation Commenting & Mapping system Desktop application look and feel under a distributed Web environment Technical  Rapid Application Development (RAD) Short iterative development cycles Developed using the RAD methodology Utilized an Integrated Development Environment (IDE) to reduce development time Quick and flexible development Business Value  User Acceptance Reduces cost of deployment and acceptance Reduces training costs (when Disaster Centers hire temporary workers or social volunteers – need to get them using the system fast) We were able to train 110 FEMA users assisting Katrina disaster affected families in a 30 min. web cast Business Value  Robust Reduces time to market Requirements are met in a rapidly changing environment. Ability to respond to requirements that are unpredictable like the weather Continuous Improvement

21. Page 21 Technical  Business Value Technical  Long-Tail Approach to Data Collection Accept data from a large number of sources No data set is too small Ability to collect data from numerous sources to increase the total number of units available Business Value  Enterprise Integration Reduce cost by re-use (adopt) Collaborate between program areas Leverage existing investments Business Value  SOA Adoption to a Service Oriented Architecture Operational Efficiency Faster and less expensive integration Business Value  Adaptable Accept data from a large number of sources No data set is too small Ability to collect data from numerous sources to increase the total number of units available Technical  Data Mashups Utilizing Google’s map API as a data mashup platform Overlays Potential to display other overlays Displaying grouped data enhances overall user experience Technical  Web Service/REST Means of data exchange between systems Direct access to property data to outside organizations Transfer of data using a simple form of Web service Adhere to a standard transportation method

22. Page 22 What Our Partners Can Do Understand our Business Needs Help CIOs Lead Cultural Change Promote Service Reuse across the Federal Government Make it Plug and Play – Google Example